Privacy Policy

1. Scope

This Privacy Policy applies to:

• K-AI — the self-hosted desktop and server software you run on your own hardware.
• K-AI Cloud — our optional hosted service at cloud.getk-ai.com for account sign-in, sync, billing, and related features.
• Our websites — including getk-ai.com and related marketing pages.

When you run K-AI locally without linking to K-AI Cloud, most of your workspace data stays on your devices. This policy explains what we do and do not collect in each mode.

2. Information we collect

2.1 K-AI (local / self-hosted)

When you use K-AI on your own machine, we do not operate the application backend for you and we do not receive your chats, documents, email content, notes, files, or other workspace data by default.

• No product telemetry by default. The local app is designed to run without sending usage analytics to us.
• Sign in with Google (official desktop builds). If you create your local account with Google, OAuth runs between your device and Google. We store your Google account identifier and tokens on your device so the app can sign you in and, if you approve the requested permissions, connect Google services locally. If you also link the device to K-AI Cloud, an encrypted copy of those tokens is kept in K-AI Cloud so cloud agents can act for you. Kai Shade does not receive your chats, documents, email content, notes, or files through sign-in alone. See Section 3 for everything we do with Google user data.
• Optional K-AI Cloud during setup. If you choose to connect K-AI Cloud later in onboarding, the same email or Google identity may be sent to K-AI Cloud to create or link a cloud account — see Section 2.2.
• Your API keys and model providers. If you configure third-party AI or email providers, those services receive data according to their own policies — not through us unless you also use K-AI Cloud features described below.
• Optional connections. If you connect Google or other external services inside the app, those integrations exchange data directly between your instance and the provider you authorize. Google user data is handled only as described in Section 3.
• Updates. If you download releases from GitHub or our site, those platforms may log standard request metadata (IP address, user agent) under their own policies.

2.2 K-AI Cloud

If you create a K-AI Cloud account or link a device, we collect and process information needed to operate the service, including:

• Account information — email address, authentication identifiers, password hash (we do not store plaintext passwords), and profile settings associated with your account.
• Subscription and billing data — plan tier, subscription status, invoices, and payment metadata processed by Stripe. We do not store full payment card numbers on our servers.
• Synced and cloud-stored content — enabled sync categories are encrypted on your devices before they reach K-AI Cloud. We do not store the key with that copy, so a stolen database is not readable to us. Task schedules (title, schedule, instruction) and billing stay readable so cloud jobs can fire. When you unlock cloud agents, that job decrypts synced data in memory. A live unlocked job on our infrastructure is not invisible to us.
• Device linking — device identifiers, pairing tokens, and link status for desktops you connect to your cloud account.
• Usage and quotas — metered consumption such as included AI credits, cloud browser minutes, API call counts, and feature entitlements.
• Support and communications — information you send when contacting us at team@getk-ai.com.
• Logs — server logs that may include IP address, timestamps, request paths, error diagnostics, and security events.

2.3 Shopify stores you connect

If you install K-AI on a Shopify store, or connect a store from K-AI, we receive an access token for that store and the Admin API data needed to do what you ask in chat. That can include products, orders, customers, themes, and analytics. The token is stored with your K-AI Cloud account so the connection keeps working. We do not keep a separate customer database. Customer and order details can appear in chat on your account, which you control.

Shopify can ask us to confirm a customer data request, delete a customer, or delete a shop. We confirm those requests. Uninstalling the app, or a shop-deletion request, deletes the store access token. To get a copy or deletion of Shopify-related data in your K-AI account, email team@getk-ai.com. Shopify is a trademark of Shopify Inc.

2.4 Website visitors

Our marketing site may receive standard web server or CDN logs (IP address, browser type, pages viewed, referrer). We do not use third-party advertising trackers on getk-ai.com.

3. Google user data

This section covers data K-AI receives from Google APIs when you sign in with Google or connect a Google service. It overrides anything broader elsewhere in this policy. K-AI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3.1 What we access

K-AI only requests the Google permissions you approve on Google's consent screen. Depending on what you connect, that can include:

