Authenticated ownership
Supplied RLS policies restrict account records to the authenticated owner.
Security by evidence
Private by design. Precise about every claim.
ALLLAST describes only controls that are present in this release. We do not use labels such as “bank-grade,” “military-grade,” “zero-knowledge,” or “end-to-end encrypted” without independent evidence.
Implemented in V7
Controls present in this V7 release
These statements are based on the packaged frontend and the inspected Supabase schema and Edge Functions. Credentialed end-to-end production tests remain a separate release gate.
Private file paths
Uploads use a random path under the user ID and are opened through short-lived signed URLs.
Transactional message save
One database function creates the message, recipient link, delivery rule, audit entry and attachment scan record.
Attachment release gate
A delivery job is not created while an attached file has not been marked clean.
Protected recipient access
Recipient access tokens are handled server-side; keyholder access uses 12-character keys and server-side attempt limiting.
Server-side billing
Checkout creation and signed Stripe webhook processing run in Edge Functions rather than public browser code.
Operational release gate
Source code is not the same as a verified live service
Before public launch, the live environment must pass these checks. This page deliberately separates implemented code from confirmed operations.
Required live verification
- pendingRun a controlled two-account test to verify cross-account RLS isolation.
- pendingConfirm every deployed Edge Function with authenticated success-path tests and review logs.
- pendingComplete controlled Stripe, Resend and scheduler success-path tests and configure operational alerts.
- pendingReplace structural file validation with a dedicated malware-scanning service before accepting untrusted public uploads at scale.
Claims not made
- blockNo government death-registry integration is claimed.
- blockNo regulatory certification or compliance certification is claimed.
- blockNo guaranteed delivery or perpetual service availability is claimed.
- blockPublic announcements and executor workflows are not presented as active features.