How we look after your data

A list of what is actually in place, written plainly. If you have a question this page does not answer, write to us.

Passwords are at least 10 characters and stored only as bcrypt hashes; we cannot read them.
Two-step login with any authenticator app, plus one-time backup codes. Owners can require it for all staff.
After repeated wrong passwords a login is locked for a while, and the attempt is logged.
Each person has their own login and role, so nobody needs to share a password. A person who already has an Innlark login is invited and must accept.

Sessions

Session cookies are signed, unreadable to scripts and sent only over https.
Every user can see their signed-in devices and sign any of them out.
Changing a password signs out every other device.

Data and secrets

Payment keys, webhook secrets and other credentials are encrypted at rest with AES-256-GCM.
API keys are shown once and stored hashed. Webhooks are signed with HMAC-SHA256.
Pages are served with strict security headers: a content security policy, no framing, no sniffing.
Card details never touch our servers: guests pay on Stripe’s own pages.

Backups

The database is copied every night, compressed and encrypted, and older copies are kept for two weeks.
Backups can be sent to separate storage, and restoring one is a single command.

Privacy tools

Export everything a guest’s record holds, or erase their personal data while keeping the accounting record.
Set how long guest data is kept; older records are cleaned up automatically.
A printable record of processing, and a privacy policy and terms in ten languages.
An activity log of who changed what, for owners and managers.

Where your data is kept

If you use innlark.com, your data is kept on Innlark’s server. If you prefer, you can run Innlark on a server of your own, in the country you choose, with the same features; then the data never leaves it.

Found a problem?