Talisk holds two of the most sensitive things a business has: its email and its financial records. The architecture was built around that fact from day one. This page describes the measures actually in place — no more, no less.
01Account 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 data are never in the same tables. On top of that physical separation, PostgreSQL Row-Level Security policies are enforced by the database engine itself, so isolation does not depend on application code being bug-free: even a hypothetical application-layer flaw hits a database that refuses to return another account's rows.
The database also carries defence-in-depth guards against destructive operations (engine-level triggers that block bulk deletion of user data outside a deliberate, audited procedure).
02Encryption
- In transit: all connections to the Service use TLS (HTTPS).
- At rest: personal content — email bodies, contact details, financial documents — is encrypted at rest with a per-account encryption key (Fernet, AES-based). Uploaded files such as receipt images and attachments are encrypted at rest as well.
- Credentials: passwords are stored only as salted hashes. OAuth tokens for connected services are encrypted at rest.
- Not encrypted: amounts and dates are stored as plain numbers inside your account's own isolated database schema, so the database can add them up for your reports. The server's disk itself is not encrypted by our hosting provider, and the master key that the per-account keys are derived from is kept on that same server, because the app needs it to show you your data. So the encryption above protects your content in a leaked database or backup, but not from someone who takes over the server itself; that is guarded by restricted access (SSH keys only, two-factor sign-in on the hosting and code accounts). Backups are encrypted separately, with a key that is not kept on the server (below).
03Backups
Nightly database backups are GPG public-key encrypted before they leave the server and stored off-site in object storage. The decryption key is not stored with the backups (key custody is split between separate locations). Backups are restore-tested automatically every day, and expire within 90 days. Separately, our hosting provider takes monthly full-server snapshots, which are kept for 12 months and then expire; they are protected by the provider's access controls rather than by our own backup encryption.
04Access control
- Two-factor authentication is available on every account, and we recommend it. It is required before you connect a bank.
- Application database access runs under a dedicated role subject to the row-level security policies above — not a superuser account.
- Human access to customer content is governed by the Limited Use commitments in our Privacy Policy: nobody reads your data except with your consent, for security investigation, or where the law requires.
05Payment security
Subscription payments are processed by Stripe, a PCI-DSS Level 1 certified payment processor. Your card number and verification code go directly to Stripe — Talisk never stores full card details.
06Service providers
The small set of providers that run parts of the Service (hosting, AI, payments, transactional email), what each receives, and where they are located is published at talisk.ai/subprocessors. AI processing is covered in the Privacy Policy: our AI provider is contractually barred from training on your data.
07Data retention and deletion
You can delete your account yourself from Settings. The account locks at once, and seven days later its entire schema — mail, contacts, books, documents — is erased from the live system unless you sign in and keep it. Encrypted database backups then expire within 90 days, and monthly full-server snapshots within 12 months. The off-site mirror of uploaded documents is additive; an erased account's documents are removed from it 12 months after erasure, once the last backup that could hold the account has expired. Details in the Privacy Policy.
08Assessments
We believe in claiming only what is true: Talisk does not currently hold SOC 2 or ISO 27001 certification. As part of Google's verification program for apps that access Gmail data, a CASA (Cloud Application Security Assessment) security assessment is planned. This page will be updated as assessments complete.
09Reporting a vulnerability
If you believe you have found a security vulnerability in Talisk, please email security@talisk.ai with enough detail to reproduce it. We will acknowledge your report promptly, keep you informed, and not take legal action against good-faith research that respects user data and avoids service disruption.