Privacy
This describes the GitHub version of Fervio, served at fervio.co. It is written from the code that actually runs, not from intent. Last updated 9 August 2026.
What Fervio stores
Everything below lives in Cloudflare's key-value storage, in the region Cloudflare assigns. Nothing else is kept.
| What | Why | How long |
|---|---|---|
| Your GitHub access token | To read and write the Project on your behalf. It stays on the server and is never sent to the browser. | 7 days, then the session expires |
| Your GitHub username | To show who you are, and to record who owns and who was invited to a map. | Until you ask for deletion |
| Card order on the map | The map layout is Fervio's own; GitHub has nowhere to keep it. | Until the map is deleted |
| Who you invited, and their role | To decide who may open or edit a map. | Until the member is removed or the map is deleted |
| When you signed in, and how many times | To know how many people are using Fervio during the beta. | Until you ask for deletion |
| A share snapshot, if you publish one | So that a share link opens without a GitHub sign-in. This is a copy of the issue titles and states at the moment you published it. | 90 days, or until you revoke the link |
| Your plan, and AI usage this month | To apply the limits of your plan. | Plan: until it changes. AI count: resets monthly |
What Fervio never touches
- Your source code. Fervio never calls an API that reads it. GitHub's consent screen does say "full control of private repositories" — GitHub offers no issues-only permission. The permissions page explains it.
- The content of your issues, as a stored copy. Titles and states are read from GitHub every time you open a map and are not kept, with the one exception of a share snapshot you publish yourself.
- Your email address. Fervio never asks GitHub for it, so it has no way to email you.
- Analytics. There are no trackers, no advertising pixels and no usage-measurement services. A Content-Security-Policy blocks the page from calling any external host.
Cookies
Two, both strictly necessary, neither used for tracking. A session cookie identifies your sign-in for 7 days, and a short-lived cookie guards the sign-in round trip for 10 minutes. Both are HttpOnly, so scripts on the page cannot read them.
Who else is involved
- GitHub — the source of every issue you see, and the identity you sign in with.
- Cloudflare — serves the site and holds the storage described above.
- Polar — handles payment if you subscribe. Fervio never sees your card; Polar tells Fervio only which account changed plan.
- Anthropic — receives the text you type into the AI panel, and only that text, and only when you press the button. Your issues are not sent automatically.
Deleting your data
Deleting a map removes its layout, its member list and any share snapshot. Signing out ends the session and discards the access token. For everything else — the record of your username and your sign-ins — write to [email protected] and it will be removed. You can also revoke Fervio's access at any time from GitHub, under Settings → Applications, which stops Fervio from reading anything further.
Changes
Fervio is in beta and still changing. When what is stored changes, this page and the summary on the home page are updated together — the list above is meant to be countable, so anything new has to appear in it.