Privacy Policy

Last updated: 24 October 2026

This policy explains what personal data Zokie collects through the Zokie desktop app and the website zokie.dev (together, the “Service”), how we use it, and the choices you have. “Zokie”, “we” and “us” mean Zokie, which builds and operates the Service.

The short version: Zokie is a desktop app. Your code and files stay on your computer. On a paid plan, Zokie backs up your tasks and chats to its cloud so you can restore them, share them with your team and use them from your phone. The app and website send a few product analytics events to Mixpanel, never your code or what you type, and you can turn them off. When you sign up, we keep your name, email and profile picture so we can invite you, and Razorpay handles payments without us seeing your card. The AI tools you connect, such as Claude Code and Codex, send data to their own providers under your own accounts.

1. Personal data we collect

Your account

You sign up with Apple, with GitHub, with Google, or with your email address and a one-time code we email you. With GitHub or Google we receive your name, email address and profile picture from that provider, plus an identifier for your account there. With Apple we receive only your name and email address, plus an identifier; if you choose to hide your email, Apple gives us a private relay address that forwards to you, and your real address stays with Apple. We never receive your Apple, GitHub or Google password. Your account is kept by Zokie’s own sign-in service, in Zokie’s database on Amazon Web Services in Hyderabad, India. There are no passwords to keep: you always sign in through Apple, GitHub, Google or an emailed code. Alongside your account we keep its status (active or deleted, and requested or invited for accounts made while Zokie was invite only), the date each of those happened, and a count of wrong invite codes tried, which stops code guessing. If you are one of the first people on Zokie, your account shows a Founding Builder badge, worked out from when you signed up; we store nothing extra for it.

At zokie.dev/account you choose a display name and a handle. The theme and quiet hours you set in the app are saved with your account settings.

Invite codes

Anyone can sign up without an invite code. A code only lowers the price of Zokie Pro, or gives Pro for free, and the people who run Zokie make them. When they email a code, we use the address once, to send that email through Resend, our email provider, and we do not keep it (Resend keeps its own delivery records). The email carries the sender’s first name and the code. Each code is kept with the account that made it. If you redeem a single-use code, its maker sees your first name and when you redeemed it, and we email them that it was used.

While Zokie was invite only, people could ask for an invite with only their email address at zokie.dev/join, without making an account. We keep those addresses, the date each was left and the date we emailed it, and use them only to email that person about Zokie; the people who run Zokie see the address for this. They are not linked to any account, and nobody can add a new one.

Teams

If you create or join a team, its name, address and logo, and each member’s role, are kept by Zokie’s sign-in service. Every member of a team sees the other members’ names, email addresses, profile pictures and roles, and the email addresses of people invited to it. A team’s owners and admins also see whom the team pays for and whether each member already pays for Pro of their own, so nobody pays twice. Members on Pro, their own or paid for by the team, also share one board: each of them can see the team’s tasks, chats, cards and costs, and which kind of device last updated each task. Team owners get an email when someone joins.

Payments

Paid plans are billed by Razorpay. You enter your card, UPI or bank details, email and phone number on Razorpay’s own page; we never see or store them. We keep your subscription’s Razorpay ids, plan, seats, status and billing dates, and for a team which of its members its seats cover and when each seat started and ended, and we give Razorpay your Zokie account id so a payment can be matched to your account. Razorpay sends you payment receipts, and your invoices are Razorpay’s. The website reads your browser’s time zone to show Indian or international pricing.

Emails we send

Through Resend we send: a welcome email when you sign up, invite code emails the people who run Zokie ask us to send, a note when someone redeems your code or joins your team, and team invitations. Our emails load their fonts from Google Fonts when you open them.

Data you send us by email

When you email us for support or feedback, we receive your email address, your name if you include it, and whatever you write in the message.

Data collected when you visit zokie.dev

The website runs on Zokie’s own server on Amazon Web Services in Hyderabad, India. Like any web server, it processes your IP address, browser and device details, the page you requested and the time of the request, so it can deliver the page and protect the site from abuse; it does not keep a log of page requests. The sign-up, sign-in, download, blog, changelog and legal pages load their fonts from Google Fonts, which receives your IP address and browser details when it serves them; other pages serve their fonts from zokie.dev. Profile pictures are loaded from GitHub or Google. zokie.dev runs no advertising scripts.

When you sign up or sign in, zokie.dev sets signed sign-in cookies that scripts cannot read, used only to keep you signed in to your account; signing out removes them. A sign-in lasts 7 days from when you last used it in a browser and a year in the Zokie apps, so integrations such as Slack keep working through your Mac; each sign-in keeps the IP address and device type it started from until it ends. If you type an invite code before signing in, a cookie that scripts cannot read keeps the code for up to an hour so it survives the trip to Apple, GitHub or Google.

