Skip to content
Legal

Security

Last updated: November 14, 2026

NexaPilot holds information about your customers and the money they owe you. Here's how we protect it, and how to tell us if you find a problem.

Workspace isolation

Every customer, invoice, payment and promise belongs to a workspace. Row-level security in the database checks workspace membership on every request, so members of one workspace can never read or change another workspace's data — even through the API.

Encryption and hosting

All traffic uses HTTPS with HSTS. Data is stored with Supabase and encrypted at rest; the website is served through Cloudflare. Strict security headers, including a Content Security Policy, limit what can run on our pages.

Access and roles

  • Workspaces have owners, members and read-only viewers; only owners can manage billing, team, API keys and workspace settings.
  • Two-step verification (authenticator app codes) can be turned on for every account. Once on, the database itself refuses access until the second step is completed.
  • An activity log records who created, changed or deleted customers, invoices, payments, promises, reminders, team members and API keys.
  • Payments are handled by our payment processor — we never see or store card numbers.
  • Server-side secrets (payment, AI and email keys) live only in server functions, never in the browser.
  • API keys are shown once and stored only as a SHA-256 hash. Outgoing webhooks are signed with HMAC-SHA256 so you can verify they came from NexaPilot.
  • Customer portal links use a long random token that only shows that one customer's open invoices, and can be replaced at any time.

AI and email

AI drafts are generated only when you ask, using the facts of a single invoice. Nothing is sent to your customers without your explicit approval. Scheduled reminders are checked again just before sending and skipped if the invoice has been paid.

Your control

Workspace owners can export all data and permanently delete their workspace at any time, and every user can delete their own account from Settings → Data & privacy.

Reporting a vulnerability

If you believe you've found a security issue, please email [email protected] with the details and steps to reproduce. Please don't access other people's data or disrupt the service while testing. We'll acknowledge your report and keep you updated while we fix it. Our machine-readable contact is at security.txt.