Trust
Your business’s data, handled with care.
Where snuepi runs, who processes your data, how your account is protected, and how an agency checks the signed results of its call checks.
Where it runs
Hosted in the EU.
The application and its database run on Fly.io servers in Stockholm, Sweden. The full list of who processes data for us, and where, is on the sub-processors page.
Language models
- The model that reads price lists, requests and conversations runs at Scaleway (in the EU). At setup it also reads the business’s own website to suggest its services, prices and hours, only when it is EU-hosted, and with emails, phone numbers and IBANs removed first.
- Call checks use a model that must be hosted in the EU: the model above when it is EU-hosted, or a separate EU-hosted model. Phone numbers, emails, card and account numbers, and names and street addresses where they can be recognised, are masked before the model sees the call.
- An anonymised copy of your setup data is used to improve our model only if you said yes to it.
Security
Protected logins, protected keys.
Your account
- Passwords are salted and hashed with scrypt. Nobody at snuepi can read them.
- Two-factor login with an authenticator app, for any account. It is required for agency owners and for snuepi’s own administrators.
- You get an email when two-factor is turned on or off.
- The one-tap links in an owner’s emails (approve a booking, end a pause) act without two-factor: each answers one question, works once, for that owner only, and expires within a week.
Keys and connections
- API keys are stored only as hashes.
- The keys and tokens for the calendars and booking systems you connect are encrypted in the database (AES-256-GCM).
- The approve and decline links in our emails to owners expire and work once; the newest are also signed.
In transit and in the browser
- All traffic uses HTTPS, with HSTS.
- A strict Content Security Policy: our pages run no inline scripts.
One business, one space
- Every query is scoped to the business it belongs to, and automated tests check that one business cannot read another’s data.
- Agencies only see a client business after that business has said yes.
How to tell a real email or call from snuepi, and what we will never ask you for: Is it really snuepi?
Data handling
Only what the job needs. Yours to take or delete.
What we read
- From your calendar: only when you are busy. Never titles, descriptions, attendees or places.
- We do not sell data, and we do not share it for marketing.
Your control
- Download everything your business has in snuepi, in one file, from Settings.
- Delete your business and its data yourself. Deletion is immediate; backups are overwritten within a few days.
What we process, why, and for how long: the privacy policy.
Signed results
Signed results the agency can check. Including against us.
Each call-check result is signed with snuepi’s key and chained to the result before it, so changing or removing one later breaks the chain. Tested on simulated calls only; production keys are being set up.
Checked from the agency’s own ledger
A logged-in agency exports its ledger and checks every signature and the chain with kept verify-ledger. Call-check results are not published in a public log yet.
Checkable without us
The export carries the public keys it was signed with, so the check runs on the agency’s own machine, with nothing else from snuepi.
Found a problem?
Report a vulnerability.
If you think you have found a security problem in snuepi, email us. Tell us what you found and how to see it; please do not access other people’s data or disrupt the service while testing. We answer every report. Machine-readable: /.well-known/security.txt.