How your books are kept safe.

Your books hold your customers, your income and your tax IDs. Here is what Ekue does to protect them, in plain terms.

Start free

Every business is walled off in the database

Many products keep customers apart with checks in their application code, where one missed check can show one business another's data. Ekue enforces it inside the database itself, with Postgres row-level security: every request can only read and write the rows of the business it was opened for. An automated test walks every table to prove one business cannot see another's rows.

Signing in

Sensitive details are encrypted

Your business's EIN or SSN, your vendors' tax IDs, two-factor secrets and payment keys are encrypted before they are stored. Ekue shows a tax ID only by its last four digits.

Your files are private

Receipts and bills you upload are checked for what they really are, capped in size, and stripped of hidden metadata such as a photo's location. They are kept in private storage and opened through links that expire within minutes.

Card payments never touch Ekue

When a customer pays an invoice, the charge happens on your own Stripe account. Card numbers go to Stripe, not to us, and the money goes straight to you.

Who can see your books

Report a problem

If you think you've found a security issue, email support at ekue.com with "Security report" in the subject. Please give us a chance to fix it before telling anyone else.

Try it on this year's books.

30 days free, no card. Export everything if it isn't for you.

Start free