DelKey Privacy Policy

Updated: October 26, 2026

About DelKey

DelKey displays a Del button over your existing Android keyboard to delete the character to the right of the cursor or selected text.

1. Information processed

DelKey uses Google Analytics for Firebase for general app usage statistics and product improvement. Data may include the Firebase app instance identifier; app opens and screen views; accessibility service setup status; button color family and selected icon; app version, operating system and device model; and approximate country/region derived from IP information. Names, email addresses, phone numbers, contacts, photos, files, typed text and deleted text are not collected as analytics data. Exact button color values are not sent.

Legacy closed-test records

Starting with production version 1.12, test participation, tester ID assignment, test usage-date uploads, feedback submission and reminders are removed. On first launch after updating, the app clears legacy local test participation data and queued records, scheduled test work and notifications. Button settings and introduction preferences are preserved. Updating does not delete records previously sent to the test server. Under the policy disclosed during testing, individual test records are due for deletion within 30 days after testing ends. This policy does not confirm that server deletion has already occurred. Contact the developer through the contact details on Google Play for deletion enquiries.

2. Accessibility service

DelKey uses the Android accessibility service to detect keyboard visibility and position and access the active input connection. This is used to display the Del button and perform deletion when you press it. Typed text is not saved or sent outside the device.

3. Local settings

DelKey stores whether the button is enabled, its position, size, colors and icon, and introduction preferences on your device. Position, size and exact color values remain local. Service setup status, DelKey activation state, color family, selected icon and feature-specific ad request, display, reward completion, dismissal, unlock and failure events may be sent to Google Analytics for Firebase.

4. Analytics

Google Analytics for Firebase processes the information described above for usage statistics and product improvement. Analytics is encrypted in transit. Event and user-level data is processed according to the retention settings of the Google Analytics project. Advertising ID collection and advertising personalization signals are disabled.

5. Advertising

The advertising-integrated version uses Google AdMob (Google Mobile Ads SDK) and the User Messaging Platform (UMP). Separate rewarded ad flows apply to DelKey activation, button colors and button icons. Choosing OK in a feature notice requests its ad. After an ad is actually displayed and dismissed, that feature is unlocked even if the ad is closed early. Choosing Later, failing to load, or failing to display an ad does not unlock the feature. Ad length and close controls depend on the creative.

For advertising, measurement and fraud prevention, Google may process IP addresses and approximate location derived from them, ad/app interactions, performance and diagnostic information, and device identifiers such as app set ID. Android advertising ID and AdServices AD_ID, Attribution and Topics permissions are removed. This does not eliminate all other identifier or advertising-related processing. Typed and deleted text is not supplied to advertising SDKs.

UMP checks consent status before ad requests and presents required forms. Ad privacy options are provided when required. If consent cannot be confirmed or ads cannot be requested, the feature stays locked. Feature-specific presentation and unlock records are stored locally and survive app restarts, updates and Reset all settings. If the process ends after an observed presentation, the corresponding unlock is recovered at the next launch. Uninstalling, clearing data or changing devices does not restore these permissions.

6. Service provider

Google provides Google Analytics for Firebase, Firebase Authentication, Cloud Firestore, AdMob and UMP and processes the analytics, advertising and consent data needed for each service. DelKey does not sell typed text or pass it to advertising SDKs.

7. Children

DelKey does not knowingly collect personal information from children. If offered to an audience that includes children, advertising and data processing must comply with Google Play Families policies and applicable requirements.

8. Security and data management

Typed text is not stored or transmitted. Analytics data uses encrypted connections. Clearing app data or uninstalling removes local settings and the local app instance. Previously collected analytics data is handled according to its retention settings; uninstalling does not immediately erase server-side data.

9. Contact

For privacy questions and legacy test-data deletion enquiries, use the developer contact details listed on Google Play.

10. Changes

This policy may change when functionality, SDKs or applicable requirements change. The update date on this page will be revised.

Invitation code registration

Registering an invitation code unlocks DelKey, button colors and button icons without ads. Registration uses a Firebase Authentication anonymous installation identifier. Cloud Firestore stores the SHA-256 code hash, use status, registering identifier, server registration time and installation entitlement. The original code is not sent to Firestore or Analytics. These records support app functionality and prevent code reuse; they are not linked to ad targeting or Analytics events. Registration requires internet access. Confirmed access is saved locally and survives restarts, updates and Reset all settings, but is not restored after uninstalling, clearing data or changing devices. Records have no automatic expiry and are retained while needed to operate the invitation program and prevent reuse. Contact the developer using the contact details on Google Play for deletion requests.