Privacy Policy

Last updated: 27 July 2026 · Effective: 27 July 2026

1. Who we are

"Keyda", "we", "us" and "our" refer to the operator of the Keyda keyboard application for iOS, iPadOS and Android, the Keyda app for Mac, the Keyda browser extension, the keyda.in website, and accompanying services (the "Service"). If you have questions about this policy, contact us at support@keyda.in or via the Contact page.

For privacy, data-protection, account-deletion, and grievance requests, email support@keyda.in with the subject line Privacy Request — Keyda. We use that inbox as our privacy and grievance contact point.

2. What we collect

2.1 Account data

When you sign up with phone OTP, Sign in with Apple, or Google/Facebook (if enabled), we receive a stable provider identifier and, where you consent, your email, display name and phone number. We also generate a device identifier for your installation.

2.2 User content (scoped per account)

Keyda stores the following user content, always scoped to your authenticated user id:

• Notes you save through the keyboard's "Save as note" action — stored on our database in the user_notes table.
• Clipboard history — kept locally on your device only (App Group storage). Never uploaded.
• Stickers, image-gen outputs, document summaries, response history — kept locally on your device only.
• Profile photo, display-name override, and bio — stored locally only. The bio is sent to the AI provider as part of a prompt when you fire an AI call so the model can personalise its reply; it is never uploaded to our servers.
• AI Memory (opt-in) — when you enable "Remember conversation context" in Settings, a per-text-field SQLite database is created in your App Group container. It stores prompt/response pairs and a rolling summary so the AI stays coherent across multiple calls. Entries older than 30 days are auto-pruned. The database lives only on your device — we never see it. "Forget everything" in Settings drops every row in one tap.
• Preferences like theme, preferred language, keyboard feature toggles, AI Memory opt-in, and BYOK opt-in — stored locally; selected preferences sync to the server for cross-device continuity.

2.3 Subscription & trial state

The trial is opt-in: you must tap "Start Free Trial" inside the app. We then create a user_subscriptions row with status trialing, a 3-day window, and a 100-AI-use cap. We track:

• Trial start time, current period end, AI uses consumed, AI uses cap.
• Whether you converted the trial into a paid plan and when.
• Subscription transitions (active → canceled → expired) on conversion.

When you have no active trial or paid plan, our backend returns a synthetic "no plan" entitlement (Cloud AI locked client-side) — no row is created until you tap Start Trial or purchase.

2.4 Bring-Your-Own-Key (BYOK) credentials

Using your own AI provider API key requires no paid plan. If you choose to add one, we store it encrypted (AES-256-GCM) in our database tied to your user id, so that it is available on your other signed-in devices. It is decrypted only to return it to your own app; we do not use your key to make AI calls on our servers. You can delete any stored key from the app at any time, which removes it from our database.

Where a BYOK request goes. When Keyda answers using your key, the app on your device sends the request directly to the provider you selected (for example OpenAI, Anthropic, Google, Groq or xAI). It does not pass through Keyda's servers, so we do not see, log or store the prompt or the response for those calls, and they do not appear in the AI request logs described in section 2.5 or in your in-app usage statistics. That request is governed by the privacy policy and terms of the provider whose key you used, and is billed to you by that provider. Requests that use Keyda's AI pool instead — which requires a paid plan or an active trial — do pass through our servers and are logged as described in section 2.5.

2.5 AI request logs

Each AI request you trigger (correction, rephrase, smart-assist, etc.) is logged with: provider, model, prompt, result, latency, success/failure, and your user id. These logs power usage analytics and your in-app "Token utilization" stats. Prompts and results are not shared with anyone outside the Service, and are not used to train any AI model.

Reading links you ask about. When you paste a web link and ask Keyda about it, our server fetches that publicly accessible page, extracts its text, and includes it in your AI request so the model can answer (for example, to summarise it). In the app, a small number of links that the page directly references may also be fetched; in the keyboard only the single page you paste is read. We fetch only the link you provide — we do not crawl the web or track your browsing — and the fetched text is processed exactly like any other prompt described above. This feature is on by default and can be turned off in Settings.

2.6 Subscription and payment data

When you purchase a Lite or Pro plan through the app, the transaction is processed by the Apple App Store (iOS) or Google Play (Android). We record the store-issued purchase identifier (such as the Apple original transaction id or Google purchase token), the product/plan code, billing period (monthly or yearly), and the purchase, renewal and expiry dates and status, which we validate against Apple's or Google's servers to keep your entitlement in sync. Your card, UPI, bank and other payment-instrument details are handled exclusively by Apple and Google — we never see or store them.

