Privacy

What we keep, and for how long.

This page says what happens to the information you give Cents Security. It is short because there is not much of it. Last updated on 26 October 2026.

When you scan a site

We fetch the address you typed, its home page, the files that page loads, and public records about the domain. The result is a report, stored for thirty days under a random identifier so you can come back to it or share it. After thirty days it is deleted.

A check needs an account, so it runs as you, the same way a watched site does. The report contains what the site showed to any visitor and nothing about you, and the site being scanned is not told who asked. Before you have an account we count, as one number a day, how many times the screen asking for one was shown: not who saw it, and not which site it was for.

One check run from its own page needs no account. Its answer goes back to your browser and is not stored; we count, as one number a day, how many were run.

If you give a business profile (monthly visitors, order value), it is stored with the report so the arithmetic can be shown. It is not used for anything else.

When you open an account

We store your email address, a scrambled form of your password that cannot be turned back into the password, the date you joined, your plan, and the sites you have added. Passwords are hashed with scrypt.

When an account is new we ask a few questions: which describes you best, how many people work there, and, if you choose to answer, your name, your company, the kind of business, what brings you here and where you heard about us. We keep the answers with the account and count them together to learn who the product is for and what to build next. They are not shown to anyone else, not sold, and not used for advertising. You can change them on the account page, and they go when the account does.

Signing in sets one cookie, cents_session, which scripts on the page cannot read and which is removed when you sign out. Three more last ten minutes at most and only while you sign in: cents_pending between your password and the code we email you, when two-step sign-in is on, cents_email between asking for a code by email and typing it in, while we hold the address you typed, and cents_oauth while you sign in with another service. There is no analytics script, no advertising pixel, and no session recording.

Each time somebody signs in, or tries to, we add one to a count for the day: how they signed in (a password, a code, Google, Microsoft, LinkedIn or GitHub) and whether it worked. Not who, and not from where.

Every report you run is kept on your account for the thirty days a report lives, so your dashboard can list it; the link still opens for anybody you send it to. If you turn on alerts by email, we send them to the account’s own address and nowhere else. If you make a deploy hook, we keep a fingerprint of its token, never the token.

The person who runs the site can look up one account at a time by its exact address, to help with it, and can change its plan, confirm its address or mark a site proved; each change is written down with the account’s id and the time. No page lists accounts.

You can download everything we hold about you, change your password, or delete the account and every site on it from the account page. Deletion is immediate and not reversible.

What your own browser keeps

Three things, all optional, and none is sent to us or tells anyone who you are.

After a check, your browser remembers the site, the total and the date so the front page can offer it again. That list is kept in this browser’s own storage, holds eight sites at most, never leaves your device, and has a “Forget this list” control beside it.

If you choose a light or dark appearance at the foot of any page, one more cookie, cents_theme, holds the word light or dark so the next page arrives in the right colours. Choosing “Match my device” removes it. It is not set unless you choose.

If you choose pounds, euros or dollars on the plans page, one cookie, cents_currency, holds that word so every price is shown in it. Until you choose, we guess from the language your browser asks for, and keep nothing.

When you write to us

A message through the contact page is kept for ninety days with the name, business, email address, phone number and words you gave, so it can be answered and found again, and is emailed to the address that answers it. It is used to reply and for nothing else.

When you use a business's website check

Some businesses put our check on their own website, in their own name. If you use one, the address you check, your email and your name if you give it go to that business, which decides how it uses them. Its own privacy notice, linked from the form, says how. We keep them for that business for 90 days, or until it deletes its account, and use them for nothing of our own. You do not need an account with us, and we set no cookie and keep nothing in your browser.

When a site is watched

A watched site is scanned on the schedule you chose for it, every day or every week. Each scan is kept as a report for ninety days, so any two checks in that time can be compared, and is deleted with the site or the account if that comes first; the timeline of what changed is kept with the site until the site or the account is removed. If you set a webhook address, we send a short message there when something new and serious appears, and nowhere else.

Codes we email you

Signing in with a code, confirming your address, finishing a two-step sign-in, resetting your password and deleting an account that has no password each work by a six-digit code sent to your address. We keep a scrambled form of the code for ten minutes and nothing else about the message. If you sign in with Google, GitHub or Microsoft, we keep that service's id for your account and the verified address it gives us, and nothing else from it.

Who else sees anything

Nobody is sold or given your data. A scan does ask public services about the site being checked, one question each, and none of them are told who asked: certificate transparency logs (crt.sh, and Cert Spotter where an operator has an account with it), domain registries over RDAP, public DNS resolvers including the filtering resolvers run by Quad9 and Cloudflare, the OSV vulnerability database, Google’s Web Risk service where an operator has enabled it, and the cloud storage providers a site references. Each receives the hostname or a public address, and nothing about you.

The site runs on Contabo, which handles the request and keeps ordinary server logs for a short period under its own policy. Before a scan, a single check, a comparison, a new account or a reset code, Cloudflare Turnstile checks that a person is asking: it receives your address and what your browser tells it, under Cloudflare's own policy, and we are told only whether it passed. Codes are delivered by Resend, an email delivery service, which receives your address and the message. Signing in with Google, GitHub or Microsoft sends you to that service, which then tells us who you are.

Your rights

Maksym Gavrylenko, 1A South Street, Birmingham, UK, B170DB, runs Cents Security and is responsible for the data on this page.

Under UK and EU data protection law you can ask for a copy of your data, ask for it to be corrected, or ask for it to be deleted. The account page does all three without asking us. For anything else, write to mgavrylenko05@gmail.com.