Data handling and security
Last updated Nov 11, 2026
Your code stays on your machine. Ingot is a desktop editor: your files are opened, indexed and edited on your computer. This page lists exactly what leaves your computer, when, where it goes and how long it is kept.
What stays on your computer
- Your files and folders, and the codebase index Ingot builds for search (it runs on your computer, or with a local model you set up).
- Local history, terminals, test runs and Git operations, except pushes you make to your own Git host.
- Chat messages with agents. Only chat titles and their order are synced (see below).
- Requests to local models: they never leave your computer.
What leaves your computer, and when
| What | When | Where it goes | How long it is kept |
|---|---|---|---|
| Your prompt and the code context the agent picked (files you attach, code it reads) | Only when you send a chat, an inline edit or a Tab prediction with an Ingot model | Our server, then OpenRouter, then the model provider | Not stored by us. We keep a usage record: model, tokens, cost and time. |
| The same, with your own key | When you use your own provider key | Straight from your computer to that provider (not through Ingot) | Under that provider's policy |
| Account details | When you sign up or change them | Our server | Until you delete your account |
| Settings, keybindings, rule files, chat titles and order | While signed in with sync on (on by default; turn it off in the editor settings) | Our server | Until you delete them or your account |
| Agent status: status, agent name, short detail, model, open folder name | While signed in | Our server, so the dashboard and Ingot Remote can show it | One row per editor session, replaced on each update |
| Ingot Remote: the state of your agents and the commands you send from your phone | While Remote is on | Our server's memory only, never written to the database | Finished commands are dropped after 10 minutes |
| Ingot Web: the pages and files of a project you publish | While the project is published and someone opens it | Through our relay, straight to the viewer | Never stored. We keep only the project name, share settings and times. |
| Together: edits and cursors | While a session is open | Through our server's memory to the other participants | Never stored |
| Feedback and bug reports: message, optional screenshot, optional diagnostics (scrubbed), app version and OS | Only when you press Send | Our server | [Feedback and support message retention period] |
| Crash reports: error type, scrubbed message and stack trace | If error reporting is turned on in your build | Our error-tracking service | Under that service's retention |
| Questions to Ask Ingot on this website | When you ask one | A model provider, to answer it | The question is not stored. We keep a hashed IP, the outcome and token counts. |
Privacy mode
Privacy mode is on by default. With it on, Ingot models and OpenRouter with your own key use only zero data retention routes: providers that neither keep your prompts nor train on them. Direct provider routes that cannot promise this are skipped, and if no private route is available the request stops with an error instead of falling back. Your own keys for other providers follow that provider's policy, and local models never leave your computer. Turn it on or off in the editor under Settings › Tools › AI Models › Privacy mode. See the Privacy mode docs page for details.
Where your data is stored
- Database: Neon Postgres in AWS eu-central-1 (Frankfurt, Germany).
- API server, relay and Together: Fly.io, region fra (Frankfurt, Germany).
- Website: Vercel, on a global edge network, with server functions in [Vercel function region].
- Model providers may process requests in the United States or other countries.
Subprocessors
These companies process data for us. We will update this list before adding a new one.
| Company | Purpose | Data it receives | Location |
|---|---|---|---|
| Neon | Database | All account data listed on this page | EU (Frankfurt) |
| Fly.io | API server, relay and Together | Traffic to our API, server logs | EU (Frankfurt) |
| Vercel | Website hosting | Page requests, request logs | Global edge, [Vercel function region] |
| OpenRouter | Routing requests to Ingot models | Prompts and code context of hosted requests | United States |
| Model providers | Running the model you pick | Prompts and code context of that request | [Model providers used directly, if any] |
| Resend | Sign-in codes and account email | Your email address and the message | [Email provider region] |
| Google and GitHub | Sign-in, only if you choose it | They send us your email, name and avatar | United States |
| [Merchant of record: Lemon Squeezy or Paddle] | Payments, invoices and tax (after the beta) | Billing details you enter at checkout | — |
| Error tracking | Crash reports, only if turned on | Scrubbed technical data | [Error-tracking provider and region] |
| Google Workspace | Our support mailbox | Emails you send us | — |
| Your browser's push service | Ingot Remote notifications, only if you allow them | A chat title and a fixed short line | Depends on your browser |
Encryption and access
- All traffic to our API and website uses HTTPS (TLS).
- Model provider keys, Git tokens, connection secrets and share keys you save are encrypted with AES-256-GCM before they are stored.
- Sign-in sessions, access tokens, one-time codes and device tokens are stored only as hashes.
- IP addresses on support, sales and feedback forms are stored only as one-way hashes.
- Crash reports and feedback diagnostics are scrubbed of tokens, keys, email addresses, IP addresses and home-folder names before they are sent, and again on the server.
- Access to production data is limited to the people who run the Service, and admin actions are written to an audit log.
Delete your account or data
There is no delete button in the dashboard yet. To delete your account, email [Privacy contact email] from the address on your account. We may ask you to confirm, and we delete it within [Account deletion period, e.g. 30 days].
- Deleted with the account: your profile, sign-in methods, sessions and tokens, saved keys, synced settings, usage records, team memberships, Web projects, push subscriptions, and all Zaprex data (chats, tasks, runs, memory, connections).
- Unlinked but kept: billing records (for tax law), and support messages and feedback reports (ask us to delete those too).
- Not in our hands: requests already sent to a model provider under its own policy, and commits or pull requests in your own Git host.
You can also delete parts yourself at any time: revoke access tokens and remove saved keys in the dashboard, turn off settings sync in the editor, stop or delete Web projects, and clear Zaprex memory.
Report a security problem
Email [Security contact email]. Please give us a reasonable time to fix the problem before you share it publicly.