What happens to your data, in plain words.
No badges we haven't earned. Here is where your files go in each part of Milyo, and what we haven't done yet.
Free matcher · try.milyo.app
Your files never leave the tab.
Your file→Matching engine, running in your browser→Results on screen, CSV to your disk
The page's security policy forbids it from sending data anywhere but its own address, and it has no upload endpoint. Close the tab and everything is gone. Check it yourself: open the network tab while you match.
Paid app · private beta
Stored, encrypted with your own key.
Your source→Card numbers masked→Encrypted per tenant, Frankfurt (EU) Planned
Saved sources and schedules mean we must keep your transactions. Customer rows live in a separate data plane; the part of Milyo that holds settings and billing never reads them.
| Concern | What we do |
|---|---|
| Keeping customers apart | Every row carries its tenant, and the database itself refuses cross-tenant reads (row-level security) as a second wall. |
| Encryption | Each customer gets its own data key. It protects stored files and sensitive columns. Wrapping it with a cloud key-management key comes with hosting in Frankfurt. Planned |
| Leaving Milyo | Deleting your org destroys its key. Every copy becomes unreadable, backups included. |
| Card numbers | Values that look like card numbers and pass a Luhn check are cut to the last 4 digits before anything is stored, raw files included. |
| Source credentials | Kept in a secrets manager. Our database only holds a reference to them, and they never appear in logs. Planned |
| Database sources | We ask for a read-only user, test it, and warn you if it can write. Milyo never moves money. Planned |
| Sign-in | Sign in with Google (Microsoft on request). We store no passwords. |
| Audit log | Append-only: no screen or API can edit or delete an entry. Sign-ins, org and member changes, runs and exception actions are logged. Private beta CSV export for owners is Planned |
| Corrections | Transactions and matches are never edited in place. An unmatch or write-off is a new record; the original stays in history. Private beta |
Not done yet
- SOC 2 audit. We'll start when the first customer needs it, and say so here.
- SAML single sign-on and custom roles.
- Bring your own key.
- Running the engine inside your own cloud. It's designed for, not built.
Found a problem?
Email security@milyo.app. A person reads it within one working day. Please don't test against other customers' data.