Web checkout (keyda.in/subscribe). If instead you buy a one-time period directly on our website, the transaction is processed by our payment partner Razorpay. To start that checkout, the app first asks our server for a short-lived, single-use code (valid ~60 seconds) that signs you into the web page without re-entering a password; the page never sees your account password. Razorpay collects your card/UPI/bank details directly — we never see or store them. We store the order id, payment id, amount, currency, plan code and billing period, and status (created/paid/failed) for that transaction, and use it to activate your Lite/Pro entitlement for the period you paid for.

2.7 Telemetry & activity events

To diagnose issues and improve reliability we log activity events like sign-in, app foreground/background, theme change, and aggregated counts (e.g. characters corrected). These events are tied to your user id but do not contain the text you typed.

2.8 Voice & speech data

If you use the voice typing / voice assistant feature, Keyda accesses your microphone only while you are actively recording — you start it by tapping the mic, and it stops automatically after a short pause. Keyda never listens in the background. On iOS, Apple's platform rules prohibit third-party keyboards from accessing the microphone at all — a security restriction that applies to every keyboard on the system, not only Keyda. To comply with it, the recording is performed by the Keyda app, which transcribes your speech and hands only the resulting text back to the keyboard; the keyboard extension itself never touches the microphone. (On Android, where the platform permits it, recording happens within the keyboard, but the same data handling described below applies.)

• Transcription: audio is converted to text by Apple's Speech Recognition framework — on your device where the language supports it, otherwise by Apple-hosted speech services under Apple's privacy policy. Keyda does not store or upload the raw audio.
• Transcripts: the recognised text is saved to a private, per-user voice history stored on your device (so features like undo work). Syncing that history to your Keyda account is off by default and only occurs if you enable it in Settings → Voice; you can clear it at any time.
• Voice commands & AI: if a phrase is an AI request, the transcribed text (not the audio) is sent to your chosen AI provider exactly like a typed AI request (see 2.5).

2.9 Website analytics (keyda.in)

Our marketing website keeps a simple, first-party visit log so we can see how many people reach the site and which pages and download buttons they use. For each visit we record the page path, referrer, any UTM campaign tags, your device/browser type, your IP address, and an approximate location (country, and where available region/city) that our server derives from that IP using an offline geo-IP database — there is no precise/GPS location, no location permission prompt, and no call to any third-party service. We use this only in aggregate to understand traffic and demand (for example, which platforms visitors choose to download from). This applies to the website only and is unrelated to anything you type in the keyboard. The log uses no cookies and no third-party trackers, and honours your browser's Do Not Track signal.

2.10 Browser extension

The Keyda browser extension (Chrome) adds spelling/grammar correction to text fields on websites you visit, and gives you access to your Notes, Documents and AI Sessions in the browser. It handles data differently depending on the feature:

• Sign-in. You sign in with Google or phone OTP, the same as the app (see 2.1). We receive a stable provider identifier and, where you consent, your email, display name and phone number.
• Spelling fixes — on-device only. The extension checks words you type against a dictionary bundled with the extension itself, entirely on your device. Misspelled words, and the word you click to fix, are never sent to our servers or anywhere else — this happens whether or not you're signed in for the underline, and requires sign-in only (no AI, no plan) for the one-tap fix.
• Sentence-level suggestions — sent to our servers. Unlike the mobile keyboard's AI features, which only activate when you tap something, the extension's fuller "Keyda suggests" correction runs automatically a short moment after you pause typing near a misspelling, without a separate trigger tap. When it runs, the text of the field you're currently editing is sent to Keyda's servers for grammar correction, rephrasing, or tone rewriting (processed the same way as the AI requests described in 2.5), then discarded from that request once a result is returned; usage is logged the same way other AI requests are (see 2.5). You can turn this off entirely in the extension's Settings, leaving only the on-device spelling fixes.
• Right-click actions. "Fix grammar," "Rephrase," and "Save selection to Keyda Notes" from the right-click menu send only the text you've selected, and only when you choose one of those actions.
• Preferences. Theme, feature toggles, and the position you've dragged the suggestion popup to are stored locally in your browser (not on our servers).
• The extension does not collect your browsing history, the URLs of pages you visit, or the content of any field you are not actively being corrected on.

2.11 Desktop app (Mac)

Keyda for Mac is a desktop version of the app: your Notes, Documents, Sketches, AI chats, and an in-app writing check inside Keyda's own editors, signed in to the same account and synced the same way as on mobile (see 2.1–2.6). It also offers one optional, desktop-only feature that needs a system permission, described here in full:

