Privacy

Who we are

ELI5 bot is run by Appstyx SRLS, Via San Morese 9, 50019 Sesto Fiorentino (FI), Italy, P.IVA 06456860489. For anything about your data, email [email protected].

The waitlist

When you join the waitlist we store your email address and when you joined. We use it only to invite you and to email you about access, and we don't share it with anyone except the providers listed below that run our systems.

This site sets no cookies and runs no analytics or tracking scripts. Fonts are served from this site, not from a third party.

The GitHub App

Once you install the app on your repositories, it:

• reads the pull requests it explains: their code, description, commits, and the issues and pull requests they mention;
• copies the repository to a temporary folder to read it, and deletes the copy as soon as the explanation is written;
• writes one comment on each pull request, its own explanation.

We keep the explanation, usage numbers for each run (tokens and cost), the pull request author's GitHub username, and the 👍/👎 reactions and replies the explanation gets, with the usernames of the people who left them. We don't keep your code.

Who processes it

• Railway hosts this website, the service and its database, including the waitlist, in the EU (Netherlands).
• Cloudflare delivers this website to your browser and protects it from abuse, which means it handles your IP address.
• OpenRouter passes the code being explained to the AI model that writes the explanation. It doesn't store prompts or responses, only metadata such as token counts. Our requests only go to inference providers with a zero data retention policy, which keep no copy of what they're sent and so can't train on it.
• GitHub provides the code and receives the comment.

How long we keep it

• Your waitlist address: at most 24 months after you signed up. Ask us and we delete it straight away.
• Explanations and run records, including the pull request author's username: while the pull request is open, then for 90 days after it's merged or closed, and never more than 24 months after they were written. If you uninstall the app or remove a repository from it, they're deleted within 30 days.
• Usage numbers for each run: as long as the run's explanation.
• Reactions and replies, with the usernames of the people who left them: as long as the explanation they belong to, and at most 12 months.
• The temporary copy of your code: deleted as soon as the run ends.
• Service logs: Railway deletes them after 30 days at most.

When runs, reactions and replies are deleted, we keep monthly totals for each installation of the app: how many runs, what they cost, and how many reactions and replies they got. The totals contain no names.

Why we're allowed to use it

• The waitlist: to take a step you asked for before any contract, inviting you (GDPR article 6(1)(b)).
• Explaining pull requests: to provide the service to the account that installed the app (article 6(1)(b)).
• Usage numbers, reactions, replies and service logs: our legitimate interest in running the service securely and making the explanations better (article 6(1)(f)). You can object to this at any time.

Outside the EU

Our database is in the EU, but Railway and OpenRouter are US companies and most inference providers are outside the EU, so your data can also be processed in the United States. Railway and OpenRouter cover these transfers with the EU's Standard Contractual Clauses.

Your rights

You can ask to see the data we hold about you, correct it, delete it, limit how we use it, object to its use, or get a copy in a portable format. Email [email protected] and we'll reply within a month. You can also complain to Italy's data protection authority, the Garante per la protezione dei dati personali, or to the authority where you live.

Last updated 25 October 2026.