Privacy & security

Bank statements are among the most sensitive documents you have. This page explains exactly what DocuBridge does with yours — including the limits.

Current status

Real statement processing is enabled

Every protection described on this page is active. An independent security assessment has not been completed yet; we'll publish it here when it is.

In your browser
We check the file type, size, page count and password protection on your device. Files that can't be processed are never uploaded.
Your consent
Extraction runs on our servers, so we ask before uploading. Nothing is uploaded silently.
In transit
The file is sent over HTTPS (TLS). This is transport encryption, not end-to-end encryption — our server must read the statement to extract transactions.
On our server
The PDF is read in memory by an isolated worker process with strict time and memory limits. It is never written to disk and is discarded as soon as extraction finishes.
Stored results
Extracted transactions are encrypted with AES-256-GCM, using a key derived from a secret that only your browser holds plus a server key. They're deleted 24 hours after upload or immediately when you click Delete.
Payments
Checkout is handled by Stripe. We never receive your card number. Credits are added only after Stripe confirms the payment to our server.

Your PDF fileNo: Read in memory during processing, then discarded. Never written to disk or storage.
File nameNo: Only the file's contents are uploaded; the name never leaves your browser.
Extracted transactions and your editsYes — encrypted: Deleted 24 hours after upload, or immediately when you click Delete.
Account numberLast 4 digits only: Kept with the extracted transactions and deleted with them.
Browser sessionA keyed hash only: The session secret lives in an HttpOnly cookie in your browser. We store only a one-way hash.
Credits and ordersYes: Order reference, amount, status and credit balance — no card details. Retention period pending legal review (tax/accounting records).
Server logsYes — no document content: Event names, timings and error codes only. Logs are built from an allow-list, so transaction data can't be logged by accident.

Data	Stored?	Details
Your PDF file	No	Read in memory during processing, then discarded. Never written to disk or storage.
File name	No	Only the file's contents are uploaded; the name never leaves your browser.
Extracted transactions and your edits	Yes — encrypted	Deleted 24 hours after upload, or immediately when you click Delete.
Account number	Last 4 digits only	Kept with the extracted transactions and deleted with them.
Browser session	A keyed hash only	The session secret lives in an HttpOnly cookie in your browser. We store only a one-way hash.
Credits and orders	Yes	Order reference, amount, status and credit balance — no card details. Retention period pending legal review (tax/accounting records).
Server logs	Yes — no document content	Event names, timings and error codes only. Logs are built from an allow-list, so transaction data can't be logged by accident.

Use your statements to train AI models.
Sell or share your data for advertising.
Run advertising, session-replay or third-party analytics scripts on pages where you upload or review statements. These pages load no third-party scripts at all.
Send your statement to an AI or OCR provider. Scanned-statement support, if added, will be opt-in and listed below before it's enabled.

Not end-to-end encrypted. Our server reads the statement in order to extract it.
Deletion and backups. Delete removes data from our live database. Infrastructure backups, once enabled in production, may hold encrypted copies until they expire; those copies can't be decrypted without the session secret held in your browser. We'll publish backup retention before launch.
No certifications yet. DocuBridge is not SOC 2 or ISO 27001 certified. We'll say so here if that changes.

Google Cloud — statement processing and encrypted storage, United States region.
Vercel — website hosting. Statement uploads pass through it to Google Cloud and are not stored there.
Amplitude — product analytics via our own relay; never receives document content, file names, amounts or IP addresses.
Stripe — payment processing, once paid plans start. Never receives statement data.

See also the privacy policy. To report a security issue, email robin421@gmail.com.