Privacy policy

Account data is what we collect to run the service: your email address, a hash of your password, session records with IP address and browser identifier, and audit entries recording actions taken in your workspace.

Customer data is what you upload: ledgers, statements, documents, and anything derived from them. We are a processor for this data. You determine what it contains and why.

Email address — to identify your account and send verification, reset, and notification messages. Password hash — to authenticate you; the password itself is never stored. IP address and browser identifier — to show you your active sessions, to rate-limit sign-in attempts, and to record security events. Usage records — to meter plan limits and AI spend.

We do not use tracking or advertising cookies, and we do not sell personal data.

When you ask the assistant a question, the question and the specific excerpts retrieved to answer it are sent to our AI provider. Only the excerpts relevant to that question are sent — not your database, and never another customer's data.

Your financial data is not used to train models.

Application data is stored in the deployment region for your account. Backups are encrypted before leaving the host and stored with a separate provider. Sub-processors are limited to hosting, the AI provider, email delivery, and payment processing; the current list is available on request.

Customer data is retained while your account is active and for a defined window after termination so you can export it. Audit logs are retained for the configured period, which may exceed the customer-data window because they are the record of who did what.

Backups age out on their own schedule. A deletion request is applied to live data immediately and recorded, so that if a backup is ever restored the deletion is re-applied rather than the data reappearing.

Where GDPR or comparable law applies, you may request access, correction, erasure, restriction, portability, or object to processing. Export is available directly in the product; other requests go through the contact page and are answered within one month.

Where we act as a processor for customer data, requests from your end users should be directed to you as controller, and we will assist.

Tenant data is isolated by database-enforced row-level security. Passwords are hashed with Argon2id. Session and reset tokens are stored only as hashes. Sensitive fields, including integration credentials, are encrypted at rest. Details are on the security page, which also states plainly what we do not claim.

If a breach affects your personal data, we will notify you without undue delay with what we know, what we are doing, and what you should do.

Material changes will be notified before they take effect. Questions or requests: contact us.