Controlled pilot
Pilot sign in
Imported estates are stored per signed-in user and per client tenant. Access is enforced in the database, so a session can only read the datasets it committed for the tenant it is working in.
Account
Email and password
What this gate does and does not do
Read before using any real client file
- In place: authenticated sessions, per-user and per-tenant row-level access rules in the database, server-side validation of the session on every read and write, and a delete control that removes only the current tenant dataset.
- Not in place: organisation-level user management, roles, sharing between colleagues, an import audit trail, customer-managed encryption keys, data-residency guarantees, or a formal security review. Treat this as a controlled pilot with test or de-identified data only.