Security
Last updated 14 November 2026
This is a draft. The highlighted details are still to be filled in, and the text has not been checked by a lawyer yet.
You put our script on every page of your site and our packages inside your servers, so you should know what they do, where what they send ends up, and how to tell us if you find a hole. This page says what is in place and what is not yet. It is not a promise that nothing can go wrong; what happens if it does is below.
Where we stand
The short version. Each item is explained further down.
| What | State | Detail |
|---|---|---|
| The script on your site is pinned by a hash | Done | Your browser refuses a changed file. Released versions are never rewritten. |
| Everything travels encrypted | Done | HTTPS everywhere, with HSTS, so a browser never falls back to plain HTTP. |
| Data stored in the EU | Done | Hetzner, Germany and Finland. Backups in another Hetzner location, every night. |
| Visitors’ IP addresses kept out of the analytics | Done | A visit ID made with a value thrown away each day. The privacy policy has the detail. |
| Passwords checked against known breaches, 2FA, a code on a browser we don’t know | Done | See Your account. |
| Open-source tracker and packages | Done | Read the code: the tracker and the server packages. |
| A status page that stays up when we’re down | Done | status.sitegoose.com is checked and written from a separate server, so it says when we’re down while we’re down. Your own status pages keep answering too: a copy of each is kept on Cloudflare and shown, grey and dated, when our servers can’t answer. |
| Independent security test | Not yet | Planned before launch. The firm, the date and a summary of what was found and fixed will be listed here. |
| Bug bounty | Not yet | Planned, after the security test. Reports are welcome now: see Reporting a vulnerability. |
What runs on your site
The tracking script. Your pages load one file from our domain. The install code carries that file’s SHA-384 hash, so if the file served ever differs from the one you installed, by a single byte, your visitors’ browsers refuse to run it. Once a version is released its files are never changed; a fix is always a new version, and you choose when to move to it. The script loads a few more files for features such as forms and recordings; it carries their hashes too, and on a pinned install a changed one is refused as well.
The script never reads what a visitor types into a field unless you turn on a feature that needs it (a form you built with us, say), and session recordings leave out typed text and the fields you mark as private. It cannot be told to redirect your visitors anywhere but your own domain, and a test or edit you make with us can load styles only from your own domain, so a setting of ours can’t be turned against your site.
The server packages. What you install from npm, PyPI, Packagist and the other registries is the code you can read in the package itself. They send timings, errors and counts, never the bodies of your requests. The only response headers they add are the security headers you choose on the dashboard, and what their first-party proxy passes on is served as data, never as a page or a script.
The source is public: the tracker and the server packages. Each published version is tagged there, so you can match what you installed to what you read.
Where your data is kept
- Servers: Hetzner, in Germany and Finland. Every outside company that gets any personal data from us is on the sub-processors page, with what it gets and why.
- In transit: every connection to us, from your visitors’ browsers, your servers and your own, is over HTTPS. Our domains send HSTS, so a browser that has visited once never tries plain HTTP again.
- Visitors: for plain analytics the IP address is not stored. A visit gets an ID made from the site, the browser and the address together with a random value that is deleted at the end of each day, so afterwards nobody, us included, can link it back. Recordings leave out typed text.
- Backups: copied every night to storage in another Hetzner location. The copies of your account, settings and files are encrypted before they leave the server. A backup that fails or doesn’t run raises an alert to us the next day.
- Payments: card details go straight to Stripe and never reach our servers.
- AI features: nothing is sent to an AI provider unless someone on your team uses an AI feature, and then only what that question needs. What that is, exactly, is on the sub-processors page.
- Our own access: the staff tools need a second factor. Changes we make to a site are in the same audit log as yours.
- How long: what is kept for how long, and what closing your account deletes, is in the privacy policy.
Your account
- Passwords are 8 to 64 characters, with no rules about capitals or symbols, and are refused if they appear in a known breach (only the first five characters of a hash leave our server to check). They are stored as bcrypt hashes.
- A browser we don’t know gets a six-digit code by email before it can sign in with a password. Your usual devices are not asked.
- Two-factor authentication with an authenticator app, and ten one-time recovery codes shown once and stored only as hashes.
- Sign in with Google if you prefer no password with us at all.
- Team roles: each person has a role on each site, and a role can be limited to the areas it needs. Every change to a site’s team or settings is kept in an audit log for a year, with the address it came from.
- Keys and webhooks: the API has a read key and a separate write key per site, so a key on a dashboard somewhere can never change your data. Every webhook we send to you is signed with a secret of its own, so you can check it came from us.
If something goes wrong
If personal data from your sites is exposed, lost or changed, we tell every affected account owner by email within 48 hours of becoming aware, with what happened, what data and how many people were involved, what we have done and what you may need to do yourself. Section 9 of the Data Processing Agreement is that promise. For a breach of data about you as our customer, we tell the supervisory authority within 72 hours, as the GDPR asks, and you without undue delay if the risk to you is high.
If we think our own servers have been compromised, the first thing we do is switch your visitors to a verified copy of the tracking script kept elsewhere, so no browser runs anything from a server we don’t trust.
Whether something is down on our side is on status.sitegoose.com, which runs on a server apart from the ones it checks, along with any notes we post while we fix it.
Independent checks
Our own word is not enough, so three things are done by other people:
- A security test by an outside firm, attacking the dashboard, the collector and the packages. Planned before launch; the firm, the date and a summary will be listed on this page.
- A bug bounty, paying people who report a hole responsibly. Planned, after the security test. Until then a report is still welcome and still answered; see below.
- Open source, so anyone can read what runs on your site. Published; the links are above.
Reporting a vulnerability
Found something? Email info@sitegoose.com with “Security report” in the subject. Say what you found, where, and how to see it again; a request and response or a short script is ideal. A human answers within 3 working days, tells you what we make of it, and keeps you posted until it is fixed. We name you on this page afterwards if you want that.
We won’t take legal action over research done in good faith. Good faith means: you don’t read, change or delete data that isn’t yours, and stop as soon as you can show the problem; no denial-of-service tests, spam or social engineering of our staff or customers; you give us a reasonable time to fix it before publishing; and you only test accounts and sites you own (a free account is enough). A problem in one of our suppliers goes to them, not us.
The same contact is at /.well-known/security.txt, in the standard place security researchers look.