zokie.dev sends a few product analytics events to Mixpanel: the page you open (its path, never the rest of the address), the website that linked you here, campaign and referral tags in the link, clicks on the download, install help, upgrade and sign-in buttons, team invites sent, and finishing sign-up. It sets no analytics cookie. A random id kept in your browser’s session storage links these events until you close the tab, and we tell Mixpanel not to use your IP address. Your browser’s local storage keeps the campaign tags or website that first brought you here, so a sign-up days later is credited to them; it holds no identifier. Once you sign in, events are linked to your account id, never to your name or email, and your Mixpanel profile records that first source. The website sends no events and stores nothing for analytics if your browser sends Global Privacy Control or Do Not Track.

Data the app keeps on your computer

The Zokie app stores its data under ~/.zokie on your computer:

settings in config.json;
projects, tasks, chat history and recorded spend in zokie.db;
your sign-in session, with your name and email, in session.json;
the access tokens of tools you connect, such as Linear, in connections.json;
git worktrees, checkpoints, attached and pasted files, notebooks and Python environments;
an app log in logs/ that records no message text, but can include your account id, the names of repositories you clone, the tools and skills you install, and file paths inside error messages.

Product analytics in the app

The app sends a short, fixed list of product events to Mixpanel: the app opening, updating, or not having closed cleanly last time, signing in, each onboarding step and finishing onboarding, connecting a tool, an agent or GitHub, adding a project, an agent run starting and finishing (the kind of task, which agent, and whether it finished, failed or was stopped), your first task, a pull request being opened or merged, a command arriving from your phone, which Zokie features you open, upgrade prompts and clicks, a team invite being sent, and an error being shown (where it appeared, never its text). Each event carries a random id stored in ~/.zokie/analytics-id, your account id when you are signed in, the app version, your operating system and processor type, and we tell Mixpanel not to use your IP address. ~/.zokie/analytics-state.json remembers which once-only events were already sent, the version that last ran and whether it closed cleanly. Your Mixpanel profile records your operating system, app version and whether Claude Code or Codex is installed. Events never include your code, file or folder names, prompts, chat text, repository or branch names, pull request titles, your name or your email. To turn this off, set "disableAnalytics": true in ~/.zokie/config.json and restart Zokie.

Product analytics from our server

Our server sends Mixpanel a few events linked to your account id: a payment going through or failing and a plan being cancelled (the plan, seats, amount and currency, whether an offer applied, and whether it was your first payment), an invite being created, and an invite code being redeemed (the invite’s id, the account that made it and the code’s last four characters). Your Mixpanel profile records your plan and when you first paid. These events never include your name, email or payment details.

Cloud backup and phone control (paid plans)

On a paid plan, while you are signed in, the app backs up to the Zokie cloud: your projects’ names and git remote addresses; your tasks (title, branch, status, what the agent is doing right now such as the command it is running or the file it is editing, agent, model, costs and pull request number); your chats including their message text; your task cards (labels and descriptions); your recorded spend; and this computer’s name and app version. This lets you restore your work on another computer and follow it from your phone. The app also sends the questions your agents are waiting on (a title, the command, file path or web address they ask about, and any choices), and receives the messages, decisions and new tasks you send from your phone. Notifications reach your phone through OneSignal, which receives your account id and the task and question titles. Your repositories and files themselves are never uploaded, though chat text can contain code or file names that came up in the conversation. For free accounts and signed-out computers, none of this is stored in the Zokie cloud.

Tools you connect

When you connect Linear, Jira, Notion or Slack, you approve access on that service, and the sign-in passes through our server, which hands the tokens to your computer and then clears its own encrypted copy. From then on the app talks to those services directly with your tokens; for example, it reads your Linear issues about every ten minutes and turns them into tasks. You can disconnect at any time.

Zokie for Slack

When a workspace installs Zokie for Slack, our server stores its workspace ID, workspace name, bot user ID and an encrypted bot token. Linking your account associates your Slack user ID with your Zokie account. The app receives messages that mention it and direct messages you send it, and uses your requests to create or steer tasks. When you ask it to fix a bug in a channel thread, it also reads the original report and replies in that thread, up to the first 15 messages and 9,000 characters of context. This text becomes part of your task description and is sent to your computer, where your chosen coding agent can use it. It follows the same storage and deletion practices as your other task content. Zokie does not download files or images from the thread.

Zokie posts task confirmations (including the name of the computer the task runs on), status, progress lines while the agent works (at most one every five minutes), permission requests, and completion summaries back to that Slack thread; people who can read the thread can see those replies. A workspace admin approves channel-history access when installing or reinstalling the app, and the bot can read only conversations it has joined. Removing the Slack app stops further access; it does not erase task content already saved in Zokie. Contact yo@zokie.dev to request erasure.

The app includes no crash reporting.

Data the app sends to other services on your behalf

Zokie runs tools you install and sign in to yourself. When you use them, your data goes to those services under your own accounts, not to us:

