HomeSecurity
SECURITY

Invoice follow-up contains sensitive business context. We treat it that way.

Access is authenticated, records are isolated by workspace, invoice files stay private, and managed sending requires explicit approval.

The controls in the product today.

Specific safeguards, without certification claims or vague security badges.
01IN PLACE

Account access

Clerk handles sign-in and session management. The product workspace requires an authenticated account.
02IN PLACE

Workspace isolation

Business records carry a workspace ID. Supabase row-level security checks workspace membership before account data can be read or changed.
03IN PLACE

Private invoice files

Invoice PDFs are stored in a private bucket. Viewing or downloading a source file requires an authenticated, workspace-scoped request and is served without public caching.
04IN PLACE

Approved sending

Managed follow-up starts only after the account holder approves the payer, business identity, first message, cadence, attempt limit, document option, and send time.
AUDIT HISTORY

Important actions stay attached to the invoice.

Reminder drafts and timeline events form an audit history. The authenticated app can add those records and read them, but cannot rewrite or delete them through ordinary workspace access.
DATA HANDLING

We use focused infrastructure providers.

Clerk provides authentication, Supabase provides database and private file storage, Vercel hosts the application, and Resend supports email delivery. Our Privacy Policy explains the full set of processing providers and retention practices.Read the Privacy Policy

Found a security issue?

Send the affected URL and a clear description. Please do not include live invoice files or unnecessary personal data.Report a security issue