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. The email is also the first address alerts are sent 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 anybody sign in as you.
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 rather than page source.
Form checks
If you set up a form check, we store the selectors and the values it types in. You choose those values, and they should never be real personal data. Every message it sends says it is a monitoring test. What we never store is what your visitors submit: we do not read your inbox or your form backend.
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 deleted automatically after the period your plan specifies.
How long we keep things
Check history and screenshots follow the retention period of your plan. Deleting a website deletes its checks, findings and incidents with it. Deleting your account deletes all of the above.
Who else sees it
The service runs on infrastructure we rent, and email is delivered through a sending provider. Both see the data required to do their job and nothing more. A current list of them belongs here before this document is published.