• Google account basics — your name, email address, profile picture, and Google account ID, to sign you in.
• Gmail — messages, threads, labels, and the ability to send, reply, draft, label, archive, and trash mail when you ask.
• Google Calendar — your calendars and events, and the ability to create and change events when you ask.
• Google Drive, Docs, Sheets, and Slides — file names and contents you open or search, and the ability to create and edit documents, spreadsheets, and presentations when you ask.
• Google Contacts and Workspace directory — names and photos, used to show who a person is in Gmail and Google Chat.
• Google Chat — the spaces and direct messages you belong to, their members and messages, and the ability to send messages when you ask.

3.2 How we use it

Google user data is used only to provide and improve the user-facing features you see in K-AI:

• Signing you in and showing which Google account is connected.
• Reading, searching, summarizing, drafting, and sending email, and organizing your inbox, when you ask in chat or from the mail view.
• Showing your schedule and creating or changing events.
• Finding, reading, creating, and editing Drive files, Docs, Sheets, and Slides.
• Reading and replying to Google Chat messages.
• Building your personal memory in K-AI (who you talk to and what you work on), which you can view, edit, and delete in the app.
• Running scheduled tasks and cloud agents that you set up to act on your Google account.

3.3 What we never do with it

• We do not sell Google user data.
• We do not use or transfer it for advertising, including personalized, retargeted, or interest-based ads.
• We do not transfer it to data brokers, information resellers, or ad networks.
• We do not use it to determine credit-worthiness or for lending.
• We do not use it, and do not let anyone we share it with use it, to develop, improve, or train generalized or non-personalized AI or machine-learning models.
• We do not use it for analytics, marketing, or any purpose unrelated to the features in Section 3.2.

3.4 Who we share it with

We transfer Google user data to others only when needed to provide or improve the features in Section 3.2, to comply with applicable law, for security purposes (for example, investigating abuse), or as part of a merger, acquisition, or sale of assets after we notify you. Specifically:

• The AI model you choose. When you ask K-AI to work with your email, calendar, files, or chats, the relevant content is sent to the AI model that answers you. With a local model it stays on your device. With a cloud model, your device sits in the middle first: detected cards, secrets, passwords, ID numbers, addresses, emails, and phone numbers are replaced with placeholders before the provider sees the request, and restored only after the reply comes back. The map stays on your device. See Section 5. With your own API key the request then goes to that provider under your account with them. With K-AI Cloud credits it then goes through OpenRouter. We do not keep the prompts.
• K-AI Cloud infrastructure. If you link a device to K-AI Cloud, encrypted tokens and any sync categories you turn on are stored with our hosting and database providers (including Supabase) so cloud agents and sync work. They store it for us and may not use it for anything else.

Google user data is not shared with Stripe, Deepgram, Shopify, or any other provider in Section 6.

3.5 Human access

No person at Kai Shade reads your Google user data, except when you ask us to for a specific message or file (for example, in a support request), when needed for security purposes such as investigating abuse, to comply with law, or when the data has been aggregated and anonymized for internal operations.

3.6 Storage, retention, and deletion

• Google tokens and the data K-AI caches from Google (such as calendar events and your memory entries) are stored on your device. Tokens are encrypted in K-AI Cloud when you link a device.
• Turning a single Google service off in K-AI Settings → Integrations stops K-AI from using it. Disconnecting your Google account there deletes its tokens from your device and from K-AI Cloud.
• Deleting your K-AI Cloud account deletes the cloud copy of your tokens and synced data.
• You can also revoke K-AI's access at any time from your Google Account permissions page.
• To have us delete any Google user data we hold, email team@getk-ai.com.

4. How we use information

We use collected information to do the following. Google user data is used only as described in Section 3.

• Provide, maintain, and improve K-AI Cloud and our websites.
• Authenticate users, link devices, and enforce plan entitlements.
• Process payments and manage subscriptions.
• Run cloud agents, sync, marketplace, and related hosted features you request.
• Monitor reliability, prevent abuse, and protect the security of our systems and users.
• Respond to support requests and communicate service-related notices.
• Comply with legal obligations.

