Built to protect your money data

Isolation enforced by the database

Every Talisk account's data (mail, contacts, books, documents) lives in its own isolated database schema. Your data and another customer's are never in the same tables.

On top of that physical separation, PostgreSQL Row-Level Security is enforced by the database engine itself, so isolation doesn't depend on the application code being perfect. Even a hypothetical app-layer bug hits a database that refuses to return another account's rows.

Encrypted, in transit and at rest

• ✓ In transit: every connection to Talisk uses TLS (HTTPS).
• ✓ At rest: personal content (email bodies, contact details, financial documents) is encrypted with a per-account key (Fernet, AES-based). Uploaded files like receipts and attachments are encrypted at rest too.
• ✓ Credentials: passwords are stored only as salted hashes; OAuth tokens for connected services are encrypted at rest.

Backups you could actually recover from

Nightly database backups are GPG public-key encrypted before they leave the server and stored off-site. The decryption key isn't stored alongside them. A copy of the backup bucket on its own reveals nothing.

A restore is verified every day against the encrypted backup, so "we have backups" is something we prove, not just claim.

Guardrails against catastrophic mistakes

The database carries engine-level triggers that block bulk deletion of customer data outside a deliberate, audited procedure. Defence-in-depth so a single bad command can't wipe your records.

Your data is yours, never shared

We don't sell or share your data, and we never train public AI models on it. The AI that drafts your replies and reads your bills works on your behalf, on your data, for you.

You can export your books and documents whenever you want, and ask us to delete your account and its data.