Workspace isolation
Business data is scoped to organisations and access is governed by authenticated membership and database row-level security policies.
TRUST & DATA PRACTICES
How Agri Business OS handles your workspace
A plain-language overview of the safeguards built into the product today. This page describes product behaviour; it is not a substitute for contractual privacy terms.
Authentication
Accounts use Supabase authentication. Protected workspaces require a valid signed-in user, with password recovery and self-service password changes available.
Access control
Team access is managed through organisation membership and role-aware product controls. Sensitive subscription state is service-controlled rather than directly editable by workspace users.
Operational resilience
The application includes dependency health checks, uncached health responses, production error recovery surfaces and deployment type checking.
What you should do
Use a unique password, keep account access personal, remove team members who no longer need access and review workspace permissions regularly.
Before commercial launch
Formal privacy, terms, retention and support commitments should be published once the contracting entity, service contacts and final operating policies are confirmed.