Subprocessors

RealBooks uses the third-party services below to operate the product. Each one processes some category of customer data on our behalf. We list every vendor here so customers can audit our supply chain before signing up and at any time while using the product.

Last updated: June 9, 2026

Vendor	What they do for us	Data categories	Region	Security docs
Plaid	Bank account linking + transaction data sync	Account credentials (via Plaid, never stored by RealBooks) Bank account + routing numbers Transaction history Bank balances	United States	Link
Stripe	Subscription billing for RealBooks itself (planned for GA; not in beta scope)	Customer name + email Payment method (handled by Stripe; RealBooks never touches PAN)	United States	Link
Railway	Application hosting + Postgres database hosting	All RealBooks application data (sensitive fields such as bank tokens, tax IDs, and MFA secrets are additionally encrypted at rest by RealBooks via AES-256-GCM)	United States (us-east region)	Link
Resend	Transactional email delivery (verification, invites, password reset, invoice send)	Email addresses + email content	United States	Link
Anthropic	AI-assisted bill extraction + tax categorization (Claude API)	Uploaded bill text + OCR content Vendor / category names referenced in AI prompts	United States	Link
AWS S3	File storage (attachments, invoice PDFs, exports)	Uploaded files (bill PDFs, receipts, attachments) Generated PDFs	United States	Link
Sentry	Error tracking + observability	Server-side error stacks (PII redacted via beforeSend filters) Request IDs + correlation metadata (no PII)	United States	Link
OnCatch (in-app feedback widget)	Feedback collection on-page (the small widget at bottom-right of the app)	Voluntary user feedback content Page URL the feedback was left on	United States	Link

Notes

RealBooks does not store your bank login credentials. Bank connections are made through Plaid; your password is entered into Plaid's UI and never reaches our servers.
Customer payment method data is never stored by RealBooks.Subscription billing (when it goes live for GA) runs through Stripe-hosted checkout; we do not see or store credit-card numbers.
Sensitive fields are encrypted at rest using a separate field-encryption envelope (AES-256-GCM) before being written to the database. See the engineering shipping report for details.
We do not currently use any sub-processors outside the United States.If that changes, this page will be updated and existing customers will be notified.

Questions?

Email hello@realbooks.online with any question about this list or our data handling.