All features

Security and data management

Your data.
In your hands.

Understand your data’s journey: from browser to database and back to your session. A guide to encryption, keys, metadata and authorised access.

Security and data management

The database stores the data. The key gives it meaning.

Even the Ratio team cannot read encrypted financial content from the database without your keys. Amounts, descriptions and categories are protected on your device before saving.

The same transaction, in six steps. Content becomes readable only on an authorised device.

  1. 01

    On your device

    The transaction is readable here.

    Your device reads it.

    The browser reads your statement. Here you can check the expense before confirming: this is where its content is readable.

    Illustrative exampleSupermarket · €42.50
  2. 02

    On your device

    Before saving, I encrypt it.

    The key protects it.

    The device uses the financial key to turn the amount, description and category into an encrypted block. This happens before sending the transaction to Ratio.

    Illustrative example7xK…a9Q · AES-GCM
  3. 03

    From device to Ratio

    The encrypted block travels.

    You send protected content.

    The request sends the encrypted block along with metadata needed to save and synchronise it. Financial content stays encrypted throughout this exchange.

    Illustrative example7xK…a9Q · AES-GCM
  4. 04

    On the Ratio server

    I see an encrypted block.

    Ratio stores the block.

    The database saves encrypted content. Database access alone does not reveal what it says.

    Illustrative example7xK…a9Q · AES-GCM
  5. 05

    From Ratio to device

    It returns still encrypted.

    You retrieve the same block.

    The authenticated session requests transactions from an authorised workspace. Ratio returns encrypted content: authentication grants access, the key makes it readable.

    Illustrative example7xK…a9Q · AES-GCM
  6. 06

    On your device

    In my session, it is readable again.

    Your key opens it.

    The key is used on the device to decrypt the block. The expense becomes readable in your session and feeds search, charts and transactions.

    Illustrative exampleSupermarket · €42.50

The amount and description are fictional; the encrypted string is illustrative. Arrows show the financial content’s journey. Dates, identifiers and other operational metadata are handled separately.

How we handle your data

What this means for the Ratio team.

Reading a database row does not reconstruct the amount, description, merchant or category inside the encrypted block. The Ratio team also needs decryption keys to make that content readable: administrative database access does not replace them.

The financial key is not stored in plaintext in the database. Materials needed to restore it are protected in encrypted form; an authorised session uses them to work with data on the device.

What the service can still see.

Zero-Knowledge covers encrypted financial content, rather than every database field. Ratio handles account data such as email and subscription, workspace membership, transaction dates, identifiers and sync versions.

This metadata enables authentication, authorisation and history replication. It can reveal structural information, such as a transaction’s existence and date. Hash indexes support operation without storing descriptions in plaintext.

Passwords, recovery and devices.

Use a strong password and keep your recovery code somewhere safe. The code is part of recovering key access: support cannot reconstruct encrypted content from the database alone.

An unlocked session contains readable data on the device. Machine and access security matter alongside encryption of stored history. Local AI devices are authorised separately and can be revoked.

History, synchronisation and AI.

Ratio synchronises the encrypted replica and builds readable views on your device. Free works on the most recent 12 months and keeps encrypted history for up to 18 months.

An authorised MCP server can decrypt data locally for your model. With a local model, analysis stays in the environment you configure. If you choose an external AI provider, it also processes the data you send. Database encryption does not replace this choice.

Retention and deletion

Encrypted financial history stays in your workspace. On Free, transactions older than 18 months are permanently deleted when you run a new import; the 12-month window limits search and statistics.

From profile settings, request account deletion by confirming your email. The procedure removes the user, owned workspaces and related data from the application database. Data already exported or sent to external tools must be managed in those environments.