Google API Services User Data Policy

How Kriya uses Google user data

Kriya can create a calendar event or draft an email for you — but only if you connect your Google account, and only for the request you just made. This page is our full disclosure of what we access, why, how long we keep it, and how you cut it off.

Effective: 26 July 2026 Last updated: 26 July 2026 App: Kriya AI Keyboard (com.kriya.keyboard)

Limited Use commitment

Kriya AI Keyboard's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

1. Connecting Google is optional

Kriya is a keyboard first. Typing, autocorrect, languages, themes and emoji all work with no account and no internet at all. Sign-in with Google is used only to create your Kriya account; connecting Gmail and Calendar is a separate, later, entirely optional step that you take only if you want the agent to draft mail or book meetings for you.

You can use Kriya forever without connecting anything, and you can disconnect at any moment without losing your account, your skills, or your keyboard.

2. Exactly which scopes we request, and why

We request the narrowest scope that makes each feature work. If a scope isn't listed here, we don't ask for it.

Scope	What it lets Kriya do	Why the feature needs it
`openid` `email`	Identify you and show which account is connected.	So the app can display "Connected as name@gmail.com" and file your tokens under the right account.
`calendar.events`	Create a calendar event (optionally with a Google Meet link), and list your upcoming events when your command asks for them.	"kal 4 baje meeting" has to become a real event. Reading upcoming events is what lets the agent answer "am I free Thursday?" and avoid double-booking. Restricted to events — Kriya cannot alter calendar settings, sharing or ACLs.
`gmail.compose`	Create a Gmail draft, and send an email after you tap Confirm.	Drafting a reply is Kriya's most-used action. This scope covers both drafting and sending, so we don't have to ask for a broader mail scope.
`gmail.readonly`	Read a message only when your own typed command requires it — e.g. "what did Rahul mail me?" or "reply to the last mail from my landlord".	The agent cannot answer a question about your mail without reading the specific message the question is about. This is demand-driven only — see §3.

What we deliberately do not request

No Google Drive. No Docs or Sheets. No Contacts. No Photos. No Tasks. No Chat. No Cloud Storage. No account-management or admin scopes. Even if a Kriya access token were somehow stolen, it could not reach any of them.

3. How we use Google user data

Google user data is used for exactly one thing: performing the action you just asked for.

Demand-driven only

The agent touches Gmail or Calendar only in service of a command you typed in that moment. There is no background sync, no polling, no scheduled job, no inbox mirror, and no copy of your mailbox anywhere in our systems. If you never ask, we never look.

Confirm-gated writes

Every write — an event, a draft, a sent email — shows you the exact content first and waits for your explicit Confirm tap. Nothing is created, sent or booked automatically. This is a hard product rule, not a setting.

Read, answer, discard

When the agent reads a message to answer you, that content is used for that one reply and is never written to our database or logs. It is also fenced as untrusted content, so text inside an email cannot issue instructions to the agent.

Never for anything else

Not for advertising. Not for profiling. Not for training AI models. Not for market research. Not sold, ever, to anyone.

4. The four Limited Use rules, answered directly

Google's policy sets four requirements for apps handling restricted scope data. Here is our position on each, in plain terms.

Requirement	How Kriya complies
1. Limit use to providing or improving user-facing features that are prominent in the app's interface	Google data is used only for the Gmail and Calendar features the user explicitly invokes — creating an event, drafting or sending mail, or answering a question about their own mail. These are the visible, advertised features of the app.
2. Do not transfer the data except as necessary to provide or improve those features, to comply with law, or as part of a merger with user notice	The only transfer is to Google's own Gemini API, as our AI sub-processor, and only the specific text needed to answer the request. We do not sell, rent or share Google user data with any other party, data broker or advertiser.
3. Do not use the data for serving advertisements	Kriya contains no advertising SDK at all and shows no ads of any kind. Google user data is never used for advertising, personalisation or audience building.
4. Do not allow humans to read the data unless the user consents for specific messages, it is necessary for security or legal compliance, or the data is aggregated and anonymised	No employee, contractor or developer reads your Gmail or Calendar data. Our logs record method, path, status, duration and a hashed user reference only — never request bodies, never message content. The one exception permitted by the policy: if you explicitly send us a message during a support request, or if a specific security or legal obligation compels it.

