Privacy Policy
Last updated: September 24, 2026
This policy describes what personal data DeployYourCode collects, why we collect it, and how you can exercise control over it.
1. Data we collect
Account data (name, email, password hash or social-login identifier, optional avatar), organization data (name, members, projects, uploaded logos), billing data (subscription status and history — full payment details are held by Stripe, not us), security data (active sessions — including, for a session that began through your organization's single sign-on, which identity provider it came through — two-factor and passkey enrollment, and audit-log entries — each recorded with the IP address and browser of the request that made it, when the action was made with your own credentials), your organization's security settings (if it uses single sign-on or directory sync: the identity provider's issuer, domain and sign-in configuration, and a hash of the directory sync token, never the token itself), organization verification data (whether your organization is verified and how: for the GitHub account that connected your repositories, its numeric id, its login and when GitHub says it was created; for a card, Stripe's fingerprint of it and whether it is credit or debit — never its number, and the card is never charged; for a review, what you wrote to us), abuse-handling records (what our automatic checks found on a public app's front page — read from the platform's own address for it, never a domain you attached — and any action we took, with its stated reason, your notice and any appeal), abuse reports sent through our public form (the reported address, the category, the description, and the reporter's name and email if given), and basic server logs (IP address, user agent) for security and debugging.
2. How we use it
To provide and secure the Service: authenticating you, running your organizations, processing subscription payments, sending transactional email (invitations, password resets, receipts, billing alerts), preventing abuse, and complying with legal obligations. We do not sell personal data or use it for third-party advertising.
3. Processors we share data with
Stripe (payments), Resend (transactional email), Anthropic (the AI assistant, the automatic build-fix feature, and our automatic abuse check, which sends it features of a public app's front page — its title, headings, forms and visible text), Google (only if we turn on Web Risk: the public addresses of apps we host, to ask whether they are listed as dangerous), GitHub (reading the repositories you connect), Fly.io (running your applications and databases, and our own background-job server with its history database and queue), Tigris Data (private storage, once builds run on dedicated build machines, for their logs, results and images for a few days, and for the archive of background job history), Cloudflare (domain registration if you buy a domain through us, the bot check on our sign-up and sign-in forms, and routing of email sent to our support and abuse addresses), Google (the mailboxes those addresses are delivered to), Supabase (our own database), Sentry (error reports, only while error reporting is turned on), and our hosting providers. The current list, with what each one holds, is at /subprocessors. Until 24 September 2026 background jobs were processed by Inngest, which keeps what it processed under its own retention policy. Each processor receives only the data required for its function and is bound by its own data-processing agreement.
4. Cookies and local storage
We use strictly necessary, first-party cookies only: a session cookie to keep you signed in, one additional session cookie per extra account you sign in to on the same device, a short-lived cookie during social or single sign-on, a cookie recording which sign-in method you last used, and — if you complete two-factor authentication — a cookie that remembers this browser for 30 days so you are not challenged every time. Your theme preference and some interface state are kept in your browser's local storage and are not sent to us. We use no advertising, analytics or cross-site tracking cookies of any kind, and load no third-party scripts.
5. Data retention
Account and organization data is retained while your account is active. Webhook delivery logs are kept for 30 days, our record of each push GitHub sends us (the repository, branch and commit, with its message and author name) for 14 days, in-app notifications for 90 days, uptime history for 30 days, hourly totals of the requests our edge handled for each of your fronted apps (how many were forwarded, blocked, challenged or rate-limited, by which rule, and how many bytes — never a visitor's address, which stays in Cloudflare's own analytics and is shown to you on demand from there, not copied into our database) for 30 days, our record of each build run on a dedicated build machine (how it ended, its error message, and the names of the environment variables your code reads, with the file and line where each is read) for 30 days after the build ends, AI assistant conversations for 180 days after their last message, audit-log entries for 12 months — the IP address and browser recorded beside an entry are kept exactly as long as the entry, and an organization owner or admin can download the log or have each new entry sent to the organization's own webhook endpoints, after which that copy is the organization's to keep — and abuse reports for 180 days after they are resolved (our record of what we did about one is kept), after which they are automatically pruned. Our automatic abuse checks keep a clean result for 30 days and anything they found, once decided, for 180 days. Before we act on abuse we preserve evidence — a copy of what the app served, its deployment and image, and the organization's recent activity log including the addresses recorded in it — in private storage for 180 days. Our record of an action taken over abuse, and a ban of an identifier (an email address or its domain, a GitHub account, a card fingerprint, a domain), are kept after the account and the organization are deleted, so that a repeat of the abuse can be recognized. Verification data is kept while the organization exists. Our shared build service keeps its own record of how each build it ran ended (the outcome, its error message and the image it produced) for 24 hours while it is running (it sleeps between builds and prunes only while awake, so a record can persist until its next wake), so that the answer survives a restart of that service; our hosting provider's automatic snapshots of that service's disk can keep such a record for up to 5 more days. A build run on a dedicated build machine also leaves its build log and result — and an AI fix's patch, when the build applied one — in private storage at Tigris Data for 30 days, and the image it built there for at most 1 day. Background job history — our record of each background job run on your behalf (deploys, database provisioning, usage metering and the like), which can include the data that job was given and what it produced — is kept on our job server for 21 days, then moved to private archive storage and deleted from there after 12 months (365 days). That history can include your name and email address (for example, the job that sends your welcome email), and deleting your account does not remove it early: it expires on that schedule. Our hosting provider also keeps automatic snapshots of the job server's databases for 5 days, so job history deleted there can persist in a snapshot for up to 5 more days. Application runtime logs are not stored by us — they are read live from the hosting provider and are subject to its own retention window. Server logs are rotated on a short schedule by our hosting provider.
6. Your rights
You can update your avatar and your security settings (password, two-factor, passkeys, active sessions) from the account page, and permanently delete your account there — we email you a confirmation link, and organizations where you are the only member are deleted with it. An organization owner can export the organization's data as JSON from the settings page. To correct your name or email address, or to request a copy of your personal data, contact us at the address below and we will action it. Depending on your jurisdiction you may have additional rights (access, rectification, erasure, portability, objection).
7. The AI assistant
The in-app assistant and the automatic build-fix feature send data to Anthropic to generate a response: the messages you type, and — so it can answer them — details of your projects, environments, services, deployments, databases, domains and usage. Automatic build fixes additionally send the contents of the repository files being diagnosed. Conversations are stored so you can return to them, are visible only to you — other members of your organization cannot read them — and are deleted 180 days after their last message. The assistant has read-only tools: it cannot change anything without you approving a specific action first, and it is never given your environment variable values, your database credentials, or the output of your running application.
8. Security
Passwords are hashed, sessions can be revoked remotely, and optional two-factor authentication and passkeys are available on every account. Data is encrypted in transit. Tenant data is isolated per organization at both the application layer and the database layer (row-level security). Application secrets — environment variables, managed database passwords — are encrypted at rest with AES-256-GCM and are never displayed back to you anywhere in the product. Note that if your own application prints a secret to its logs, that output is visible to members of your organization in the log console; we cannot filter your application’s output. Our staff can access tenant data for support and can sign in as a user to reproduce a problem; that access is limited to platform administrators, who must use two-factor authentication, and each such sign-in is recorded in the audit log of every organization that user belongs to, naming the administrator. If you would rather keep a secret in your own vault (Azure Key Vault, AWS Secrets Manager, Google Secret Manager, HashiCorp Vault), we store only a pointer to it and read the value when your app is deployed, so we hold no copy.
9. International transfers
Our processors may store or process data outside your country. Where required, those transfers rely on standard contractual clauses or an equivalent safeguard offered by the processor.
10. Changes to this policy
We will notify you of material changes to this policy by email or an in-app notice before they take effect.
11. Contact
Privacy questions or data requests: [email protected].