• System-wide Writing Check — off by default, opt-in. When you turn this on, Keyda asks for macOS Accessibility permission. Only while it is enabled and permission is granted, a small companion helper reads the text of the single field you are currently focused on in whatever app you are typing in, so it can underline misspelled words and offer a fix. This is entirely opt-in — it does nothing until you switch it on in Settings → System-wide Writing Check, and you can revoke the Accessibility permission at any time in System Settings → Privacy & Security → Accessibility.
• On your device only. The spelling and word-suggestion check runs on your Mac using Apple's built-in on-device spell-checker. The text of the field you're editing is not uploaded to our servers or sent anywhere for this feature — it is read locally to place the underlines and, if you click a highlighted word, to show a correction.
• Password fields are always skipped. The helper never reads secure/password fields, and it never runs in the background — it only looks at the field that currently has focus while the feature is enabled. It does not log your keystrokes, capture your screen, or read fields you are not actively editing.

2.12 Shared AI Sessions

You can invite up to 100 people into one shared AI chat (for planning, group study, teamwork). If you create or join a shared session:

• Who sees what. Every message sent in a shared session, and every AI reply to it, is visible to every other member of that session, along with a display name/avatar identifying who sent it. Members can see the full running conversation, not just their own messages.
• Whose quota it runs on. When a member asks the AI something in a shared session, the request is served using the session creator's subscription/quota, not the asking member's — the creator's plan and daily caps apply to the whole session.
• No personal context leaks in. AI replies inside a shared session never draw on any individual member's private notes, documents, AI Memory, or profile bio — only the shared conversation itself is used as context, so one member's personal data is never surfaced to the others through an AI answer.
• Retention. Shared session messages are stored on our servers (scoped to that session) for as long as the session exists. Any member can leave a session at any time; the creator can end the whole session, which removes it for everyone.
• Invitations. Session links let anyone who has the link join — treat a session link like an invitation you'd hand to a specific group, since Keyda cannot verify who ultimately opens it.

2.13 Connected workspaces (GitHub, Linear, Jira)

You can optionally connect a GitHub, Linear or Jira account so the Keyda assistant can answer questions about your work — "what's assigned to me?", "which pull requests are open?". Nothing is connected by default: each one requires you to authorise it explicitly in Settings → Integrations, and you can disconnect it in the same place at any time.

• What we store. The authorisation credential issued by that provider, encrypted (AES-256-GCM) and tied to your user id, plus the workspace or organisation name so we can show you what is connected. For GitHub we store no long-lived credential at all — a short-lived installation token (about one hour) is minted from our GitHub App when needed and cached encrypted. We never receive or store your password for any of these services.
• What we read, and when. Only at the moment you ask a question that relates to that service. For Linear and Jira: issues assigned to you, recently updated issues, your team/project list, and issues matching a term in your question. For GitHub: your connected repositories, recent commits, open pull requests, and — only when you explicitly trigger a code review — the changed files of the pull request or commit you selected. We do not bulk-export, mirror or continuously sync your workspace, and we do not read anything on a schedule or in the background.
• Where it goes. What we fetch is placed into the instructions accompanying your AI request and sent to the AI provider handling that request (see 2.5 and section 4) so it can answer you. That accompanying context is not stored in our AI request logs. The answer you receive is logged as described in 2.5, and may quote issue keys, titles, statuses or authors that appeared in it.
• Writes. Linear and Jira connections are read-only — Keyda does not create, edit, comment on, transition or delete anything in them. On GitHub, the only actions Keyda takes are ones you explicitly trigger: posting the results of an AI code review you requested onto that pull request or commit, and merging a pull request when you tap Merge.
• Other people's data. Issues and pull requests in a shared workspace may have been created by, mention, or be assigned to your colleagues. Keyda reads only what the account you connected can already see, and shows it only to you.
• Disconnecting. Disconnecting a workspace in Settings → Integrations deletes the stored credential from our database immediately. You can additionally revoke Keyda from the provider's own account settings (GitHub, Linear or Atlassian) if you want access withdrawn on their side too. Deleting your Keyda account removes these connections along with the rest of your account data.

2.14 Image generation (Image Studio)

Image Studio turns a written description into a picture. It runs on our servers, not on your device, so the following leaves your device when you generate an image:

• Your prompt. The description you type. By default it is first rewritten into a fuller prompt by a text model so the picture matches what you meant; you can switch this off with Refine image prompts in Settings, in which case your wording is sent unchanged.
• Reference images you attach. If you attach one of your own photos for the model to work from, that image is uploaded with the request. This is the one place Keyda sends a picture from your library off your device, it happens only for an image you pick yourself, and only for that one request. We do not scan, index or upload your photo library.
• The image you get back. Images you create are stored on our servers against your account, so your gallery survives reinstalling the app, switching device, or signing out and back in. They are private to your account and are not shown to anyone else.
• Where it is processed. Your prompt and any reference image are sent to the image-generation processor named in section 4, which runs the model that draws the picture. We do not use your prompts, your reference images or your generated images to train any AI model.
• Deleting. Deleting an image or a whole session in the app deletes it from our servers as well, including the stored image file. Deleting your account removes all of them.
• Allowances. We keep a count of how many images you have generated in the current month so your plan's allowance can be applied (see our Terms). That is a number — it is not a copy of your images.

2.15 Location (app & keyboard)

Some things you can ask Keyda depend on where you are — "salons near me", or a bare "weather". Answering those needs a position, so:

• Only after you allow it. Your device location is read only if you grant the operating-system location permission, and only when you use a feature that needs it. You can withdraw that permission at any time in iOS or Android settings, which stops this completely.
• What we store. Your most recent position only — latitude, longitude, the accuracy figure the platform reports, and whether the fix came from GPS, the network, or was entered by you. It is a single row tied to your account, and each new fix overwrites the previous one. We keep no location history and cannot reconstruct where you have been.
• Who receives it. To answer a "near me" or weather question, the coordinates and your search term are sent to the mapping and weather services listed in section 4. They receive coordinates and a search term — not your name, email or account id.
• Deleting. The stored fix is deleted with your account. Revoking the OS permission stops any new fix being recorded.

2.16 What we never collect

• On the mobile keyboard: the text you type outside features you explicitly trigger. On the browser extension: any text beyond the field you're actively being corrected on, or a selection you explicitly acted on (see 2.10) — spelling fixes there never leave your device at all.
• Passwords, OTP codes after verification, or your contacts. We never scan, index or upload your photo library — the only pictures that leave your device are ones you deliberately attach yourself (a reference image in Image Studio, or a photo you add to an AI chat); see 2.14.
• Background screen activity, background or always-on microphone audio, and any location fix taken in the background or without the permission you granted — location is read only while you are using a feature that asks for it, and no location history is kept (see 2.15). Our website separately derives only an approximate city/country from your IP address, with no GPS and no permission prompt — see 2.9.
• On the Mac app's optional System-wide Writing Check: password/secure fields, background activity, your screen, or any field you are not actively focused on — and none of the text it checks leaves your device (see 2.11).
• Raw voice recordings — only the transcribed text, and only as described in 2.8.
• Your browsing history or the URLs of pages you visit, from the browser extension.
• From a connected GitHub, Linear or Jira workspace: anything the account you connected cannot already see; anything on a schedule or in the background; or any bulk copy of your issues, repositories or pull requests (see 2.13).

3. Why we collect it

Where privacy law requires a specific legal basis, our basis may include performance of a contract, consent, compliance with legal obligations, legitimate interests, or other permitted uses depending on the jurisdiction and feature involved. You may withdraw consent for optional features at any time by turning the feature off, clearing its data, or contacting us.

4. Who we share it with

We use a small number of processors strictly to deliver the Service. None of them are sold or rented your data.