Claude Code sends your prompts, code and attached files to Anthropic. Claude tasks start with Claude Code’s Remote Control switched on, which makes the session available in claude.ai and the Claude apps; you can turn it off for a task until Zokie restarts, or everywhere with disableRemoteControl in your settings.
Codex sends your prompts, code and attached files to OpenAI; Gemini CLI sends them to Google, and Cursor to Cursor.
OpenRouter, when you connect a key, receives the messages, the code and files read in the task, and the results of the commands run for the models you pick, and passes them to that model’s provider; some providers keep prompts or use them to improve their models, under OpenRouter’s and their own terms. Connecting OpenRouter passes through zokie.dev, which forwards OpenRouter’s one-time code to the app on your computer and keeps nothing; the key is stored in your computer’s keychain. On a paid plan the app also reads your OpenRouter credit balance with that key to show it beside your usage; the balance stays on your computer.
Quick Deploy sends the app you choose to deploy, including its code, build settings and the environment variables you give it, to the hosting service you connect (such as Vercel, Netlify, Cloudflare, Render or Fly.io), under your own account with that service. Once deployed, the app is public on the internet.
GitHub CLI (gh) talks to GitHub to read your account and repositories, clone them, show your contributions, open and merge pull requests, and show their status.
Updates: a few seconds after launch and about every hour, Zokie reads zokie.dev/updates and downloads a newer signed version in the background; it installs when you choose. These requests carry no account data.
uv downloads Python packages from the Python Package Index when you set up Data mode, and ccusage is fetched from npm to read your agents’ spend if it is not installed.
Importing a Google Sheet reads it from Google; images linked in a chat load from the sites that host them; and pull requests Zokie opens show the Zokie logo from zokie.dev.

Language servers run on your computer.

2. How we use personal data

We use the personal data described above to:

run your account, send invite codes and provide support (the people who run Zokie see your name, email, profile picture and status for this);
send the emails described above, including important notices such as changes to these policies;
run your subscription, back up and sync your work, run teams, and deliver notifications to your phone;
see which features people use and where they get stuck, through the product analytics described above, so we can improve Zokie;
keep the website available, secure and free of abuse;
comply with the law and enforce our Terms of Service.

We do not sell personal data, use it for advertising, or use it to train AI models. Backed-up chats are used only to store them, restore them, and show them to you, your team and your phone.

4. Retention

We keep your account (and an address you left at zokie.dev/join while Zokie was invite only), your subscription records and your paid-plan backups until you ask us to erase them, including after a paid plan ends. Deleting your account from your profile at zokie.dev/account signs you out and locks the account; it does not erase the data behind it and does not cancel a paid plan, so cancel your plan on the Billing page first, and download your backup there too if you want a copy. To have your personal data erased, email yo@zokie.dev. We keep support and feedback emails for as long as we need them to handle your request, and delete them when you ask. Payment records are kept by Razorpay under its own retention period. Mixpanel keeps analytics events for us; email yo@zokie.dev and we will delete the events linked to your account.

Data the app stores on your computer stays there until you delete it. Removing the ~/.zokie folder removes all of it; branches and commits in your own repositories are yours to keep or delete.

5. Security

Zokie keeps your code on your own computer, which limits what can be exposed. The website and API are served only over HTTPS, tool tokens are encrypted while they pass through our server, and we use established providers for hosting, payments and email. No system is perfectly secure, so please keep your computer, your GitHub account and your AI provider accounts protected with strong passwords and two-factor authentication.

6. Your rights and choices

Depending on where you live, you may have the right to:

ask what personal data we hold about you and get a copy of it;
correct or update it;
ask us to delete it;
withdraw your consent, where we rely on consent;
object to or restrict certain processing;
raise a grievance with us, and with your data protection authority.

At zokie.dev/account you can change your display name and handle, download a copy of your backed-up tasks, chats and costs (on the Billing page), cancel your plan, and delete your account. For anything else, email yo@zokie.dev. We will reply within 30 days. You can also stop sending data to third-party services by signing out of them, disconnecting tools, turning off Remote Control, or not using the related features. To stop product analytics, set "disableAnalytics": true in ~/.zokie/config.json for the app, and turn on Global Privacy Control or Do Not Track in your browser for the website. To stop the server’s events about your account, email yo@zokie.dev and we will stop them and delete the ones already sent.

7. Jurisdiction-specific disclosures

India

Zokie is operated from India and processes digital personal data in line with the Digital Personal Data Protection Act, 2023. You may nominate another person to exercise your rights in the event of your death or incapacity. Our grievance contact is the Zokie grievance officer, reachable at yo@zokie.dev.

European Economic Area and United Kingdom

We process your sign-up details to provide the account you asked for; payments, backups, teams and phone notifications to provide the service you asked for; support emails on the basis of our legitimate interest in replying; website logs on the basis of our legitimate interest in running a secure site; and product analytics on the basis of our legitimate interest in improving Zokie, which you can object to by turning analytics off as described above. Your data may be processed outside your country by us and our providers. You can complain to your local data protection authority.

California

We do not sell or share personal information for cross-context behavioral advertising.

8. Children

Zokie is built for software developers and is not intended for anyone under 18. We do not knowingly collect personal data from children. If you believe a child has sent us personal data, email yo@zokie.dev and we will delete it.

9. Changes to this policy

We may update this policy as Zokie changes. We will change the date at the top of this page, and for significant changes we will tell people who have given us their email address.

10. Contact us

Questions or requests about this policy or your data: yo@zokie.dev. Zokie is built and operated in India.