EQkey Privacy Policy

1. The short version

EQkey does not upload a stream of your ordinary keystrokes. After the adult-eligibility check succeeds, the keyboard may learn accepted English words and next-word counts on your device to improve local suggestions. It excludes secure fields, keeps that model separate for each credential identity, and does not send the learned words or counts to EQkey's API. Other text leaves your device only when you deliberately use an AI feature or submit information such as account details or support feedback. Separately, while usage analytics is on, we collect the app diagnostics described under Usage analytics below — including session replays of the app's own screens, in which text and images are masked.

• Reply sends the message you chose to copy or paste so the service can suggest a response.
• Charm sends the draft you entered in EQkey so the service can suggest a rewrite.
• Opener sends the scene, persona, relationship and tone choices needed to create an opening line. It does not send text from a conversation unless you deliberately enter text into the request.

AI suggestions are returned as editable drafts. EQkey does not send a message on your behalf.

2. Information we process

AI request content

When you use Reply, Charm or Opener, we process the text and choices needed to complete that request. These may include a copied message, your draft, previous suggestions you asked us to avoid repeating, the selected persona, relationship, opener scene and intimacy level.

Account and profile information

EQkey can be used with a device-based guest session. We create a random device identifier, guest identifier and authentication token to maintain that session, apply usage limits and prevent abuse.

The onboarding asks for gender and date of birth before the personalized keyboard is built. Those answers are held only in memory until the date-of-birth check confirms that the user is 18 or older; no profile choice is uploaded or persisted before that check. Other profile and sign-in fields are optional. Depending on the feature you choose, we may process:

• your name or nickname and email address, plus an optional email address or phone number you enter in a support or safety report;
• gender, birthday, occupation, interests and other profile choices you provide;
• Google, Apple or Firebase account identifiers and authentication tokens. A complete signed Firebase ID token may contain an identity-provider `picture` or profile-photo URL claim;
• personas, relationship choices, intimacy level and keyboard preferences associated with your account.

Google and Apple sign-in are optional. Phone and Facebook sign-in are not currently offered. Information supplied by an available identity provider depends on your provider settings and the permission screen you approve. EQkey does not separately call a profile-photo API or add a standalone avatar field to the login request. Separately, some AI features let you choose images for analysis. On iOS, the keyboard’s Read/Rizz feature asks for photo-library access; on Android, and in the app’s Understand feature on iOS, you choose images through the system photo picker without giving EQkey access to your library. Only the images you choose are read and uploaded to Surgelit’s API so an AI model can generate or analyze a response. EQkey does, however, send the complete Firebase ID token to Surgelit's API for authentication, and that signed token may contain a provider profile-photo URL claim. We therefore treat that claim conservatively as linked account information collected for App Functionality, not for tracking.

Purchases

When you subscribe to EQkey+, Apple or Google Play processes the payment. EQkey's service receives the purchase token, receipt or transaction data needed to verify the purchase and keep your membership in sync across renewals, cancellations and refunds. Payment-card data is handled by the applicable store and never reaches EQkey. When a subscription purchase succeeds and usage analytics is on, EQkey also reports a subscription event to AppsFlyer with the price and currency charged (never your card details), as described under Service providers and disclosures.

Support and safety reports

If you report AI content or contact support, we process the report or message, any contact information you choose to provide, and the information needed to investigate it. The current iOS feedback client does not add device diagnostics. On Android, a feedback submission may also include the operating-system version and device model to help troubleshoot the issue.

Service and network information

Our systems may process technical information that normally accompanies a network request, such as IP address, request time, app version, platform, response status and security logs. We use this information to deliver the service, protect accounts, prevent abuse and diagnose failures. We do not use an advertising identifier to provide EQkey.

Push notifications

