Legal · beta
Privacy policy
Last updated 16 November 2026
SiteOps is a website monitoring service in public beta. This page says what data it keeps, why, who else handles it, and for how long. It is written to be read, not to cover every case; if something is unclear, write to uros@foldnine.dev.
Who is responsible
SiteOps is run by Uroš Orolicki, an individual based in Serbia, who is the controller of the personal data described here. Contact: uros@foldnine.dev.
This policy follows the Serbian Law on Personal Data Protection (Zakon o zaštiti podataka o ličnosti, “Sl. glasnik RS” 87/2018) and, for people in the EU and EEA, the GDPR.
What SiteOps keeps
- Your account: name, email address, a hash of your password (Argon2id; the password itself is never stored), when you verified your email, and the workspaces you belong to with your role. If you sign in with Google or GitHub, SiteOps keeps which provider it was and that provider’s account ID for you, plus the name and verified email address it returns; it never sees your Google or GitHub password and asks for no other access.
- Sessions: one cookie,
siteops_session, which keeps you signed in. Only a SHA-256 hash of its value is stored on the server. A sign-in ends when you close the browser, after 60 minutes without activity, or 12 hours after you signed in, whichever comes first. It is strictly necessary, so there is no cookie banner. SiteOps uses no analytics, advertising or third-party tracking cookies. - What you monitor: the websites and API endpoints you add, the check settings, and the results: status, timings, response headers from an allow-list, a short body excerpt, certificate and DNS details, broken links. Incidents, notes and the activity log you and your team create. Alert channels you configure (email addresses, chat or webhook destinations).
- The free site check (no account): the URL you enter, its result, and a one-way hash of your IP address, used only to limit how often one address can run checks. The IP address itself is not stored.
- Abuse limits: sign-in and sign-up attempts are counted per IP address and per email address to stop password guessing. These counters include the IP address.
- Emails we send you: verification, password reset, alerts and reports you set up.
SiteOps does not sell data, does not use it for advertising, and does not train models on it.
Why (legal basis)
- Account, sessions, monitored sites and results, alerts: to provide the service you signed up for (contract).
- Abuse limits, the hashed IP on free checks, and security logs: to keep the service and the sites it checks safe (legitimate interest).
Who else handles it
- Hosting: SiteOps runs on a virtual server rented from Hetzner Online GmbH in its Falkenstein data centre in Germany. The database is stored there. Hetzner acts as a processor under its data processing agreement.
- Backups: once a day an encrypted copy of the database is stored in Google Drive (Google Workspace). It is encrypted on the server, before it leaves, with a key only the operator holds, so Google cannot read it. Google acts as a processor under the Google Workspace Cloud Data Processing Addendum.
- Email delivery: Google (Google Workspace, Gmail SMTP) sends the emails SiteOps sends. Google receives the recipient address and the message content. Google acts as a processor under the Google Workspace Cloud Data Processing Addendum.
- Network: Cloudflare carries all traffic to siteops.foldnine.dev through a Cloudflare Tunnel and terminates HTTPS, so it handles requests, including your IP address, in transit. It does not store your account data.
- Password screening: when you choose a password, SiteOps sends the first 5 characters of its SHA-1 hash to the Pwned Passwords service (api.pwnedpasswords.com, run by Have I Been Pwned with Cloudflare) to check it against known breaches. The password, the full hash and your email address never leave the server.
- Sign-in with Google or GitHub (optional): you sign in on their site, under their own privacy policies, and they tell SiteOps who you are. They learn that you signed in to SiteOps.
- Payments: if you buy a paid plan, Polar (polar.sh) sells it to you as merchant of record, and its payment provider Stripe processes the card. They receive your name, email, billing address and payment details under their own privacy policies. SiteOps receives only your email address, the plan and the payment status, never your card number.
Germany and Ireland are in the EU, which Serbian law treats as offering adequate protection. Where a provider may process data outside the EU, it relies on standard contractual clauses.
The monitoring worker sends requests to the websites you add. Those sites see requests from the SiteOps server’s IP address with a SiteOps user agent, not anything about you.
How long
A job deletes old data every hour. The periods below are the ones it runs with.
- Check results: 90 days.
- Activity log and incident timeline entries: 365 days.
- Free site checks and their hashed IPs: 30 days.
- Sent alert records: 90 days.
- Email verification and password reset links: 7 days after they were used or expired.
- Sessions: until they expire (at most 12 hours) or you sign out, then up to 1 day.
- Abuse-limit counters with IP addresses: up to 7 days.
- Your account, workspaces, websites and incidents: until you delete them or ask us to. Deleting a website deletes its checks, results and incidents.
- Backups: daily, kept for 14 days, so deleted data is gone from backups 14 days after deletion.
Your rights
You can ask for a copy of your data, have it corrected, have it deleted, object to processing, or ask for it in a portable format. Write to uros@foldnine.dev from the email address on your account; you will get an answer within 30 days. You can also complain to the Commissioner for Information of Public Importance and Personal Data Protection (Poverenik, poverenik.rs) or, in the EU, to your local data protection authority.
Security
Traffic is encrypted with HTTPS. Passwords and session tokens are stored only as hashes. Backups are encrypted on the server before they are copied off it, with a key only the operator holds. The monitoring worker runs separately from the web app, in a network that cannot reach private addresses or cloud metadata. No system is perfectly secure; if a breach affects your data, you will be told without undue delay.
Changes
If this policy changes in a way that matters, account holders get an email before it takes effect. The date at the top always shows the current version.