Privacy policy

Effective October 22, 2026

This page covers what Eris collects about you, why, who else receives it, how long we keep it, and what you can ask of us. We collect only what running Eris needs, and we never sell your data.

It applies to you as a visitor of erisdeploy.com and as a customer signed in at app.erisdeploy.com. It does not cover what your apps hold: the containers, databases and files on your own servers, and the backups in your own buckets. That data is yours, and Eris handles it only on your instructions.

Who we are

Eris is run by its two founders, Alexander Satretdinov and Ruslan Kosolapov, individuals living in Bulgaria. We are joint controllers of your personal data under Article 26 of the GDPR. We have agreed in writing that both of us answer for every processing described here and that one address takes every request: hello@erisdeploy.com. You can exercise your rights against either of us.

What we collect and why

Your account

You sign in with GitHub or Google. From GitHub we receive your login, your user ID, your avatar URL and your verified primary email address; from Google, your account ID, name, avatar URL and email address. We keep the login or name and the avatar to show who is signed in, the ID to recognise you next time, and the email address to send you sign-in codes and alerts. You can change the address in Settings. When you install the Eris GitHub App, we keep its installation ID so we can read the repositories you choose.

We need this to provide the service you signed up for (GDPR Article 6(1)(b)).

What you deploy

To build and deploy your repository we keep its name or URL and, for each deploy, the commit hash, message and author's name and login, as GitHub reports them. We also keep the addresses of the servers you connect, your app and server settings, and a history of what happened in your account, kept for 30 days. Registry passwords you give us are stored encrypted. This, too, is the service itself (Article 6(1)(b)).

Sessions and cookies

Signing in sets the cookie eris_session, which lasts seven days from sign-in. Two short cookies, eris_sign_in and eris_sign_in_code, hold a sign-in in progress for ten minutes. These are strictly necessary and need no consent. Your browser also keeps your theme, language and layout choices in local storage; they never leave your device.

Your consent choice is one cookie on erisdeploy.com, read by both sites, and it lasts six months. Google's cookies, _ga* and _gcl_*, are set only if you allow them (below).

Emails

We email you sign-in codes, links to confirm an address, the alerts you set up, and a notice when your account is deleted. We keep a record that each email was sent and whether it was delivered, but not its text. Bounces and complaints mark an address as undeliverable.

Telegram

If you connect Telegram in Settings, we keep the ID of your chat with our bot and send your alerts there. We keep a record that each alert was sent, but not its text. Disconnecting in Settings, or deleting your account, removes the chat ID.

Assistants

When you allow an assistant such as Claude Code to use Eris, we keep the grant: which client, what it may do, and when it was given and last used. You can revoke it in Settings.

Logs and errors

Our servers log the requests they answer, which can include your IP address, and the errors they hit. When something breaks in the Dashboard, on Eris's servers or in the agent on your server, an error report goes to Sentry. Reports carry the request's method and URL, but not its cookies, headers or body. We do this to keep Eris secure and working, which is our legitimate interest (Article 6(1)(f)).

Telemetry and ad measurement

Both sites show a banner on your first visit. Until you allow something there, nothing is requested from Google. You can allow two things separately:

• Telemetry. Google Analytics 4 records the pages you view and what you do in Eris: signing up or in, connecting a server, starting and finishing a deploy, giving an assistant a grant. It ties them to your account by its ID, never your GitHub or Google login.
• Ad measurement. If you came from one of our Google Ads, we keep the ad's click ID and tell Google Ads when you first connect a server and first deploy, so we know which ads work. We keep the click ID for 90 days at most. We never use your data to show you ads.

Both rest on your consent (Article 6(1)(a)). You can change your mind at any time from Cookie settings in the footer of erisdeploy.com or in the Dashboard's account menu; withdrawing deletes Google's cookies and the IDs we stored for that purpose. Google keeps Analytics data for 14 months. Read how Google uses information from sites that use its services.

Writing to us

When you email hello@erisdeploy.com, we keep the conversation so we have it the next time you write.

Who receives your data

We use these providers to run Eris, each under a data processing agreement:

• Hetzner, Germany: the servers that run Eris and its database, in Falkenstein (fsn1).
• Cloudflare: DNS, the network in front of erisdeploy.com and app.erisdeploy.com, and storage for database backups in Western Europe.
• Amazon Web Services: sending email, through Amazon SES in Frankfurt (eu-central-1).
• GitHub: signing in, and reading the repositories you choose.
• Google: signing in with Google, and Analytics and Ads if you allow them.
• Sentry: error reports.
• Better Stack: our server logs.

If you connect a Telegram chat, Telegram receives the alerts we send there. It is not our processor: you chose it, and it handles them under its own privacy policy.

The two of us can read your account through an internal console, and do so only to answer you, to fix something that broke, or to stop abuse. We disclose data to authorities only when the law requires it.

Transfers outside the EU

Four of these providers are in the United States:

• GitHub and Google, under the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses in their data processing terms.
• Sentry, under the Standard Contractual Clauses in its data processing terms.
• Better Stack, which keeps our logs in the US West region for three days, our proxy's access log included, under the Standard Contractual Clauses in its data processing terms.

Telegram is outside the EU as well. Alerts go there only because you connected a chat to receive them (Article 49(1)(b)).

How long we keep it

• Your account and what it holds: until you delete it.
• Database backups: 30 days.
• Server logs: three days.
• Your account's history of events: 30 days.
• Sessions: seven days after you last use one.
• Your consent choice: six months, after which the banner asks again.
• Ad click IDs: 90 days at most.
• Google Analytics data: 14 months.

Deleting your account

You can delete your account at once from Settings, under Account. Your servers, apps, databases, deploy history, sign-in methods and assistant grants go with it, every session ends, the GitHub App installation is removed, and we email you that it is done. What runs on your own machines and sits in your own buckets stays where it is. If you cannot sign in, write to hello@erisdeploy.com and we will delete it for you within a month. Deleted data stays in our database backups for up to 30 days and in our logs for up to three; Google Analytics keeps its data for 14 months.

Your rights

Under the GDPR you have the right to:

• know what we hold about you and get a copy of it;
• have it corrected;
• have it erased;
• restrict or object to how we use it, including what we do on our legitimate interest;
• receive it in a portable format;
• withdraw a consent at any time, without affecting what was done before.

Much of this you can do yourself in Settings. For the rest, write to hello@erisdeploy.com. We answer within a month and may ask you to confirm the request from the email address on your account.

You can also complain to a supervisory authority. Ours is Bulgaria's Commission for Personal Data Protection (КЗЛД); you may also go to the one where you live or work.

Security

Everything between your browser and Eris travels over HTTPS. Registry passwords you give us are encrypted in our database, and session tokens and sign-in codes are stored only as hashes.

Changes

When this policy changes, we update the date at the top. If we start using your data for a new purpose that needs your consent, the banner asks you again.

Adapted from the Basecamp open-source policies / CC BY 4.0