Skip to main content
Privacy isn’t a setting in myClerkBook — it’s the architecture. The whole product is built so that exposing your financial data to third parties is structurally impossible, not merely discouraged.

​
No bank access. Ever.

myClerkBook does not request, store, or process bank credentials. It does not integrate with Plaid, Finicity, MX, or any data aggregator. All financial data is entered by you or extracted from documents you upload. There’s no bank connection to revoke, because one never existed. This is a permanent architectural constraint, not a roadmap choice. Any feature that would require bank access is out of scope by definition.

​
Three layers of enforcement

Privacy is enforced by three independent mechanisms at once:
1

Edge layer

Authentication is validated and rate limiting is applied before a request ever reaches code that touches your data. Unauthenticated requests are rejected at the edge.
2

Application layer

sanitizeForAI() strips all personally identifiable information from document content before any AI prompt is built. Claude receives the financial content of a document — never your name, email, or account numbers.
3

Database layer

Row Level Security is enabled on every table and enforced by PostgreSQL itself. No application bug, agent action, or internal query can return another user’s data — the database guarantees isolation, not application code.

​
Hard delete

When you delete your account, all your data is removed immediately and completely — no soft delete, no archive, no retained backups beyond the database’s short recovery window, and no use of your data for model training. Export everything or delete everything at any time under Account → Data.

​
Data processors

myClerkBook uses a small set of vetted service providers, each under a data processing agreement: Supabase (database), Clerk (identity), Anthropic (document parsing — sanitised, no PII, no training use), Resend (notification email), Twilio (SMS/WhatsApp), Polar (billing), Loops (lifecycle email), and PostHog (anonymised product analytics).
For privacy requests or questions under POPIA or GDPR, contact legal@myclerkbook.com. Full details are in the Privacy Policy.