Where your data lives, and who can reach it

A short technical answer, because "bank-level security" is a phrase and not a fact. Here is what is actually running, and the numbers you can hold us to.

Your company cannot see another company’s data

Every table carries the company it belongs to, and the database refuses to return a row from a different one — not the application, the database. This is Postgres row-level security, and it holds even if a bug in our code asks for the wrong thing.

✓117 of 117 tables have row-level security switched on

✓246 access policies written against them

✓A request without a valid session returns zero rows from every one

What is running underneath

Nothing home-made where something audited exists. Each of these is a company whose whole business is doing this one thing properly.

Supabase — Postgres

Your books sit in Postgres, the database most accounting systems in the world run on. Encrypted at rest, backed up continuously, with point-in-time recovery.

Plaid — the bank connection

Your bank password is typed into Plaid, never into RunGrid. We never see it. Plaid returns a token, and that token is encrypted again by us with AES-256-GCM before it is stored — so it is unreadable even to somebody holding the database.

Stripe — the money

Card numbers never touch our servers. The payment form is Stripe’s, on Stripe’s domain, and we receive a reference. Stripe is PCI DSS Level 1, the highest tier there is.

Vercel — the application

Served over HTTPS from a global edge network, with DDoS protection and automatic certificate renewal. There is no server sitting in an office.

Anthropic and Google — the AI

Runny’s reasoning runs on Claude, image generation on Google. Neither trains on your business data. What is sent is only what the question needs, never your whole database.

Who, inside your company, can reach what

Six roles, from owner to view-only. An employee sees the jobs assigned to them; an accountant sees the financials but not the billing; only an owner can delete the company. You can require two-factor sign-in for everyone, and set how long an unattended screen stays open before it locks.

You will not run out of room

There is no disk to fill. Storage grows as you use it — a hundred transactions a month or fifty thousand, three photos on an estimate or three hundred, the answer is the same and it is not something you will ever have to manage. Files and database both scale on their own, and nothing is deleted to make space.

Nor is there a version of this where your history becomes a problem. Seven years of ledger is a small database by any modern measure, and old records stay searchable rather than being archived somewhere you cannot reach them.

It is your data, including the day you leave

Every list in the product exports to CSV, and the reports to Excel and PDF. There is no export fee, no notice period, and no support ticket required. If you close the account you can take everything with you first — which is the only version of "your data" that means anything.

What we do not claim

We are not SOC 2 certified and we do not say we are. That audit costs money and takes months, and a young product claiming a badge it has not earned is exactly the sort of thing this page exists to avoid. What is written above is what is built, and it can be checked.

Found something?

Write to security@rungridonline.com. A real person reads it, and a genuine report gets an answer, not a form.

Start your 15-day free trial →