Privacy notice
Plain-language description of how BankLint processes data during its controlled beta. Last updated 2026-10-18.
Draft: this notice has not yet been reviewed by a lawyer. Sections marked “legal review” are expected to change.
What BankLint processes
- Account data: your Google account email address, name and Google account identifier, received when you sign in with Google.
- Workspace data: workspace, company and flow names and settings you enter, memberships, roles and invitations (invitee email address).
- Validation evidence: for signed-in validations, sanitized findings, semantic facts used for regression comparison, provenance and a SHA-256 of the file. Uploaded payment files themselves are not stored. Anonymous validations on the home page store nothing.
- Audit trail: security-relevant actions (sign-ins, permission denials, configuration and billing changes) with the acting user and time.
- Ask BankLint (AI), when enabled: your question (with account-like identifiers removed) and the verified answer, visible only to you.
- Operational data: server logs with a request reference, route, status and timing (no file contents, no IP addresses), kept up to 30 days; rate-limit counters keyed by a daily-changing hash of an IP prefix, which expire after at most one hour and are then deleted.
Service providers and locations
| Provider | Purpose | Location |
|---|---|---|
| Supabase | Database and authentication | AWS us-east-1, United States |
| DigitalOcean | Application and validation service hosting | Amsterdam, Netherlands (EU) |
| Sign-in with Google; Google Analytics (see below) | Google’s global infrastructure | |
| Anthropic | AI explanations, only for workspaces where Ask BankLint is enabled and only when you ask | May be processed in several regions (including the US and Europe); stored in the United States |
| Stripe | Subscription billing, if your workspace upgrades | Stripe’s infrastructure (including the United States) |
| Resend | Service email (invitations and invitation notices) | Resend’s infrastructure (including the United States) |
BankLint does not claim EU-only processing. International transfer safeguards: legal review.
AI disclosure
- AI is never used to decide validation results; deterministic rules do. Ask BankLint is off unless enabled for your workspace, and is never available to anonymous visitors.
- When you ask, Anthropic receives sanitized evidence selected by BankLint and your sanitized question. It never receives your payment file.
- Under Anthropic’s default API terms, inputs and outputs are retained for up to 30 days (longer only where Anthropic’s policies or law require) and are not used to train models by default. BankLint has no zero-data-retention agreement with Anthropic.
Billing
Payments are handled by Stripe on Stripe-hosted pages. BankLint never receives or stores card details. BankLint stores the plan, status, renewal dates and Stripe customer and subscription identifiers for your workspace, and passes Stripe your workspace identifier and billing email.
BankLint sends service email only (for example invitations). Emails never contain payment-file contents or validation findings. No newsletters or marketing email.
Analytics and cookies
- Strictly necessary cookies: the encrypted BankLint session cookie and a short-lived sign-in cookie.
- Google Analytics 4 is loaded on banklint.com with Consent Mode. Analytics storage is denied by default; analytics cookies are set only if you accept in the cookie banner. Before that, Google may receive cookieless measurement pings. Change your choice at any time with “Cookie settings” at the bottom of each page. Analytics never receives file contents or validation results.
Retention
- Workspace data, validation evidence and the audit trail are kept while the workspace exists. A payment problem never deletes data: evidence stays readable.
- Invitee email addresses are intended to be removed 30 days after an invitation closes; this clean-up is not yet automated.
- Retention periods and deletion on request: legal review.
Your rights and contact
To access, export or delete your data, or for any privacy question, contact [email protected]. Controller identity, legal basis and supervisory authority details: legal review.
See also Security.