Furio Sign in Try it

Privacy Policy

Last updated: 20 November 2026.

This policy covers the getfurio.com website and Furio Cloud: visiting the site, signing in, workspaces, the manifests you upload, payments and email. It also covers the anonymous build counts of the open-source Furio tools, the furio command and the GitHub Action.

Controller

H2Code, VAT no. IT15572751004, Via del Pigneto, 00176 Rome, Italy. For anything about your data, use the contact at the bottom of this page.

Account

If you sign in with GitHub, GitHub gives us your GitHub user id, username, name (if set) and primary verified email address; we ask only for permission to read your profile and email addresses, not your repositories. If you sign in by email, we process your email address and send you a one-time link, valid 15 minutes. We store your email, name, the sign-in methods you used and when the account was created. Legal basis: performance of the contract.

Workspaces and members

For each workspace we store its name, its GitHub account, its plan and the email addresses of its members, which the person who invites them provides. Legal basis: performance of the contract.

Uploaded manifests

We store the last valid .architecture/ folder of each repository (manifest and diagrams), the repository name, the commit and the upload time, and the map built from them. We also keep the history of uploads (each upload's folder and what it changed on the map) for 7 days on Free, 90 days on Individual and one year on Business, then delete it automatically. For pull requests, the GitHub Action can send the proposed manifest to compare it with the map: it is checked and answered, never stored.

Manifests can contain team names, links and other details you choose to write: write only what is needed. On the Free plan this content is public. For the Free plan we ask GitHub's public API whether a repository is public; nothing about you is sent. Upload tokens are stored only as a fingerprint.

Payments

Purchases are handled by Stripe acting as merchant of record, as an autonomous data controller: your card number never reaches our servers, and the receipt or invoice is issued by Stripe. From Stripe we receive the outcome of charges and the state of the subscription, linked to your workspace. Stripe may transfer data outside the EU under the EU Standard Contractual Clauses; see Stripe's privacy notice.

Domain checks

On paid plans, for each domain declared on the map we query the public registration database of its registry (RDAP), connect to the domain's web server to read its certificate, and resolve its DNS, once a day; we store the latest results. Nothing about you is sent to these services beyond the domain name.

Provider status pages

On paid plans, every 5 minutes we read the public status page of each provider named in the manifests (Stripe or Vercel, for example), to show its incidents on the map. We ask only the fixed addresses of a list we keep, never an address taken from a manifest, and once per provider however many workspaces use it: nothing about you or your workspace is sent. We store the incidents each page reports.

Email

Sign-in links and the email to a new member of a workspace, which shows the address of the person who added them, are sent through Brevo, an EU email platform acting as our processor. So are, on paid plans, the domain alerts, the daily digest of new problems on the map (members can turn it off per workspace) and the provider incident emails, one when an incident starts on a provider the map uses and one when it closes (members choose per workspace which incidents: major and critical by default, minor too, or none). They are part of the service. We do not send marketing email.

Analytics

To count visits to the public pages of getfurio.com (the home page, the documentation and the legal pages) we run a self-hosted analytics tool (Umami) on our own server in the EU. It sets no cookies and uses no cross-site identifiers; it stores aggregate statistics only. The dashboard and the hosted maps are not measured. If we ever add measurement tools that require consent, we will ask first.

Build counts of the command and the Action

The open-source tools count builds, so that we know whether Furio is used and on what. Each furio build, from the command or from the GitHub Action, sends our analytics server (the same self-hosted tool, in the EU) one event with the Furio version, the operating system, whether it ran in CI and, outside CI, a random number made on that machine. In GitHub Actions on github.com the event carries, in place of that number, a coarse fingerprint of the repository: one of 65,536 values, each shared by more than twenty thousand of the numbers GitHub gives to repositories, so that we can count how many projects build without the value leading back to one. Whoever knows the number of a repository can compute its value. The event carries no name, no path and nothing from your manifests, and no other command sends anything.

The event names a placeholder address in place of yours: the analytics tool stores no IP address and derives no location from it. The first build on a machine says that builds are counted and sends nothing. You can turn the counts off at any time with furio telemetry disable, or by setting FURIO_TELEMETRY=0 or DO_NOT_TRACK=1, in a workflow too. Legal basis: our legitimate interest in knowing whether the software is used. The guide shows the whole event.

Cookies

We set one essential session cookie (HttpOnly) that keeps you signed in for up to 30 days and is deleted on sign-out. Signing in with GitHub uses a second technical cookie that lasts at most 10 minutes. No tracking cookies, no consent banner. Your display preferences, such as the light or dark theme, are remembered in your browser only and never sent to us.

Server logs

Our server records technical logs of requests (address, path, time, outcome) to operate and protect the service. They are kept for 30 days. Legal basis: legitimate interest in security.

Where

Our servers are in the EU (Italy).

Retention

Account, workspace and manifest data are kept while the account or workspace exists, including while a paid workspace is locked after its subscription ended, so that it can come back. You can delete your account from the dashboard at any time. A workspace can be deleted only by its owner, its most senior member, once its subscription has ended; the other members can leave it. When the owner deletes their account, the workspace passes to the next member by seniority; the only member of a workspace must delete it before deleting their account. Deleting happens at once, and deleted data leaves our backups within 30 days. We keep only what the law requires (invoicing records are kept by Stripe as merchant of record). You can also ask us to do it for you.

Your rights

Under the GDPR you can request access, rectification, deletion, restriction and portability of your data, and object to processing based on legitimate interest, from the contact below. You can also lodge a complaint with your supervisory authority (in Italy, the Garante per la protezione dei dati personali).

Contact

privacy@getfurio.com