Access is enforced in the database
Every table carries row-level rules. If your account has no right to a row, the database refuses to return it — the interface never gets the chance to decide. This is the difference between a screen that hides data and a system that does not hand it over.
Every relation has a declared owner
An authorisation manifest records, as data, which roles may touch each table, view, function, storage bucket and scheduled job. Anything not explicitly granted is denied. Because the manifest is data, drift between what we intended and what is actually configured becomes detectable rather than theoretical.
Logs are stripped before they are stored
Log output passes through a redaction layer that removes authorisation headers, tokens, prompts, document contents, email addresses, phone numbers and payment identifiers. Diagnostics should never become a second copy of your case.
Sessions can be revoked, and revoking means something
Signing a device out invalidates its scope rather than merely clearing a local token. You can see active sessions and end them from your account.
Your data can leave
You can request a copy or the deletion of your data from inside your account. Data you cannot export is not really yours.
Firms are verified before they can take a client
A law firm passes a verification step before its profile can accept a mandate. Being on Lawendo is meant to carry information.