Privacy policy
Last updated September 20, 2026. This policy is a development-preview draft and must be reviewed by the service operator before a public launch.
Information we use
SailBooks stores your account email, securely hashed password, business profile, customer details, invoices, payment status, bookkeeping accounts, imported transaction fields, categories, ledger entries, and reconciliation history. Stripe authorization credentials are encrypted on the server. Customer card and bank details are collected directly by Stripe and are not stored by SailBooks.
How information is used
We use this information to authenticate your account, maintain your books and reports, display invoices, process payments in your Stripe account, and reconcile payment status. Invoice details are accessible to anyone who has the invoice’s unguessable public link. Draft invoices remain private.
Imported financial records
CSV files are sent to the server for validation. SailBooks retains mapped transaction fields, import decisions, and correction history. Confirmed imports automatically contribute format candidates containing mapping configuration and a header fingerprint, not sample transactions or raw header text. Bookkeeping records are private to your workspace.
Account emails
When account emails are configured, SailBooks uses Resend to deliver verification and password recovery messages. This shares your account email and a temporary account link with the email provider. SailBooks stores only a hash of each temporary token.
Cookies and retention
We use PostHog to measure visits, pageviews, referral domains, and browser and device types. An anonymous identifier in local storage helps recognize returning browsers. Analytics does not include form contents, account emails, financial records, or session recordings. We remove query strings and replace private invoice and workspace paths before sending page URLs to PostHog.
We use an essential session cookie to keep you signed in. This preview does not use advertising cookies. The operator must define retention, deletion, and privacy contact procedures before launching the service.
Create account →