Privacy

What this site collects

This site counts visits with Google Analytics 4. If you accept, Google's script reports the page's path, without any query, to Google, which processes it for the site, and sets identifiers in your browser — a client id, in cookies or similar storage.

The site's own code asks for one page view per page: no event, no user id, Google Signals and ads personalisation off. Google Analytics 4 anonymises your IP address by default.

Consent

Google's script loads only after you accept: until then this page has asked Google nothing. Accept, in the banner, loads Google's script once; Decline loads nothing, now or on any later page.

Dismissing the banner — Escape, or reading on — is a refusal. The answer is kept in this browser, under fugaro:analytics-consent in localStorage.

To withdraw, use the banner here: it always offers the choice again. Declining stops reporting at once, on this page too, and deletes Google's cookies (_ga and the rest) from this browser.

What this site does not do

• It sets no cookie of its own.
• It has no account, form or comment box.
• It loads nothing from another origin except Google's script, and only after you accept.
• It keeps no log of its own. The host's request logs are the host's, and this repository does not control them.

Where it runs

The command line tool and the desktop console run on your own machine. They talk to your own Google Cloud project, your own git provider and the model provider you configured, and to nothing the Fugaro project operates. Nothing is reported anywhere: no telemetry, no usage statistics, no crash report, no identifier.

The update check

The one thing the tool asks outside your own accounts is whether a newer release exists. It asks GitHub, at most once a day: one request to this repository's public release list, carrying nothing about you, with the answer kept on your machine.FUGARO_NO_UPDATE_CHECK=1 or update_check: false turns it off;fugaro doctor, which you run yourself, still reports your version.

The phone app

The phone app is built to sign in to your own Firebase project — the project id you type in for an installation — and to read only what that project's rules grant it. Signing in, it names the paired device to that project, and nothing else of yours goes with it. Its writes go into the mailbox your own installation reads. Its two credentials, a Firebase ID token and the pairing key, live in the device's secure storage, the Keychain or the Keystore, and nowhere else.

Crash reports and anonymous usage. The app version that carries these reports sends two things to a Firebase project the Fugaro project operates, and not to your own: crashes, through Firebase Crashlytics, and anonymous usage, through Firebase Analytics. A crash report holds the crash's logs, diagnostics and app performance data; the usage count says which screens were opened. Firebase gives the app an app-instance identifier of its own, and that travels with both. Google holds all of it, as Firebase's processor, for the Fugaro project, under Google's Firebase privacy policy.

Never sent: the contents of any message, anything from your installation or its mailbox, your credentials and your keys. The reports are read to find and fix crashes and to see which screens are used, and for nothing else. The app carries no advertising identifier.

The app versions that carry these reports send them. There is no switch inside the app to turn them off: uninstalling the app stops them, and not installing it avoids them. The command line tool and the console are unaffected: they carry none of these reports. Earlier builds of the app send nothing at all.

Deleting your data

Everything else the software holds lives in your own accounts, your own cloud project and your own devices, and removing the installation removes it. The crash reports and anonymous usage above are the exception, and deleting the app does not remove them: Google holds them for the Fugaro project, under the policy linked above. Uninstalling the app stops the sending. It does not take a report already sent out of Google's hands, and the issue tracker is where to ask about one.

Contact

Questions and bug reports go to the repository's issue tracker. Report a vulnerability through SECURITY.md's private route, never in a public issue.