What we do, and what we don't.
Whatever is on this page is what the system does today — no more. When something changes, the date above changes with it.
Encryption
Passwords and authenticator secrets are encrypted with AES-256-GCM. Each record keeps its own initialization vector and authentication tag, and the application does not start without a valid key.
Documents are stored on our server in Brazil, with access controlled by the application. File-level encryption of documents is being rolled out; until it is finished, we do not claim documents are encrypted at rest.
Who can read what
Technically, Kayso can decrypt your passwords. The encryption key lives on our server, and that is what makes it possible to reveal a proposed password during an approval and to recover access. We would rather say it than let you find out later.
Access to the production server and database: only Conceitto's technical team, with individual key-based access logged on the server.
When our platform team opens an organization, the access is recorded in the platform's audit log. We are bringing that record into the trail your own team sees.
Signing in
Password plus a second step — a code by e-mail or an authenticator app — according to the policy your organization sets.
Isolation between customers
Every query is filtered by the organization of the signed-in user. Isolation enforced by the database itself is being rolled out, so that a query without that filter returns nothing instead of another customer's data.
Audit trail
Who asked, who decided, when, from which address and with what justification. The application offers no way to edit or delete an audit record — not for administrators, not for us. The trail can be exported as CSV at any time.
We are adding a hash chain so that any change made directly in the database can be detected and pointed to.
Where the data lives
On a server in Brazilian territory, under the LGPD. The data processor is identified and the data protection annex is signed together with the proposal.
Backup
Before every update, the database and the document files are backed up — if the backup fails, the update does not happen. The server also has the hosting provider's own backup.
We have not yet published a timed restore test. When we do, how long it took will appear here.
What we don't have yet
Report a vulnerability
Write to hello@kayso.io with the subject "Security". We reply to every report.