engineering8 min read
Privacy by architecture
Your e-Financials API key is the master password to your books. Here's how we handle it.
HHenri · Founder
Your e-Financials API key is the master password to your books. Here's how we handle it: encryption, isolation, audit, and zero persistence in logs.
The threat model
If our backend were compromised, what could an attacker do? With read-only DB access, the answer is: see company names, bank line metadata, receipt blobs. With full DB access plus the encryption keys, the answer is more nuanced — hence the encryption-at-rest model.
What we do, in five bullets
- • AES-256-GCM encryption-at-rest with per-tenant data keys
- • KMS access scoped per-customer; we sign with your key only in memory
- • API key is never logged or echoed, ever
- • Open-source the encryption layer (so anyone can audit)
- • Quarterly third-party security audit, published