Your data, kept separate and protected
Security isn't a feature we bolt on at the end. It's how Tickin is built, starting with giving every workspace its own database.
A dedicated database for every workspace
Most software keeps every customer's records in the same shared tables, separated only by an ID column, so a single mistake can expose the wrong data. Tickin doesn't work that way. Each workspace runs in its own isolated database, so your data is never mixed with anyone else's.
How we protect your data
Workspace isolation
Every workspace has its own dedicated database. Your records live apart from every other company's, by design, not just by a filter.
Workspace-scoped access
Sign-in is tied to your workspace. Credentials and sessions only ever resolve against your own data, so one customer can never reach another's.
Encrypted in transit
All traffic between you and Tickin travels over HTTPS/TLS, so your data is encrypted on the wire end to end.
Encrypted secrets
Sensitive integration credentials, like Slack and email keys, are stored encrypted with AES-256-GCM, never as plain text.
Hashed passwords
Passwords are never stored in a readable form. They're hashed with bcrypt, a slow, salted algorithm built specifically for credentials.
Restricted internal access
Access to customer data is limited to authorized personnel, and only for supporting and operating the service.
Found a security issue?
We take reports seriously. Reach our team and we'll respond quickly.
Contact security