Privacy Policy
Type History · com.coco.typehistory
In short: The text Type History records is stored only in a local database on this device. It is never uploaded, never synced, and never shared with anyone, including the developer. Password fields are never recorded. However, this app shows ads through Google AdMob and collects anonymous usage and crash reports, so an internet connection and your advertising ID are used to load those ads and send anonymous statistics. Your typed records are not part of that traffic.
1. Information We Collect
Type History has no account, no login, and no server of its own. The information the app handles is as follows.
- Text you type — stored on your device only (never transmitted): Through the Accessibility Service, the app reads text you type into text fields in other apps and saves it, along with the app name and a timestamp, in a local database (Room) on this device. This data never leaves the device.
- Password fields — never recorded: Fields flagged as password fields (
isPassword) are skipped at the code level before any text is read.
- App settings — stored on your device only: Your retention period, pause state, excluded app list, and PIN lock preference are kept in the app's private storage. Your PIN is stored only as a SHA-256 hash with a random salt, never as plain text, and cannot be reversed.
- Advertising data — collected by Google AdMob (sent to a server): To serve ads, the AdMob SDK may collect and use device identifiers such as the advertising ID (AD_ID), approximate location, and app interaction data. This is collected by Google; the developer receives only aggregated ad performance reports. See section 4 below.
- Anonymous usage and diagnostic data — collected by Firebase Analytics and Crashlytics (sent to a server): To improve the app and keep it stable, anonymous usage events (aggregate figures such as how often a feature was used or which settings are on) and crash reports are sent. Neither the text you type nor the package name of the app you typed it in is included in these events. See section 4 below.
- What we do not collect: No name, email address, phone number, contacts, photos, files, precise location, financial information, or health information.
2. Use of the Accessibility Service
Type History uses the Android Accessibility Service for its core feature: keeping an on-device copy of the text you type in other apps so you can recover it later. This is the only way Android allows an app to provide that feature.
- What it reads: The app subscribes to exactly one event type, text change events (
TYPE_VIEW_TEXT_CHANGED). From those events it reads the text in the field and the package name of the app you typed it in.
- What it is used for: The text is saved to the local database on this device solely so you can look it up, search it, and copy it back later.
- What it does not read: Password fields are skipped. Nothing is recorded for apps you have excluded, or while capture is paused.
- No actions on your behalf: The app never clicks, scrolls, navigates, or fills in forms for you. It is a read-only service and declares no gesture capability (
canPerformGestures) and no key event filtering.
- Your control: The Accessibility Service is off by default. Before you enable it, the app shows a dedicated disclosure screen explaining exactly what it reads and where it is stored, and requires your explicit consent. You can turn it off again at any time in Android Settings.
- This app is not a monitoring or spy tool. It cannot access another person's device or messages, and it does not recover messages deleted by someone else.
3. Permissions We Request
- Accessibility Service: Read the text you type in other apps and save it on this device (core feature).
- Internet (INTERNET) and network state (ACCESS_NETWORK_STATE): Used only to load ads and to send anonymous usage statistics and crash reports. Your typed records are not included in that traffic, and the app's capture and recovery features work fully without an internet connection.
- Advertising ID (AD_ID) and ad services permissions (ACCESS_ADSERVICES_*): Declared by the Google AdMob SDK for ad serving and measurement.
- Biometrics (USE_BIOMETRIC): Used to unlock the app when you enable fingerprint or face unlock alongside the PIN lock. Biometric data is handled entirely by the Android system; the app only receives whether authentication succeeded.
- WAKE_LOCK, FOREGROUND_SERVICE: Declared automatically by Google libraries bundled with the ad SDK (such as WorkManager). The app itself does not use them.
4. Third-Party Services
Type History uses the following third-party services.
- Google AdMob: Serves in-app ads (a native ad and an app-open ad at launch). AdMob may collect and use device identifiers such as the advertising ID, approximate location, and app interaction and diagnostic data to serve relevant ads and measure them; this information is provided to Google. See the Google Privacy Policy and AdMob's data disclosure.
- Firebase Analytics: Collects anonymous usage events so the developer can see how the app is used. The text you type and the package name of the target app are never included — only aggregate figures such as counts and setting values are sent. See the Google Privacy Policy.
- Firebase Crashlytics: Collects crash reports and diagnostic information to improve app stability. See the Google Privacy Policy.
- The text records you type are never sent to AdMob, Firebase, or any other third party.
- You can reset your advertising ID or opt out of personalized ads in Android Settings > Google > Ads.
5. How Information Is Used
The records stored on your device are used only so that you can look them up, search them, and copy, share, or delete them from within the app. The developer has no access to this data. None of the app's information is ever sold.
6. Data Retention and Deletion
- Automatic deletion: Records older than your retention period are deleted automatically. The default is 7 days, and you can choose 1 day, 3 days, 7 days, 30 days, 90 days, 180 days, or 1 year.
- Manual deletion: You can delete individual records, or wipe everything at once with "Delete all records" in Settings.
- Stopping capture: You can pause capture in Settings, or exclude specific apps from being recorded.
- Uninstalling: Removing the app deletes your records and settings from the device. There is no copy on any server, so no separate deletion request process is needed.
- App lock: A PIN lock with optional fingerprint or face unlock keeps your records closed even if you hand your device to someone for a moment.
7. Children's Privacy
This app is not directed at children under 13 and does not knowingly collect personal information from children.
8. Changes to This Policy
This privacy policy may be updated as needed. Changes will be posted on this page.
9. Contact
For privacy inquiries: philleeran@gmail.com
Last updated: 2026-08-22 · 한국어