// PRIVACY
A plain answer, because most of the boilerplate this kind of page usually contains doesn't apply here.
last updated 14 Sep 2026
Most of what's on this site is client-side tooling or self-hosted software that runs on the operator's own devices. None of it sets tracking cookies, runs analytics, or sends anything to a third party. This page exists because one of these tools talks to a Google API, and Google requires a published privacy policy before it will let that access run outside a short testing window.
One project on this site includes an offsite backup client that copies the operator's own files to the operator's own Google Drive account. It authorises with OAuth and requests only the drive.file scope, which limits it to files it created itself — it cannot see, list, or modify anything else already in that Drive account.
It collects no information about the account holder or anyone else, and shares nothing with any third party. The only data that moves is the operator's own backup files, travelling from the operator's own storage to the operator's own Drive.
The other tools linked from this site are either fully client-side — nothing you enter ever leaves your browser — or self-hosted software the operator runs for personal use. Visiting this site or using these tools doesn't collect data about you.
There's deliberately no contact address on this page. Every tool described above processes only the operator's own data, in the operator's own accounts, and collects nothing from anyone else — so there's no one else's data to ask about. Google's own OAuth consent screen carries a separate developer and support address for its own use; this page doesn't need to duplicate it, because its only job is describing how the operator's own tools handle the operator's own data.