PrivacyPolicy.

We collect what we need to run your account and nothing else. We never sell your data, never advertise to you, and never look at your code except when you ask us to for support. Payment details are handled by Cashfree — they never reach our servers.

This policy explains it fully. Mohit Bansal is the data controller (“we”, “us”), and it applies to kodeo.website and the KODEO app.

You give us:

• Account details — name, username, email address, password (stored only as an Argon2id hash), and optionally a profile picture, bio, developer role and tech stack.
• Workspace content — workspace and project names, descriptions, files and the people you invite.
• Billing details — the name, email, phone number and optional company, GSTIN and address you enter for receipts.
• Anything you write to us in a support message.

We record automatically:

• Session and security data — sign-in time, IP address, browser/device description and an approximate location, so you can review and revoke sessions.
• Payment records from Cashfree — plan, amount, status, and a masked description of the method (for example “UPI · name@bank” or “VISA •••• 4242”).
• Basic technical logs needed to keep the service running and safe.
• Only if you turn it on in KODEO for VS Code (“Share Performance Numbers”, off by default, and never while VS Code’s own telemetry is off): how long the extension took to start, open a project and join the room, and how quickly your typing reached the room. These numbers are stored with the editor’s name and the extension’s version only — never your account, device, project, files or address.
• Only if you turn it on in the kodeo CLI (“kodeo config telemetry on”, off by default, never in CI): how long kodeo took to start, sign in and sync a save, and how quickly its dashboard draws. Stored with kodeo’s version, your operating-system family and the kind of terminal only — never your account, device, project, files or address.
• How much the kodeo CLI and KODEO for VS Code are used, as counts per day by client and version (for example how many times “kodeo watch” or the dashboard was started) — counted by our servers when they answer, with nothing about who.
• When you share a preview of a running app: who shared it, for which project, who may open it, its port, when it ends, and how many bytes, requests and visitors it had. Our preview server forwards visitors’ requests to your app without storing them; the request log you see stays in your own browser tab or terminal. Someone opening a preview is counted by a random id in a cookie on the preview’s own site, and a member’s name is shown to the person sharing it. If someone reports a preview, we keep the report and a one-way hash of their address — never the address.

We never collect your card number, CVV, UPI PIN or bank credentials. Those are entered on Cashfree’s own page.

• To provide the service — accounts, workspaces, projects, collaboration and themes (performing our contract with you).
• To take payments, issue receipts and apply plan limits (performing our contract, and meeting legal accounting duties).
• To keep accounts safe — detecting suspicious sign-ins, rate limiting and preventing abuse (our legitimate interest in security).
• To send service email — verification codes, security alerts, invitations, receipts and billing notices. These are not marketing and cannot be switched off while your account is open.
• To improve the product by understanding which features are used (our legitimate interest), never by reading your code.

We do not sell your personal data or share it for advertising. We share the minimum necessary with the providers who run KODEO:

• Cashfree Payments — your billing name, email and phone number, to create the payment and mandate.
• Neon (database hosting) and Vercel (application hosting) — they store and serve the data on our behalf.
• Our email provider — your email address and the message content, to deliver transactional email.
• Google / GitHub — only if you choose to sign in with them; we receive your name, email and avatar.
• DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., servers in China) — writes KODEO Assist’s answers. It receives the question you ask, KODEO’s Help Center, and — only if you allowed it (Settings → Privacy) — facts about your account such as your plan, usage, roles, whether two-factor is on, which computers (the kodeo CLI or KODEO for VS Code) and tokens can reach your projects (their names and dates — never a token), and your live preview shares (the project, who can open them and when they end — never the link). We remove email addresses, phone numbers, sign-in codes and anything shaped like a secret before sending, and never send your files or code. When you ask from KODEO for VS Code, it is also told that editor’s state — for example whether you’re live, the extension’s version, whether saves are waiting to be sent, and your pop-up setting — never your files, code or terminal output. When you ask from the kodeo CLI, it is told the CLI’s state the same way — its version, your operating-system family, whether the folder is linked and being synced, and whether you asked from its dashboard — and, if you allowed account checks, which of your computers are syncing which project right now (names only). Staff also use it to draft support replies (the ticket text, with the same details removed).
• Other workspace members — your name, username and avatar are visible to people in workspaces you join.

We may also disclose data if the law requires it, or to protect our rights, users or the security of the service.

• Account and workspace data — until you delete your account or the workspace.
• Sessions — until they expire or you revoke them.
• One-time codes (OTP) — 10 minutes.
• Payment records, receipts and invoices — retained as required by Indian tax and accounting law (generally up to 8 years), even after account deletion.
• Security and webhook logs — kept for a limited period for debugging and audits, then deleted.
• KODEO Assist conversations (signed in) — 30 days, deletable any time; a visitor’s stay only in their own browser. The questions asked, with personal details removed, are kept 180 days to improve the Help Center.
• Support tickets — while your account exists; screenshots and logs attached to a ticket are deleted 90 days after it closes.
• KODEO for VS Code and kodeo CLI speed numbers (only if you turned them on) — 90 days. Daily usage counts — 400 days.
• Shared previews — the record of a share while it’s live and for the workspace’s history afterwards; preview traffic counts per day (bytes and requests, by workspace) — 400 days. Pins on a running app — until they’re deleted with their project.

• Passwords are hashed with Argon2id and checked against known breach lists; we can never read them.
• Sessions use short-lived tokens with rotation and reuse detection, in secure, httpOnly cookies.
• All traffic is encrypted with HTTPS, and the database connection uses TLS.
• Payment webhooks are cryptographically verified before anything is recorded.
• Access to production data is limited to what is needed to operate the service.

We only use cookies that the product needs. There are no advertising or third-party tracking cookies.

• Sign-in cookies that keep you logged in (httpOnly, Secure, SameSite=Lax).
• A short-lived cookie during email verification and password reset.
• A theme cookie that remembers your chosen theme so the page never flashes the wrong colours.

• Access and correct your details from your profile at any time.
• Export or ask for a copy of your data by writing to us.
• Delete your account yourself from Settings → Danger zone; owned workspaces and projects go with it.
• Object to or restrict certain processing, and complain to a data protection authority.

Write to privacy@kodeo.website and we will respond within 30 days. Under India’s IT Rules, our grievance officer is Mohit Bansal, grievance@kodeo.website.

Our providers may process data outside India. When that happens we rely on their contractual safeguards and standard data protection clauses.

KODEO is not intended for children under 18. If you believe a child has given us personal data, contact us and we will delete it.

If we change how we handle your data, we update this page and the date above, and tell you in the app or by email before significant changes take effect. See also our Terms and Refunds policy.