Cookies
Last updated 4 September 2026
This website sets no cookies. There is no analytics, no tag manager, no advertising pixel, no session tracking and no third-party script on any public page. That is also why you were not shown a consent banner — there is nothing to consent to.
The one exception
Our own back office at /admin, which only we can sign into, sets a single cookie:
| Name | What it does | How long |
|---|---|---|
dm_admin |
Records that whoever is using the browser has signed in to our back office. It contains a signed expiry time and nothing else — no name, no identifier, nothing about you. | 8 hours |
It is strictly necessary for that page to function, which is the one category of cookie that does not require consent under the Privacy and Electronic Communications Regulations. Unless you have our back office password, you will never receive it.
Things that are not cookies but are worth mentioning
We would rather list everything a browser does on this site than be technically accurate and unhelpful:
- Google Fonts. Pages load the Inter typeface from
fonts.googleapis.comandfonts.gstatic.com. That is a request to Google, which Google may log. It sets no cookie, but it is a third-party request and you deserve to know it happens. - Server logs. Our host, Vercel, keeps ordinary logs of requests — the sort every web server has kept since the 1990s.
- Local storage. Not used. Nothing is written to your browser's storage by any page here.
The app
DebitMate itself is not a web page and has no cookies. It stores its data in a file on your own device and makes exactly one kind of network request — a licence check, described field by field on the privacy page.
If this changes
If we ever add something that sets a cookie or tracks visitors, this page will say so and a consent banner will appear before anything is set. We have no plans to; a page about personal budgeting funded by watching people read it would be a strange thing to build.
← Back to DebitMate