Privacy
What Senriko stores, why, and for how long. Written from the code rather than from a template.
Draft. This describes what the service actually does with data and has not been reviewed by a lawyer. It must not be published as it stands.
Last updated: August 18, 2026
Your account
Your email address and a hash of your password - never the password itself. The email is also the first address alerts go to, and you can add or remove others at any time. Sessions are stored as hashes of opaque tokens, so a copy of our database does not let anyone sign in as you. The session cookie is httpOnly and SameSite=Lax, lives for 30 days, and carries nothing but the token.
The websites you watch
The addresses you ask us to check, and what we observe on them: response codes, timings, page titles, canonical URLs, which analytics tags are present, and the values you accepted as normal. We store hashes for comparison where the full value is not needed. We do not crawl anything you have not added, and we obey robots.txt on everything except the pages you explicitly asked us to watch.
Form checks
If you set up a form check, we store the selectors it uses and the values it types in. Those values are ours, not yours and not a real person's: every check submits as a generated identity on our own domain, with a reserved phone number and a message that says in plain words that it is a test and nobody should be contacted. You can see the exact values in Settings, and they are deliberately not editable - a filter you built against them would silently stop matching.
Screenshots
When a form check fails we keep a screenshot of the page so you can see what we saw. They are private, served only to your own account, and swept on a schedule: 3 days on Free, 14 on Starter, 30 on Pro, 60 on Business and above. The sweep deletes the file from object storage first and only then drops the reference, so a deleted screenshot cannot survive as an orphan nobody can find.
People who visit this website
Analytics run only after you accept them in the banner - nothing is set before that, and declining is a single click that we remember. When accepted, Google Analytics 4 receives the usual page-view data. The free conversion checker stores nothing at all: not the address you type, not the result. Our own monitoring checks identify themselves in every request with a User-Agent naming this site.
How long we keep things
Check history follows your plan: 7 days on Free, 30 on Starter, 90 on Pro, 365 on Business, 730 on Agency and Enterprise. Screenshots follow the shorter schedule above. The site chronicle - the record of what happened to a website - is kept for one year. Usage records for billing are kept while the account exists. Deleting a website deletes its checks, findings, incidents and chronicle with it; deleting your account deletes the workspace and everything in it.
What you can do about it
You can export your data and delete everything today, and the export is the one to reach for first. Both are in Settings: the export is one file holding your workspaces, sites, checks, incidents, monthly summaries and chronicle, minus the screenshots, which are served only to a signed-in session. Deletion takes your password to confirm and removes the workspace, its websites, checks, incidents, screenshots and chronicle. There is no soft-delete holding pen and no reactivation window - when it is gone it is gone, which is why the copy comes first.
Who else sees it
The service runs on infrastructure we rent, and email is delivered through a sending provider; both see what they need to do that and nothing more. Analytics data goes to Google when you have accepted analytics cookies. We do not sell data, we do not share it with advertisers, and we do not use what we observe on your websites to build anything that is offered to anybody else.
How it is protected
Traffic is HTTPS end to end. Passwords are hashed with scrypt at parameters we raise as hardware gets faster, and an old hash is upgraded the next time you sign in. Secrets in our own admin are stored encrypted and never displayed back - only reset. Every administrative action against an account is written to an audit log. Active checks - the ones that submit a form - only run against a website after somebody proved they control it, by a meta tag or a DNS record.
Asking us about any of this
Write through the contact page. A person reads it. If you believe we hold something we should not, say so plainly and we will look at the actual rows rather than at a policy summary.