What we do, and what we will not claim
Leads are personal data belonging to people who never heard of us. This page says where that data sits, who can reach it, how long it stays and how its deletion is proven. It also names the one claim our predecessor made that is not true here.
Where the data is
- Hosted in the EU
- Application and database run in EU regions. Nothing is replicated outside.
- One database, scoped by account
- Every query is bound to an account; the scoping is tested, not assumed.
- Backups
- Managed by the database provider, inside the same region.
Who can reach it
- Roles you define
- Rights are per object, not three fixed levels. The navigation only shows what the rights allow.
- Access follows responsibility
- A record is visible to its owner, its watchers and the roles that may see all.
- Argon2id for passwords
- With rules on length and reuse, and a lockout after repeated failures.
- Sessions that expire
- Rolling renewal, revocable, and immediately void when a user is deactivated.
What is encrypted, and what is not
- Secrets are encrypted
- SMTP passwords, API credentials and tokens with AES-256-GCM at rest.
- Sensitive fields are masked
- A field marked sensitive is hidden in lists, exports and the UI. Masked, not encrypted.
- In transit
- TLS everywhere, including outgoing webhooks and mail.
- We do not claim per-field encryption
- The previous version of this site did. It was true of the old product, not this one.
How long it is kept
- Every dataset has a rule
- A table with no retention rule fails the build. Coverage is not a policy document, it is a test.
- Deletion you can preview
- The run shows what it would remove before it removes it.
- Legal hold
- A record under hold survives the run and says why.
- Proof of deletion
- What was deleted, when and under which rule. Retained after the data is gone.
What you can take with you
- Export in both common formats
- CSV and XLSX, as a right in the role matrix, and every export is logged.
- The intake API is symmetrical
- What comes in through the API can go back out through it.
- No lock on your documents
- Generated documents are files, readable without our software.
What is not on this page
No SOC 2 report, no ISO 27001 certificate, no penetration test letter, and no customer references. We do not have them yet, and a security page that implies otherwise is the one thing worse than a short security page. If your procurement needs any of these, ask and we will tell you where we stand rather than where we would like to stand.
The same four things, in detail
Written against the product and shown inside it too, so what you read here is what somebody in the account reads while they set it up.
See it on your own data
Create an account and look at the change log, the retention rules and the deletion preview yourself. That is the part a brochure cannot show.