We do not sell your personal information.

4.1 Legal bases (EEA, UK, and Switzerland)

• To provide K-AI Cloud (account, sign-in, sync, device linking, cloud agents, usage metering, support) — performance of our contract with you (GDPR Article 6(1)(b)).
• Connected services you ask us to act in (Google, Shopify, email) — performance of our contract with you, on your instructions.
• Billing and tax records — compliance with our legal obligations (Article 6(1)(c)).
• Security, abuse prevention, and server logs — our legitimate interest in keeping the Services and their users safe (Article 6(1)(f)).
• Product and marketing email — your consent (Article 6(1)(a)), or, if you are already a customer, our legitimate interest in telling you about similar K-AI products, which you can refuse in every message.

You need to give us an email address to create a K-AI Cloud account; without it we cannot provide Cloud. Everything else is optional. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

5. AI processing

K-AI sends prompts and context to AI model providers only when you (or an agent you configure) invoke those features. We do not use your content, including Google user data, to train AI models.

We do not treat a model’s Zero Data Retention badge as privacy. ZDR is a promise from the provider about what they will do with a prompt after they have already received it. The model still has to see the prompt to answer it. We cannot audit that promise, a provider can change it, and OpenRouter’s own ZDR stance still allows an implicit prompt cache and leaves tools and plugins out of scope. A badge is not a control we hold.

5.1 The middleman

When a request is headed to a cloud model, K-AI sits in the middle on your machine. A local bridge inspects the request before it leaves. Detected secrets and identifiers are swapped for stable placeholders. The map from placeholder to real value is encrypted and stored on your device. The model, and any provider in front of it, sees the placeholder. When the reply comes back — including a tool call that needs the real value — the same bridge puts the original back, on your machine. The provider never receives the map.

The same value keeps the same placeholder for that chat, so the model can refer to “that card” or “that address” without ever being given it. The chat shows a count of what was held back. You can open it and see a masked hint, not the value.

This is on by default. You can turn it off, and you can turn email and phone stripping off separately, in Settings. A model running on your own machine is not sent through the bridge. That request does not leave the machine, so there is nothing to strip.

5.2 What is replaced

• Cards — the number is replaced. The last four digits stay visible next to the placeholder, so a charge can still be told apart from another card.
• Secrets — API keys, bearer tokens, private keys, and similar credentials.
• Passwords — when they are labeled, or sitting in an environment variable or a URL. A bare password with no label next to it is not detected.
• ID numbers — passports, Social Security numbers, national IDs, and similar identifiers when they are labeled or match a known format. The last few characters can remain visible next to the placeholder.
• Addresses — street addresses, and lines labeled as an address.
• Email addresses — the local part is replaced. The domain stays, so work and personal mail are still distinguishable. You can turn this off.
• Phone numbers — the national number is replaced. The country code stays. You can turn this off.

5.3 What this does not do

• Names are not removed. The model still sees who you are talking about.
• The rest of the prompt still goes. The question, the body of an email once addresses and numbers are stripped, file text, and the rest of the conversation are sent. The bridge removes detected secrets. It does not make the whole conversation local.
• Pictures are not covered. An image sent to a vision model goes through as you sent it.
• Detection is a pattern, not a guarantee. A secret written in a form we do not recognize can still leave. Do not put something in a cloud chat if it must not be seen by that provider at all. Use a local model for that.

5.4 Where the request goes after the bridge

• Your own API key: after the bridge, the request goes to the provider on your account with them, under their policy.
• K-AI Cloud credits: after the bridge, paid completions are routed through our infrastructure to OpenRouter, and we ask for a Zero Data Retention endpoint where that catalog has one. That is a narrower retention setting on a hop we already do not trust. It is not the protection. Free catalog models are not ZDR; labs may train on them. We do not keep the prompts (no prompt previews in billing logs).
• Cloud speech-to-text: live cloud Call Listen audio is processed by Deepgram. The bridge does not apply to audio. Local Whisper is the path that does not send audio to a third party.

Do not submit information you are not permitted to share with us or with model providers.

6. Third-party services

