Separate by design
Every household and business is isolated at the database level with Row Level Security. The application does not rely on hiding another workspace's information in the interface.
Security & privacy
Your data stays with the people it belongs to.
Neatora separates every household and business, verifies access on every request and gives owners control over who can join.
Our approach
Security should be part of the structure, not a promise added later.
Access checked on every request
Neatora verifies your current membership and role before returning workspace data. Choosing a workspace changes where you are—it does not grant access.
Permissions that match responsibility
Owners, managers, cleaners and household members receive different capabilities. Sensitive actions remain protected on the server and in the database.
Controlled invitations
Invitations belong to one workspace and one role. They expire, can only be accepted once and cannot be reused to join somewhere else.
Infrastructure
Postgres and Supabase
Neatora stores application data in Postgres. Supabase Auth handles authentication, while database policies enforce which records an authenticated user can access.
Compliance
Clear about our current stage
Neatora does not currently hold SOC 2 or ISO 27001 certification, and we have not published an independent penetration test. We will update this page as our assurance programme develops.
Questions or concerns
Tell us if something does not look right.
For privacy questions or to report a security concern, use our contact page. Please do not include passwords, access tokens or sensitive customer data in your first message.
Contact Neatora →