Security & trust
What we do to protect your invoice data.
Invogi handles supplier bank details and invoice data for mid-market finance teams. Here's how we approach invoice data security, and who we share data with.
Controls
Six controls, applied to every account
Encryption
TLS 1.2+ in transit everywhere; encryption at rest via our managed infrastructure providers.
Tenant isolation
Every record is scoped to your organization; authorization is enforced centrally, not per-query.
API key hashing
Keys are hashed at rest and shown once at creation. We never log the raw key.
Audit trail
Role changes, key lifecycle, uploads, policy changes, and exception reviews are logged and append-only.
Role-based access
Four roles — Owner, Admin, Analyst, Viewer — with bank account visibility restricted by role.
File safety
Stored-byte MIME validation, size/page limits, defensive XML/PDF parsing, and SHA-256 fingerprinting on every upload.
Sub-processors
Who else touches your data
Our authoritative register names Cloudflare, Supabase, Google Cloud, Clerk, and Resend; describes the data and purpose for each; identifies conditional document processing; and links to current provider transfer and downstream-subprocessor information. Paddle is disclosed separately as merchant of record because it handles buyer and payment data under its own privacy terms, not invoice content.
View the current Subprocessor List →
Read the full Data Processing Agreement →
Invogi does not currently hold SOC 2 or ISO 27001 certification, and we won't claim one until it's true. If you need a signed DPA or supporting material for a security review, contact us.