Coralis
TermsPrivacy

Privacy Policy

Last updated 20 November 2026

Coralis is a cloud for your AI accounts: it runs sessions, services and API endpoints for the projects you create. This page says what we keep, why, who helps us run it, and what you can do about it. We wrote it to be read, not skimmed past.

Who we are

Coralis is run by [company name], [address], [registration number] (“we”). We are the controller of your data under the GDPR. Write to hello@coralis.dev about anything on this page.

What we keep, and why

WhatWhyLegal basis
Your email address, name and picture (from the sign-in link, Google or GitHub)To sign you in and tell you about your accountContract
Sign-ins: when, your IP address and browserTo keep you signed in, show your devices, and stop abuseContract; legitimate interest (security)
Your projects: their files, sessions and every step a session took, services and their logs, domains, endpointsThis is the service itselfContract
API keys you paste and environment variables you addTo call the providers and run your services. Kept encrypted (AES-256-GCM); a sensitive value is never shown againContract
Which AI accounts you connected, their plan and their limitsTo send work where there is roomContract
Your plan and subscription idTo give the project its planContract

Your AI subscriptions. A Claude or Google account is signed in by you, on Anthropic’s or Google’s own page, inside your sandbox, with their own tool (Claude Code, Gemini CLI). Its login stays with that tool in your sandbox: we never read, keep elsewhere or pass on those credentials, and we never call those providers with them ourselves. What you send to an AI goes to that provider under your own agreement with them.

We do not sell your data, show ads, or use your projects to train any model. There are no analytics or advertising cookies.

Cookies

One cookie: coralis.session_token, which keeps you signed in. It is needed for the service to work, so no consent banner is involved. Websites you host on Coralis may set their own; those are theirs.

Who helps us run it

WhoForWhere
[hosting provider]The servers everything runs on[EU country] (projects in the US region: [US location])
ResendSending sign-in linksUnited States (EU Standard Contractual Clauses)
StripePayments. We never see or keep your cardEU and United States (SCCs)
CloudflareDNS and certificates for coralis.devGlobal (SCCs)
Google, GitHubOnly if you sign in with themUnited States (SCCs)
Backup storage: [provider]Encrypted nightly backups[EU country]

How long we keep it

  • Everything in your account, until you delete the account or a project. Deleting is immediate in the service.
  • Encrypted backups keep a copy for up to 6 months after that, then it is gone; a restore never brings back deleted accounts.
  • Service logs: the last 5 MB per service. Sign-ins: while they are valid (30 days, renewed while you use Coralis), and until you sign out or delete the account.
  • Invoices: as long as accounting law requires ([5] years in [country]), at Stripe.

Your rights

You can see, download, correct and delete your data, object to how we use it, and move it elsewhere:

  • Download it all: in the dashboard, “Download my data” under your name gives one file with everything we keep about you. Project files download from each project’s Files tab.
  • Delete it all: “Delete account” in the same place deletes your account, every project you own and everything in them.
  • Anything else: hello@coralis.dev. We answer within a month.

You can also complain to a data protection authority; in Poland that is the Prezes Urzędu Ochrony Danych Osobowych (uodo.gov.pl).

Security

Every project runs in its own sandbox (gVisor), with limits on memory, CPU and network. Keys and variables are encrypted with a key only the server holds. Traffic is HTTPS only. If something goes wrong with your data, we tell you and the authority within 72 hours.

Changes

If this page changes in a way that matters, we email you before it applies.