We use service providers that process data on our behalf, including:

• Stripe — payments and subscription management.
• Supabase — authentication and cloud database infrastructure.
• Cloud hosting providers — infrastructure for K-AI Cloud.
• AI model providers — when you use a cloud model. The request passes through the local bridge in Section 5 before it leaves your device. K-AI Cloud credits route requests through OpenRouter, which passes them to a company that hosts the model you picked. Depending on the model, that company can be in the United States, the EU, China, or elsewhere. Paid K-AI Cloud credits also ask OpenRouter for a Zero Data Retention endpoint. That is a provider setting, not the protection.
• Cloudflare — hosts this website and serves its pages.
• Deepgram — only if you use cloud Call Listen speech-to-text.
• Google — only if you explicitly connect Google services (e.g. Gmail, Calendar, Drive) in the app.
• Shopify — only if you install K-AI on a Shopify store or connect one.

These providers are permitted to process data only as needed to perform services for us or for you, subject to their own privacy policies. Google user data goes only to the recipients listed in Section 3.4.

7. Data retention

• We retain K-AI Cloud account and synced data while your account is active and as needed to provide the service.
• Billing records are kept for as long as tax and accounting law requires (in Spain, up to six years).
• Server logs stay in our hosting provider's rolling log window and expire there. We do not copy them anywhere else.
• A Shopify access token is deleted when you uninstall K-AI from that store, when you disconnect the store in K-AI, or when Shopify asks us to delete that shop’s data.
• When you delete your K-AI Cloud account, its synced data, memory, files, browser runs, usage logs, connected-service tokens, and sign-in record are deleted at that moment. Copies in our database provider's backups expire on its backup schedule. We keep only billing records the law requires us to keep. Google user data is deleted as described in Section 3.6.

8. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export, or restrict processing of your personal information. In the EEA, the UK, and Switzerland you have the right to:

• get a copy of your personal data, and have it corrected or deleted;
• restrict how we use it, and receive data you gave us in a machine-readable format (portability);
• object to processing based on our legitimate interests, and object at any time to marketing;
• withdraw consent you gave, without affecting what we did before you withdrew it;
• complain to a data protection authority — in Spain the Agencia Española de Protección de Datos, or the authority where you live or work.

• Account settings — manage profile and connected services in the K-AI app or cloud dashboard where available.
• Data export — K-AI Cloud may offer export tools for account-associated data.
• Account deletion — you can delete your K-AI Cloud account from in-app cloud settings. Local data on your devices remains under your control.
• Marketing email — you may opt out of non-essential marketing messages by replying to unsubscribe or contacting us.

To exercise privacy rights, email team@getk-ai.com. We answer within one month, and may need to verify your identity before fulfilling a request.

9. Security

We use administrative, technical, and organizational measures designed to protect information, including encryption in transit (HTTPS/TLS), device-held sealed copies for enabled sync categories, access controls, and monitoring. We do not store the vault key with the sealed replica. Task schedules and billing stay readable so jobs can fire. Unlocking cloud agents decrypts synced data in process for that session; that live job is not operator-invisible. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

10. International transfers

K-AI Cloud may process and store information in the United States and other countries where we or our providers operate. When personal data leaves the EEA, the UK, or Switzerland for a country without an adequacy decision, the transfer relies on the provider's certification under the EU–US Data Privacy Framework or on the Standard Contractual Clauses in its data processing terms. Section 6 lists who receives data, and when.

11. Children

K-AI and K-AI Cloud are for adults: you must be 18 or older to use them (see our Terms). We do not knowingly collect personal information from anyone under 18. Contact us if you believe a minor has provided us information, and we will delete it.

12. Changes to this policy

We may update this Privacy Policy from time to time. We will post the revised version on this page and update the effective date. Material changes may also be communicated by email or in-product notice where appropriate.

13. Contact us

Kai Shade is the controller of personal data processed through K-AI Cloud and our websites. For K-AI you run yourself without Cloud, you control your own data.

Kai Shade
Email: team@getk-ai.com
Website: getk-ai.com

See also our Terms of Service.