# Privacy Policy ยท Exodus by elim.io > What personal data Exodus collects, why, who handles it, where it is kept, for how long, and your rights. Exodus never receives your source code. ## Privacy Policy Last updated: 13 October 2026. This policy explains how ELIM (elim.io), which provides Exodus ("we", "us"), handles personal data when you visit exodus.elim.io, write to us, sign in to the cabinet at app.exodus.elim.io, or link the open-source exodus command line tool (CLI) to the cabinet. It is written to meet the UK General Data Protection Regulation and the EU General Data Protection Regulation ("GDPR"). Words like "personal data", "controller" and "processing" have the meaning those laws give them. ## 1. Who we are Exodus is a free service that, with your own coding agent, audits a repository, estimates what the app costs today and on Google Cloud Run, and plans the move. We are a small team and we do not have a designated Data Protection Officer. Every data protection question and request goes to one address: [hello@elim.io](mailto:hello@elim.io). We are the controller of the personal data described in this policy: we decide why and how it is used. ## 2. What Exodus never receives - **Your source code.** The CLI reads your repository on your machine and never uploads a file. Each finding carries the file name, the line number and that one line of code (at most 200 characters), as evidence of what was found. - **The values of your environment variables and secrets.** The audit reads the names of variables, never their values, and never opens .env files. - **Access to your Google Cloud account.** Exodus never signs in to Google Cloud for you. Your coding agent runs Google's own tools on your machine, under your account. - **Payment details.** Exodus is free and asks for none. The CLI also works offline, without an account. Then it sends nothing to us. ## 3. Personal data we collect ### 3.1 When you visit exodus.elim.io This website and the cabinet use Cloudflare Web Analytics to count visits. Its script sets no cookies, stores nothing in your browser and does not follow you across other sites. For each page view it sends Cloudflare the page's address, the referring page, your browser, operating system and type of device, and how fast the page loaded; Cloudflare works out the country from your IP address and does not give us the address. We see only totals, such as page views per page, country or browser. The servers that host this website also keep ordinary request logs: IP address, date and time, the page requested, the referring page and your browser's user agent. We use these logs to keep the site running and secure and to investigate faults. ### 3.2 When you write to us The forms Consult an expert and Report a problem collect what you type into them (such as your name, email address, company and message), the page you sent the form from and, in the cabinet, your account's email address. If you attach a report, it is shared by link, so the person who answers can open it. A submission is stored in estype, the content system this site runs on, and a notice of it is posted to our team's private Slack channel. If you email us, we keep the email and our reply. We use this to answer you and to keep a record of the conversation. ### 3.3 When you sign in to the cabinet - **Account details:** your Google account identifier, your name and your email address, and when you first and last signed in. We ask Google only for your basic profile and email address. - **Activity and request records:** a log of what happens in each project, shown as its Activity, and the IP address and browser of requests to the cabinet. ### 3.4 When you link the CLI to a project - **The project:** its name, the repository's owner and name, the platform it runs on today and its stack (languages, frameworks, databases, services). - **Audit findings:** file names and line numbers, the names of processes, databases and environment variables, and one line of code per finding as described in section 2. - **Your answers** to the audit's questions, such as your traffic, where your users are and what you pay today. - **Reports and the plan:** the reports built from the findings and answers, the plan, which tasks are done and the commit you named for each. - **Your Google Cloud bill**, when your agent sends it with exodus bill: the rows of the month (service, item, usage and cost), and the results of exodus check runs in your CI. - **CLI keys**, stored only as a hash, never the key itself, with the device name and operating system each was made on and when it was last used. One-time connection codes are stored as a keyed hash and deleted when they expire. ## 4. How we use it and our lawful bases - **Running your account and the service** (signing you in, building and showing your reports and plan): account, project and key data, activity records. Lawful basis: contract. - **Answering what you send us:** form submissions and emails. Lawful basis: legitimate interests (answering people who contact us). - **Keeping the service secure, preventing abuse, rate limiting:** request logs, IP addresses, activity records. Lawful basis: legitimate interests (the security of the service and of our users' data). - **Fixing faults and restoring from backups:** logs, activity records, backups. Lawful basis: legitimate interests (a working, recoverable service). - **Knowing which pages people read and how fast they load:** the visit counts in section 3.1, which identify no one. Lawful basis: legitimate interests (improving the site and the cabinet). - **Telling you about your account, incidents and changes to our terms:** name, email address. Lawful basis: contract; legal obligation for some notices. - **Establishing, exercising or defending legal claims and enforcing our terms:** the relevant records. Lawful basis: legitimate interests. Where we rely on legitimate interests, we have weighed them against your rights, and you may object (section 12). We do not process special category data (such as health or ethnic origin), and we ask you not to send it to us. We do not profile you. ## 5. Cookies and local storage We use only what is strictly necessary to sign you in. There are no advertising cookies, no tracking pixels, no analytics cookies and no cross-site tracking, so there is no cookie banner to accept. The visit counts in section 3.1 need no cookie. - **exodus_session**, on app.exodus.elim.io: keeps you signed in. HttpOnly, Secure, SameSite=Lax. Up to 30 days, or until you sign out. - **exodus_auth**, on app.exodus.elim.io: holds the state of one sign-in with Google, to check Google's answer. 10 minutes. The cabinet keeps nothing about you in your browser's local storage. You can block or delete cookies in your browser settings; if you block exodus_session you will not be able to sign in. The home page can play a video of Exodus from YouTube. The player is loaded from youtube-nocookie.com only when you press play, and YouTube's privacy policy applies to it from then on. ## 6. AI, agents and automated decisions - There is no AI model on our side. Reports, prices and plans are computed by plain code from the price lists the report names. **We do not train any AI model on your data, and we do not send your data to AI providers.** - The audit and the move are run by your own coding agent, on your machine, with the access you give it. Whatever it sends to its own provider is governed by your agreement with that provider, not by us. - We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Automatic limits in the service, such as rate limits, follow plain rules, and you can always ask a person to review them. ## 7. Email we send The service does not send email. When we write to you about your account, an incident, a security matter or a change to our terms or this policy, a person on our team writes to you. We do not buy email lists and do not add your address to a mailing list. If we ever start a newsletter, we will ask first. ## 8. Who we share it with **We do not sell personal data, and we do not share it for advertising.** We share it only with: - **Service providers** that host and run Exodus for us: Google Cloud (the cabinet, its database and its logs, and the sign-in with Google), estype (this website and the form submissions), Cloudflare (the visit counts in section 3.1) and Slack (the notice of each form submission to our team). Each is bound by its terms to use the data only to provide its service to us and to protect it. - **People you share a report with.** A report you share by link can be opened by anyone who has the link. The shared page leaves out your account details. Sharing is off until you turn it on, and you can turn it off at any time. - **Professional advisers**, such as lawyers and accountants, under a duty of confidentiality. - **Authorities and others where the law requires it**, or where disclosure is reasonably necessary to comply with a legal obligation or a valid legal request, to enforce our terms, to detect and prevent fraud or security problems, or to protect the rights, property or safety of our users, the public or us. - **A successor**, if Exodus is transferred to someone else. The data would remain subject to this policy, and we would tell you before it becomes subject to a different one. The CLI is downloaded from GitHub, and its source code is published there; GitHub's own privacy statement covers those visits. ## 9. Where data is stored and international transfers The cabinet's data is stored in Google Cloud Firestore in the European Union, in Belgium (europe-west1). Form submissions are stored by estype on Google Cloud in Belgium (europe-west1). Some data leaves the European Economic Area: our team and some providers (such as Slack) operate outside the EEA and the UK. Where personal data goes from the EEA or the UK to a country without an adequacy decision, the transfer relies on the European Commission's Standard Contractual Clauses and, for UK data, the UK International Data Transfer Addendum, in our providers' data processing terms. ## 10. How long we keep it - **Account and project data:** while your account exists. You can delete a project, or your whole account, at any time (section 13). - **Backups:** the database keeps point-in-time recovery and a daily backup, each for 7 days, so deleted data leaves the backups within 7 days. - **Request logs:** up to 30 days. - **One-time connection codes:** until they expire. - **Form submissions and emails:** until you ask us to delete them. We may keep data longer where the law requires it, or to establish, exercise or defend a legal claim, and only for that purpose. ## 11. How we protect it All traffic is encrypted in transit with TLS. CLI keys and connection codes are stored only as hashes. The session cookie is signed, so it cannot be forged. The database accepts no direct access from browsers; only the Exodus API reads and writes it. Requests are rate limited. Access to production is limited to the few people who operate it. No system is perfectly secure. If a personal data breach affects you and is likely to put your rights at risk, we will tell you and the relevant authority as the law requires. ## 12. Your rights Under the UK GDPR and EU GDPR, and subject to the conditions and exceptions those laws set, you have the right to: - **Access** the personal data we hold about you and get a copy of it. - **Rectification:** have inaccurate data corrected and incomplete data completed. - **Erasure:** have your data deleted where there is no good reason for us to keep it. - **Restriction:** ask us to pause the use of your data while a question is resolved. - **Portability:** receive the data you gave us in a structured, machine-readable format. Every report downloads as JSON and Markdown from the cabinet. - **Object** to processing based on our legitimate interests. - **Withdraw consent** where we rely on it, without affecting what came before. - **Complain** to a data protection authority (section 17). We give these rights to everyone, wherever you live, to the extent we can, even where your local law does not require it. ## 13. How to delete your data and exercise your rights - **Delete a project** in its Settings tab: the project, its reports, answers, findings, plan and activity are deleted, its share links stop working and its CLI keys are revoked. - **Delete your account** in Settings, under Danger zone: every project, report, share link and key is deleted, and then the account itself. - **Anything else**, or if you prefer us to do it: write to [hello@elim.io](mailto:hello@elim.io) and tell us what you would like us to do. We will answer within one month. If a request is complex, we may extend that by up to two further months, and we will tell you why within the first month. We may ask you to confirm your identity before acting, usually by replying from the email address on the account. We do not charge a fee, unless a request is clearly unfounded or excessive. You will not be treated differently for exercising your rights. ## 14. California and other US states If you live in California or another US state with a consumer privacy law, you have rights similar to those in section 12: to know what personal information we collect, use and disclose, to access it, to correct it, to delete it, and to opt out of its sale or sharing. The categories we collect are identifiers (name, email address, IP address) and internet activity (request logs and activity in the service); the sources, purposes and recipients are those in sections 3, 4 and 8. **We do not sell personal information and we do not share it for cross-context behavioural advertising.** To make a request, write to [hello@elim.io](mailto:hello@elim.io). ## 15. Children Exodus is a service for developers and businesses and is not meant for children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us personal data, write to [hello@elim.io](mailto:hello@elim.io) and we will delete it. ## 16. Changes to this policy We may update this policy as the service or the law changes. The date at the top shows when the current version took effect. If a change materially affects how we handle your personal data, we will tell account holders before it applies and, where the law requires it, ask for your consent. ## 17. Contact and complaints For anything about this policy or your data, write to [hello@elim.io](mailto:hello@elim.io). If you are unhappy with how we handled your data, please tell us first so we can put it right. You also have the right to complain to a supervisory authority: in the UK, the Information Commissioner's Office ([ico.org.uk](https://ico.org.uk/make-a-complaint/)); in the EU or EEA, the data protection authority of the country where you live or work, or where you think the problem happened. Our terms of use are at [exodus.elim.io/terms](https://exodus.elim.io/terms).