Privacy Policy
Last updated: November 2026
1. Zero Server Uploads for Financial Statements
VaultSheet is engineered so your PDF, CSV, and pasted OCR bank statements never leave your computer. Parsing (`pdfjs-dist` Web Worker), coordinate alignment, running balance reconciliation, and file generation (`.xlsx`, `.csv`, `.qbo`, `.ofx`, `.json`) run exclusively inside your local browser memory (RAM).
We do not store, log, inspect, transmit, or train any model on your bank files, balances, merchant names, or account numbers. You can verify this in Chrome DevTools → Network tab while converting any statement.
2. Browser Storage & License Activation
If you activate a VaultSheet 7-Day Pass or Pro Bookkeeper license key, your browser stores only the activated license key string inside `window.localStorage` (`vaultsheet_pro_license_v1`) so you remain unlocked across page reloads. Verification checksums are evaluated locally without server tracking beacons.
3. Payments & Merchant of Record (GDPR / CCPA)
Paid checkouts, VAT/sales-tax collection, invoicing, and payment card handling are processed by our external Merchant of Record (Polar.sh, Lemon Squeezy, or Paddle). VaultSheet does not directly handle or store credit card numbers on its servers.
4. Chrome Extension Permissions
The VaultSheet Manifest V3 Chrome Extension requests only the `downloads` permission strictly to save your locally exported `.csv` and `.qbo` files to your computer. It declares zero `host_permissions` and does not read browsing history or page DOM data.
5. Contact
Questions regarding privacy, enterprise CPA compliance, or billing receipts may be directed to support@vaultsheet.tech.