Model training: Google user data obtained through these scopes is never used to develop, improve or train generalised AI or ML models — neither ours nor anyone else's.

5. What we store, and for how long

Item	Stored?	Detail
Your OAuth access & refresh tokens	Yes	One row per user per provider, encrypted at rest with an application-level key. Never returned by any API — the app and the keyboard only ever see the words "connected as name@gmail.com". Deleted the moment you disconnect or delete your account.
Your Google email address and display name	Yes	Your account identity, so you can sign in on a new phone and find your skills.
Email bodies, subjects, sender lists	No	Read in memory to answer your request, then discarded. Never written to our database or logs.
Your mailbox, or any copy or index of it	No	There is no sync, no mirror, no cache, no search index of your mail anywhere in our systems.
Calendar event contents	No	Read on demand to answer you; the events the agent creates live in your Google Calendar, not in ours.
Contacts, attachments, files	No	We never request access to them in the first place.
Action receipt	Partially	So your History screen can show "created a calendar event" we keep roughly the first six words of your command and a short result preview. It expires on the retention schedule you choose — 24 hours, 7 days, 30 days, or never. It is not the message content.

Only Google's Gemini API, acting as our AI sub-processor, and only the specific text needed to fulfil the request you made. Under the Gemini API terms, paid API content is not used to train Google's models. Nobody else receives Google user data from us — no analytics provider, no advertiser, no data broker, no other user of Kriya.

We would disclose data only if compelled by valid Indian legal process, and we will tell you when we are legally permitted to.

7. AI processing of Google data

When your command needs Gmail or Calendar, the relevant text is sent to the Gemini API to generate the draft, the summary or the event details, and the result is streamed straight back to your keyboard. Content returned by Google APIs is wrapped in an untrusted-content fence, so instructions hidden inside an email cannot redirect the agent into doing something you did not ask for. The full prompt and full response are not saved.

8. Security controls

Encrypted in transit — HTTPS/TLS everywhere.
Encrypted at rest — the database is encrypted by our host, and OAuth tokens carry a second layer of application-level encryption on top.
Tokens never leave the server — no token is ever sent to the app or the keyboard.
Bound to a verified identity — the OAuth flow embeds your verified user ID in a signed, 10-minute state parameter, so a token can only ever be filed under the account that started the flow. Every later lookup uses the ID from your cryptographically verified sign-in token, never anything the client sends. There is no code path where one user's request can reach another user's Google account.
Least privilege — only the four scopes in §2.
Lazy refresh — tokens are refreshed only just before a call that needs one.
No content in logs — method, path, status, duration, hashed user reference. Nothing else.
Sensitive fields disabled — in password and OTP fields the keyboard disables the agent, network features and clipboard entirely.

9. How to revoke access

Two ways, both immediate, and you don't need us for either:

In the Kriya app

Profile → Connected apps → open the Google card → Disconnect. This revokes the token on Google's side and deletes our encrypted copy.
From your Google Account, directly

Go to myaccount.google.com/permissions, find Kriya AI Keyboard, and choose Remove access. Kriya loses access instantly.

After revoking, Kriya's Gmail and Calendar features simply stop working. Your account, your skills and your keyboard are unaffected, and you can reconnect any time.

10. How to delete the data

Disconnecting (§9) deletes the stored tokens. To remove everything we hold about you — account, profile, skills, history and all connected-app tokens — delete your account: it revokes every connected provider on their side first, then cascade-deletes every row of yours.

Delete your account & data → Full Privacy Policy

Emails, drafts and calendar events that the agent created for you remain in your Google account — they are yours, and you delete them from Gmail or Calendar as you would anything else.

11. Contact

For any question about how Kriya handles Google user data, including security disclosures:

👤Developer & Grievance OfficerHarshad Salunke
✉️Emailharshadsalunke2002@gmail.com
📱Call / WhatsApp+91 93599 78498
📍LocationMaharashtra, India