Telona

Security & trust

We can see your wealth.
We can never move it.

Security here isn't a badge you hover over — it's the architecture. Account aggregation is read-only everywhere. A human approves everything that touches money. And every action is written to a record you can read for yourself. Trust you can check, not just claims you have to take on faith.

Read-only by design. The agent prepares and verifies — and nothing moves until you say so.

The architecture

The money rail never runs
through us.

Here is the whole data flow, in one direction — nothing hidden. Your institutions feed a read-only aggregation into Telona. When something needs to move, the agent hands you a prepared action, and the transfer happens between you and your bank, on a leg that bypasses Telona entirely.

Your institutionsBanks, brokerages & fund admins
Read-only aggregationvia Plaid · balances & activity only
TelonaNormalizes, verifies, prepares

Read path — data only, in one direction. Telona can see, never send.

You approveOne tap — the only ask
Your bankMoves the money — not us

Money rail — you → your bank. This leg never touches Telona's servers.

The approval gate

Nothing is sent
without your click.

The gate everyone else treats as a workflow, we treat as a security control. The agent prepares each money-adjacent action and runs the checks — but the send is always yours. And when the receiving-bank details on a capital call don't match the last several, we always hard-flag it before you ever see an approve button.

Wire details changed

The receiving bank differs from the last three calls on this fund. We've held it for your review — nothing goes out until you say so.

Amount matches commitmentDue date verifiedReceiving bank — flagged

See the full approval flow on the home page

The controls

What's actually in place.

Here is the concrete list — and, just as plainly, where we're still on the path. We mark anything not yet certified, and we never claim a cert we don't hold.

Encryption at rest & in transit

Everything is encrypted in transit (TLS) and at rest. Aggregator access tokens are stored encrypted, isolated from application data.

MFA — TOTP & SMS

Two-factor sign-in with an authenticator app (TOTP) or SMS, enforceable across your whole workspace.

Per-tenant isolation (RLS)

Row-level security scopes every query to your workspace at the database. One tenant can never read another's rows — enforced by Postgres, not by app code.

Immutable audit log

Every agent action and human approval is written to a hash-chained, append-only ledger. Records are computed done, never asserted — and cannot be silently edited.

Scoped roles & permissions

Owner, collaborator and CPA-guest roles with least-privilege access. Guests see only the package you share, for only as long as the link lives.

SOC 2-track controls

SOC 2 — in progress

We build to the SOC 2 control set from day one — access reviews, change management, logging and vendor diligence.

Data export & hard delete

Export your full workspace as CSV or JSON anytime. Delete for real: a hard delete purges your data and revokes and destroys every aggregator token.

The boundary

Three lines it will never cross.

  1. 01

    It cannot move funds

    There is no code path from Telona to a payment rail. The money leg runs entirely between you and your bank.

  2. 02

    It holds no custody

    Aggregation is read-only. Telona never holds, receives, or routes your assets — it observes and prepares, nothing more.

  3. 03

    No setting turns this off

    The boundary isn't a toggle or a plan tier. It's structural — the same in every workspace, for everyone.

Your data

You own your data. Full stop.

Export everything as CSV or JSON whenever you want — it's yours to take with you. Delete for real: a hard delete purges your workspace and destroys every aggregator token. And we do not, and will not, sell your data.

  • Export anytimeFull workspace, CSV or JSON
  • Delete for realPurges data + aggregator tokens
  • No data sellingNot now, not ever