Security
Security and data handling
Hosting
Where your data lives
SanctScan runs on Cloudflare. The application and its database (Cloudflare D1) run in London: the database's primary copy is in Cloudflare's London data centre, and the app that reads it is placed in the same region. Static marketing pages are served from Cloudflare's edge, close to the visitor. Data is encrypted in transit (TLS on every connection, with HSTS preloading) and at rest.
Storage
What we store
- Your account: name, email address, and the profile picture of a Google, Microsoft or GitHub sign-in.
- Your organization: its members and their roles, the lists it screens, and its plan.
- Screenings: the name you searched, the filters you used, the matches and the risk score, so you can show an auditor what you checked and when.
- Monitoring: the searches you keep monitored, the alerts they raised, and who resolved each alert, with what outcome and note.
The free check on the public site stores nothing about the name you search. To enforce its daily limit, it keeps a counter per IP address for 24 hours.
Retention
How long we keep it
Account data is kept until you delete your account. Screening history is kept for as long as your subscription runs, because it is your audit record. Payment records are kept for 7 years for tax purposes. To delete your account and its data, email privacy@sanctscan.app. The full rules are in the privacy policy.
Processors
Who processes it
- Cloudflare: hosting, database, and bot protection on sign-up and sign-in.
- Polar.sh: subscriptions and payments. SanctScan never sees full card numbers.
- Resend: email delivery, including alert emails.
- PostHog (EU region): product analytics and error tracking. You can decline analytics cookies in the cookie banner.
Google, Microsoft and GitHub are involved only if you sign in with them. Nobody's data is sold.
Roles
Access inside an organization
Every organization has owners, admins and members. Every member can screen and monitor. Owners and admins manage sources, notifications, webhooks, API keys and members; only owners manage billing. These rules are checked on the server on every request, not just hidden in the interface, and nobody can change their own role.
API
API keys and webhooks
API keys belong to one organization and work only while their creator is still a member of it. Keys are stored hashed, so the full key is shown once, when you create it. Each key is limited to 60 requests a minute. Webhook requests carry an X-SanctScan-Signature header, an HMAC-SHA256 of the body keyed with your webhook's secret, so your endpoint can check that a request came from SanctScan. The details are in the API reference.
List data
Sanctions data
Every list is downloaded from the authority that publishes it, once a day. An import that is empty, less than half the size of the stored list, or made of mostly repeated names is rejected, and screening keeps using the last good version. Each list's size, last import and recent changes are shown on its free check page.
Disclosure
Reporting a security issue
If you find a vulnerability, email support@sanctscan.app with the details and how to reproduce it. Please give us a reasonable time to fix it before you disclose it.