Tenant isolation first
Customer records are scoped by active business membership and protected by database Row Level Security plus authorized server operations. Clarity also maintains synthetic two-tenant regression rehearsals for isolation.
Trust & security
Automation should reduce bookkeeping work without widening the security boundary.
Clarity is designed around tenant isolation, private evidence storage, constrained automation, recoverability, and a clear human judgment boundary. Security controls are part of the product architecture—not an afterthought added at launch.
Private evidence stays private
Bookkeeping files live in a private Storage bucket. File access is checked before a short-lived signed download is issued, private pages are marked no-store/no-cache, and raw Storage paths are kept out of customer page data.
AI receives less, not more
The Stage 2–3 transaction worker is designed to minimize and sanitize provider payloads, keep internal identifiers and prior-attempt blobs inside Clarity, require an exact HTTPS provider host, and reject Stage 4 model calls.
Recovery is independently checked
Cloud backup checkpoints are followed by a separate recovery artifact audit that verifies database dumps and private-file checksums. Recovery evidence stays separate from normal application data.
The browser has boundaries too
Clarity uses HSTS, frame denial, no-referrer handling, restrictive permissions, a Content Security Policy, exact Clarity-Supabase browser egress, and explicit private-cache controls for authenticated areas.
Stage 4 stays human
Automation is capped before human judgment. Ambiguous, unsupported, or material exceptions remain visible for review rather than being silently guessed through.
Authenticator MFA protects owner operations and enrolled customer accounts
Owner operations require a verified time-based authenticator factor and current AAL2, including the reviewed database owner-RPC boundary. Customer accounts can enroll TOTP per account; once enrolled, Clarity requires AAL2 before protected workspaces or private invitation acceptance. Customer enrollment is not represented as universally enabled.
Operational verification
Controls are checked repeatedly, not just documented once.
Clarity uses cloud-run guardrails and read-only production checks to catch drift while keeping customer content out of routine security logs.
Code guardrailsType checking, production builds, offline HTTP checks, security regressions, and privacy boundaries run before reviewed changes merge.
Production metadata auditsRead-only checks monitor tenant/security grants, private Storage controls, invitation boundaries, and document limits without reading customer rows.
Public availability smokeCloud-run GET-only checks verify important public routes and security headers without signing in, submitting forms, or touching customer data.
Customer experience watchdogSource is configured for four-times-daily cloud GET-only checks of public health and customer routes with bounded retries; monitoring has no production-write authority.
Cloud-only operationProduction, CI, backups, and recovery checks run in managed cloud systems. The owner's laptop is not part of the service availability chain.
AI-first with a hard edge
Routine work can automate. Authority does not.
Clarity's automation model is designed so Stage 1 handles deterministic work, Stages 2–3 can use constrained AI after explicit release, and Stage 4 remains human. AI does not independently control tenant membership, security privileges, billing, paid budgets, customer invitations, secrets, money movement, or commercial legal terms.
1Deterministic automationStrict rules · $0 model cost
2Constrained classificationMinimum-data AI when approved
3Constrained reasoningConfidence + bookkeeping guardrails
4Human judgmentAI stops here
Clarity will not claim a certification or security guarantee it has not earned.
No software can honestly promise that a breach is impossible. Clarity's approach is to reduce exposure, keep privileges narrow, monitor important boundaries, preserve recovery evidence, and disclose current product limits. External security certifications will only be represented if they are independently obtained and current.
Keep sensitive data in the right place
Never send passwords, recovery codes, or full account numbers through support.
Use the authenticated Documents area for bookkeeping files and the Support page for product or account questions.