• Apple & Google — app-store subscription purchases are processed by the Apple App Store or Google Play, which act as merchant of record and handle your payment details directly under Apple's and Google's privacy policies.
• Razorpay — if you buy a subscription through our web checkout at keyda.in/subscribe, Razorpay processes that payment and handles your payment details directly under Razorpay's privacy policy.
• AI providers you choose (Groq, OpenAI, Anthropic, Google, xAI) — receive your prompt and any model parameters when you trigger an AI request. We never share data with a provider you have not chosen.
• Apple — App Store, Sign in with Apple, and Speech Recognition (used to transcribe your voice input when on-device recognition isn't available), governed by Apple's own privacy policies.
• GitHub, Linear and Atlassian (Jira) — only if you connect one of those accounts (see 2.13). We call their APIs on your behalf to read the work items needed to answer your question, under GitHub's, Linear's and Atlassian's own privacy policies. We send them no personal data beyond the authorisation you granted and the query needed to fetch your own items.
• Replicate — runs the image-generation model behind Image Studio. When you generate an image it receives your prompt and any reference image you attached, under Replicate's own privacy policy and its model providers' terms. It does not receive your name, email or account id. Prompt refinement, when enabled, goes to one of the AI providers listed above.
• Open-Meteo — weather and place-name lookup. Receives coordinates or a place name when you ask about the weather.
• OpenStreetMap (Overpass API) — nearby places. Receives coordinates and the category you searched for when you ask something like "salons near me".
• Wikipedia, dictionaryapi.dev, Frankfurter and Nager.Date — the reference lookups behind definitions, currency conversion and public-holiday answers. Each receives only the term, currency pair or country in your question. None receives anything identifying you.
• Cloud hosting and database — our servers run on commercial hosting infrastructure under standard data-processing terms.

We do not sell your personal data, and we do not run third-party advertising or behavioural-tracking SDKs.

5. How long we keep it

• Account data: until you delete your account.
• Notes & subscription records: for the lifetime of your account; longer if required for tax or accounting compliance (typically 7 years for payment records under Indian law, which also applies to web-checkout order/payment records).
• Shared AI sessions: messages persist for as long as the session exists; ended by any member leaving (removes them from that session only) or the creator ending the session (removes it for everyone).
• AI request logs: rolling 12 months for analytics, then aggregated.
• Website visit logs (incl. IP & approximate location): rolling 12 months, then aggregated or deleted.
• BYOK keys: until you remove them or your account is deleted.
• Workspace connections (GitHub / Linear / Jira): the encrypted credential is kept until you disconnect that workspace or delete your account, and is deleted immediately when you do. The issues, pull requests and commits we read are not retained — they are used to answer that one request and then discarded.
• Activity events: rolling 90 days.
• AI Memory (device-only): auto-pruned 30 days after the last activity per conversation; "Forget everything" wipes the whole database in one tap. Sign-out wipes it too.
• Voice transcripts (device-only by default): kept in a capped on-device history; "Clear voice history" wipes it. If you opt in to cloud sync, the synced copy is removed when you clear it or delete your account. Raw audio is never retained.
• Profile photo, bio, and display-name override (device-only): kept until you change them, sign out, or uninstall.
• Generated images (Image Studio): kept on our servers, private to your account, until you delete the image or its session in the app, or delete your account — whichever comes first. Your monthly image count resets on the 1st of each calendar month (IST).
• Location: a single most-recent fix per account, overwritten by each new one and deleted with your account. No history is retained.
• Trial state: the trialing row is kept on our server permanently for fraud-prevention (we use it to enforce one-trial-per-user). It's automatically marked expired when it ends.

6. Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, restrict or object to certain processing, withdraw consent, appeal or complain, and appoint someone to exercise rights on your behalf where the law allows. To exercise any of these rights, email support@keyda.in. We respond within 30 days unless a shorter period is required by law.

Indian users may have rights under the Digital Personal Data Protection Act, 2023 (DPDP Act). EU/UK users may have rights under the GDPR/UK GDPR. California users may have rights under the CCPA/CPRA. We will not discriminate against you for exercising privacy rights.

7. Account deletion and data export

You can request account deletion or a copy of your account data by emailing support@keyda.in. Deleting your account removes or anonymises account-scoped content unless we must keep limited records for legal, tax, fraud-prevention, chargeback, security, or dispute reasons. Device-only data such as clipboard history, AI Memory, profile bio, profile photo and local voice history can also be cleared from the app or removed by uninstalling the app.

8. Children and minors

Keyda is not directed to children. You must be at least 13 to use the Service, and if you are under 18 you may use it only with consent from a parent or legal guardian where required. We do not knowingly collect personal data from children under 13. We also do not knowingly process children's personal data for targeted advertising, behavioural monitoring, tracking, or in a way that is detrimental to a child. If you believe a minor has provided us with personal data without the required consent, contact us and we will take appropriate steps to delete it.

9. Security

We use HTTPS everywhere, AES-256-GCM at-rest encryption for BYOK keys and for connected-workspace credentials, JWT-based authentication with short token lifetimes, and per-user data scoping so two accounts on the same device cannot read each other's content. We continuously monitor for vulnerabilities and apply security updates. No system is perfectly secure — please report any issue you discover to support@keyda.in.

10. International transfers

Our servers, infrastructure providers, app-store providers and AI providers may process data in countries other than the one where you live. Where required, we rely on applicable transfer safeguards, store-provider terms, processor commitments, and any jurisdictional restrictions that apply to the Service.

11. Changes to this policy

We may update this policy. Material changes will be announced in-app and on this page. The "Last updated" date at the top of this page reflects the current version.

12. Contact

Questions or requests? Email support@keyda.in or use the Contact form.