Privacy policy
What we collect from you, from your visitors, and why.
Last updated
Data about you
| Data | Why we hold it | Retention |
|---|---|---|
| Name, email, organisation | Account identity and support | Life of the account, plus 30 days |
| Password hash (bcrypt) | Authentication | Life of the account |
| Site names, domains, widget settings | Delivering the service | Life of the account |
| Invoices and payment references | Legal accounting obligation | As required by tax law |
Data about your visitors
The widget sends aggregate counters and nothing else: the site key, an event type, an adjustment id and a calendar date. No IP address is stored, no cookie is set, no identifier is created, no page URL is transmitted.
The visitor's own settings live in their browser's local storage under sa-widget-state and never leave the device. Because there is no identifier, we cannot link two events to the same person — by design, not by policy.
Legal basis
- Performance of a contract — running your account and serving the widget.
- Legitimate interests — service security, abuse prevention and aggregate product analytics.
- Legal obligation — invoicing and tax records.
Sub-processors
We keep the list short and publish changes 30 days before they take effect. Enterprise customers are notified by email and may object.
Your rights
Access, rectification, erasure, restriction, portability and objection. Write to [email protected] and we will respond within 30 days. You may also complain to your national supervisory authority.
International transfers
Production data is stored in the EU. Where a sub-processor operates outside the EEA, transfers rely on the Standard Contractual Clauses.