Privacy
This page is about the website. The app is a separate matter and collects nothing at all — that is covered in the documentation on privacy.
What this site records
Page views and a small number of named clicks, through Umami, which runs on a server I operate. It is not Google Analytics, and no advertising company is involved.
No cookies. No local storage. Nothing is written to your device and nothing is read back from it. You can confirm that yourself: open your browser's storage inspector on any page of this site and both will be empty.
Here is the whole of what a visit leaves behind. Once for the visit: the browser, the operating system, the device type, the screen size, the language your browser asks for, and a country, region and city. Then for each page you open: its address and its title, anything following the ? in that address, the page you followed a link from, and — on a handful of links — a fixed label such as download-cta. Nothing you type is recorded, because there is nothing on this site to type into.
The country, region and city are read from a database file sitting on that same server. No request about you goes anywhere else to work them out.
Visits are counted from a hash of your IP address, your browser's user agent and this site's identifier, combined with a rotating salt. The hash cannot be reversed, and the IP address is not stored beside it. The salt changes once a month. Within a calendar month the same browser therefore counts as the same visitor; once it rolls over, as a new one.
What this site does not do
- There is no cookie banner, because there are no cookies to consent to.
- No advertising, and no profiling.
- No session recording, and no attempt to identify you.
- No fonts, scripts, images or styles loaded from anyone else's servers. The typefaces are served from this site, which is why no request goes to Google when you open a page.
The one place an address does land
The analytics records never hold an IP address. The web server in front of them does. Like almost every web server, it writes a plain access log — one line per request, giving the address the request came from, the time, and what was asked for. Nothing reads that log, nothing reports on it and it feeds none of the figures above, but it is a file with IP addresses in it, and you should hear that from me rather than assume otherwise.
It rolls over at ten megabytes and rolled copies are discarded after ten days. On a site this quiet that is slower than it sounds: the current file has been filling since March.
Who else sees any of this
Nobody. It sits on a server I run, not on an analytics company's platform, and none of it is sold, shared or passed to anyone.
That undertaking is smaller than it sounds, which is rather the point. What is stored is aggregate and tied to no one, so there is nothing in it about you to sell, share or hand over in the first place.
Hosting
The site is served by GitHub Pages. GitHub receives your request in the ordinary course of delivering the page, including your IP address, and handles it under its own privacy statement. That is true of any web host and is outside my control.
Your rights
What is recorded is aggregate and is not linked to you, so in most cases there is nothing individual to retrieve, correct or erase. If you have a question about any of this, or want to raise a concern, use the contact route below.
Contact
Email support@devdrivecacheclean.com. That reaches me directly, and nothing you send there is public.