Notifications are optional and off by default. When your version of EQkey offers them and you turn them on, EQkey registers a push token for this device — an Apple Push Notification service (APNs) token on iOS or a Firebase Cloud Messaging (FCM) token on Android — together with the random device identifier described above, the platform and the app version, so that our servers can address a notification to your device. We use it only to deliver the notifications you asked for, such as a reply to a support or safety report and occasional service messages about EQkey, and to keep the registration current when you sign in or out. A push token identifies the app installation, not any content: we never put your keystrokes, drafts, AI suggestions or message text into a notification payload. You can turn notifications off at any time in EQkey's Settings or in your device's notification settings for EQkey, and we then stop sending notifications to that device. Delivery is provided by Apple or Google as described under Service providers and disclosures.

Usage analytics

EQkey counts required AI usage and, while usage analytics is on, may send allowlisted events such as app launch, sign-in method, successful AI replies, persona use, and suggestion counts, positions or lengths. Firebase may also generate its own lifecycle, session, engagement, device and technical analytics events while usage analytics is on; Firebase's automatic screen-view reporting is disabled. These events do not include your keystrokes, message text or drafts. Separately, while usage analytics is on, Microsoft Clarity records session replays and heatmaps of the app's own screens, as described below.

• Backend counters (required): AI usage counts are always sent to our API to apply free usage limits and membership benefits.
• Firebase Analytics (included in the service, on by default): accepting the User Agreement includes usage analytics. You can turn Share usage analytics off in Settings at any time and continue using EQkey either way. Turning it off stops future collection. Firebase Analytics is not present in the keyboard extension at all.
• Microsoft Clarity (included in the service, on by default): runs while the same usage-analytics setting is on. It records session replays and heatmaps of the app's own screens — taps, scrolling and navigation — together with technical data such as your IP address, device and app version and, on Android, the advertising ID. Masking is set to Strict, so text and images in those replays are masked, and input-box content is masked by the SDK in every masking mode; on iOS the IDFA is never sent. These replays cover the app's own screens. On iOS, Clarity is not included in the keyboard extension at all; on Android, recording uses Strict masking, which masks all text, images and input-box content.
• AppsFlyer attribution (included in the service, on by default): runs while the same usage-analytics setting is on and stops when you turn Share usage analytics off (the one exception, iOS's own SKAdNetwork install and conversion report, is explained under Service providers and disclosures below). What AppsFlyer receives is described there.

On-device keyboard personalization

After the app has confirmed that you are 18 or older, EQkey may update an on-device model from ordinary English words you accept and from adjacent-word counts. This is used only to rank local keyboard suggestions. EQkey does not learn from password or other secure fields, does not include these words in usage analytics, and does not upload the model to our API. The model is isolated by credential identity and is cleared or made inaccessible when the identity changes, the account is deleted, or the eligibility gate is no longer satisfied. Uninstalling the app also removes the model because EQkey excludes it from backup and device transfer.

3. Information EQkey does not access for its service

EQkey does not request direct access to your contacts, precise location, calendar, microphone, camera or health data, and it does not upload a standalone avatar. Photo-library access is limited to the image features described above: only the iOS keyboard’s Read/Rizz feature asks for it, and only images you choose are uploaded. As explained above, a complete Firebase ID token used for optional sign-in may nevertheless contain the identity provider's profile-photo URL claim, which is sent to Surgelit's API as part of that authentication token.

Operating systems protect secure password fields from third-party keyboards. EQkey does not attempt to bypass those protections.

EQkey currently displays no advertising inside the app. On Android, the AdServices (Privacy Sandbox) permissions are removed and Firebase Analytics advertising-ID collection stays disabled; the Advertising ID is used for the attribution measurement and session-replay analytics described above, which includes measuring and optimizing EQkey’s own advertising on advertising networks as described under Service providers and disclosures. On iOS the IDFA is never read and EQkey does not request App Tracking Transparency. We do not sell personal information.

4. Why iOS asks for Full Access

Apple prevents a third-party keyboard from using the network unless the user enables Allow Full Access. EQkey needs network access for the AI features and for session and account functions used by the keyboard.

Without Full Access, EQkey continues to provide ordinary keyboard input and local keyboard functions. Network-based AI features are unavailable. Clipboard content is accessed only as part of a Reply action you start — when you open the Reply panel or tap paste — and it leaves your device only if you go on to submit that request.

You can turn Full Access off at any time in iOS Settings > General > Keyboard > Keyboards > EQkey.

5. How we use information

We use information to:

• generate the reply, rewrite or opener you requested;
• personalize suggestions using the persona, relationship and intimacy settings you selected;
• authenticate users and maintain guest or signed-in sessions;
• enforce free usage limits;
• operate, secure and troubleshoot the service;
• review reports, respond to support requests and improve safety;
• send you the notifications you asked for — for example, a reply to a support request — when notifications are turned on;
• comply with law and enforce our Terms of Use.

Where applicable, our legal bases include performance of a contract, your consent, compliance with legal obligations, and our legitimate interests in operating and securing EQkey. You may withdraw consent where consent is the basis, without affecting earlier processing.

6. Service providers and disclosures

We use service providers to operate EQkey. Depending on the feature you use, these may include:

• AI processing providers, which process the content and settings submitted for an AI request on our behalf and only to generate the requested output. We do not authorize these providers to use your content to train their own models or for advertising;
• cloud hosting and infrastructure providers, which host our API and databases in the United States;
• Google, Firebase and Apple, which provide optional authentication and platform services, including delivery of push notifications through Firebase Cloud Messaging (on Android) and the Apple Push Notification service (on iOS) when notifications are turned on; Firebase Analytics receives usage events while the usage-analytics setting is on;
• AppsFlyer, our mobile attribution and install-fraud prevention provider. It runs only while the Share usage analytics setting is on: it is included in the service and on by default, and turning the setting off in Settings stops it. The one exception is on iOS: Apple's privacy-preserving ad attribution (SKAdNetwork) is operated by iOS itself and may send AppsFlyer an anonymous install and conversion report that contains no user or device identifier, whether or not the setting is on. AppsFlyer receives install and session events, the allowlisted usage events described under Usage analytics, an app-level attribution identifier it generates, your guest or account identifier, your IP address, device model, operating-system version and app version and, when you subscribe to EQkey+, a subscription event with the price and currency charged (never your payment-card details), so that we can understand where installs and subscriptions come from and detect fraudulent installs. When we advertise EQkey on an advertising network, such as TikTok, Meta or Google, AppsFlyer also shares install events and selected in-app events, such as subscription events, with that network so that it can measure our campaigns and optimize the delivery of our ads. On Android these events can include the advertising ID. Turning Share usage analytics off stops this sharing; the iOS SKAdNetwork report described above is handled by iOS itself. The SDK is not included in the keyboard extension and does not receive your message text, drafts or AI suggestions. On iOS, EQkey uses AppsFlyer's Strict SDK build, which never reads or sends the IDFA and does not request App Tracking Transparency. On Android, EQkey uses the standard AppsFlyer SDK, which reads the advertising ID; you can limit or reset it in system privacy settings;
• Microsoft (Clarity), which provides the session-replay and heatmap service for the app itself while the usage-analytics setting is on, using the data described under Usage analytics;
• Apple App Store and Google Play, which distribute EQkey and process payments for EQkey+ subscriptions. We receive the purchase verification and subscription status needed to activate and maintain your membership, and never receive your payment card details.

These providers process information to perform services for us or as otherwise disclosed to you by their own permission and privacy notices. Apart from the advertising measurement and optimization described for AppsFlyer above, we do not authorize providers to use EQkey data for advertising.

We may also disclose information when required by law, to protect users or the public, to investigate fraud or abuse, or as part of a merger, financing, acquisition or sale of assets subject to appropriate safeguards and notice where required.

We do not sell personal information.

7. Data retention

We keep personal information only as long as needed for the purposes described in this policy, and we apply the following retention periods:

• AI request content is processed to generate your response. Request and response text may appear in service logs used for security, abuse prevention and troubleshooting; those logs are retained for no more than 30 days and then deleted. We do not use AI request content to build advertising profiles. Images you choose for an AI feature are processed in memory to complete the request and are not stored; text recognized from them is treated as AI request content under this section.
• API and security logs, which may include IP address, request metadata and response status, are retained for no more than 90 days, unless a specific security investigation or legal obligation requires a longer period.
• Account and profile information is kept while your account or guest session is active, and is then deleted or anonymized in accordance with applicable law, except for limited records we must keep to comply with law, resolve disputes or enforce our agreements.
• Support and safety reports are retained as needed to resolve the issue and as permitted or required by applicable law.
• Push notification tokens are kept only while the registration is active. Signing out, deleting your account or guest data, or turning notifications off invalidates the registration, and invalidated or no-longer-deliverable registrations are deleted within 90 days.
• Purchase records, such as the store transaction identifier, purchase token and subscription status, are retained while your subscription is active and afterwards for the period needed to handle renewals, cancellations, refunds and disputes, and to meet tax, accounting and other legal obligations.

We do not keep full payment card details.

8. Security and international processing

EQkey uses HTTPS/TLS to protect information in transit. We also use access controls and operational safeguards designed to protect information against unauthorized access, alteration or disclosure. No system can guarantee absolute security.

Surgelit is based in the United States. Our service providers and infrastructure process information in the United States, which may have different data protection laws from your country. Where required, we use appropriate transfer safeguards.

9. Your choices, account deletion and privacy rights

Stop AI text processing

Do not tap an AI action. You can continue using the keyboard for ordinary typing. On iOS, you can also disable Full Access. On either platform, you can remove EQkey as an enabled keyboard or uninstall the app.

Turn notifications off

Notifications are optional and off by default. If you turned them on, you can turn them off in EQkey's Settings or in your device's notification settings for EQkey. Turning them off invalidates the push registration for this device, so we stop sending notifications to it.

Delete a signed-in account

Open EQkey and go to Settings > Account > Delete account. The entry stays available even if profile loading fails. After confirmation, we delete or anonymize your account and associated data in accordance with applicable law, except for limited records we must keep to comply with law. Deletion cannot be undone. Deleting the account also invalidates any push notification registration for this device, so we stop sending notifications to it.

Deleting an EQkey account does not automatically cancel an EQkey+ subscription. If you have an active subscription, cancel it in your App Store or Google Play subscription settings first, then delete the account.

Delete guest data or request deletion without the app

You can request deletion without reinstalling the app by emailing [email protected]. If the request concerns a signed-in account, include the account email. For guest-data requests, we may ask for information reasonably necessary to locate and verify the session. We will process verified deletion requests in accordance with applicable law. Deleting guest data likewise invalidates the push notification registration associated with that guest session.

Other rights

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, obtain a portable copy, or appeal a decision about your request. You may also have the right to complain to a data protection authority.

Send requests to [email protected]. We may need to verify your identity before completing a request. We will respond within the period required by applicable law and will not discriminate against you for exercising a privacy right.

California residents may request information about categories of personal information collected, sources, purposes and disclosures. EQkey does not sell personal information. As described in Section 6, event data may be shared with advertising networks to measure and optimize our own advertising; you can stop this at any time by turning Share usage analytics off in Settings.

10. Children

EQkey is intended only for people aged 18 or older. We do not knowingly collect personal information from children. If you believe a person under 18 has provided information to EQkey, contact [email protected] so we can investigate and delete it where appropriate.

11. AI-generated content

AI suggestions may be inaccurate, inappropriate, biased or unsuitable for a conversation. Review and edit every suggestion before sending it. You are responsible for the message you choose to send.

You can report inappropriate AI content inside EQkey at Settings > Support > Report keyboard content. Reports help us investigate safety issues and improve safety controls.

12. Changes to this policy

We may update this policy when EQkey, our providers or legal requirements change. We will change the Last updated date and provide additional notice in the app when required.

13. Contact us