Some promises hold because they cannot be broken.
A privacy policy can be changed with an update. An architecture cannot. Here is what Ozorys will never do — not out of kindness, but because it's carved into the design itself.
Never any adverts, never any trackers
Ozorys serves no adverts and carries no trackers. The reason is simple: a finance app that lives on advertising has an interest opposed to yours — pushing you to spend, and exploiting what it knows about you to target better. We refuse that conflict of interest at the root.
Our model fits in one honest sentence: you pay a few euros for the app, and that's it. No hidden cost settled with your privacy.
A budgeting app funded by advertising wins when you spend and when your data sells. A tool that genuinely serves you cannot live off the opposite of your interest.
Never a bank aggregator
Ozorys will never connect to your bank to read your accounts. Where others demand that total, permanent access, we make the deliberate choice of manual entry: no third party reads your transactions, because no bridge to your bank exists.
What we don't plug in can be neither read, nor profiled, nor breached. The small discipline of the gesture is the price — a very profitable one — of total privacy.
The bank connection is the entry point of all financial surveillance. By never creating one, Ozorys closes the door before it can even open.
Never any readable data server-side
Thanks to Zero-Knowledge, we hold no readable version of your data: not your amounts, not your categories, not the slightest exploitable trace. This isn't “we don't look” — it's “we cannot”. What we don't possess can be neither sold, nor stolen, nor seized.
That seriousness extends right down to infrastructure details: our sending domain is authenticated so that our emails can't be spoofed, for instance. Privacy is also decided in the wings nobody ever sees.
Promises carved, not posted
Most privacy commitments live in a text — a policy that a single change can empty of meaning overnight. Ours live in the architecture: local encryption, no server that reads you, no aggregator. They can't be revoked with an update to the terms, because they aren't words — they're properties of the system.
It may be Ozorys's most reassuring promise: you don't have to trust us. The design protects you even if our intentions were to change one day.
Faced with any service, tell apart what's promised in a text from what's guaranteed by the engineering. Only the latter holds when interests change.
Let's check it stuck
Six questions, marked instantly. Your answers never leave this page.
1. Why does Ozorys refuse advertising?
We refuse that conflict of interest at the root: you pay for the app, not with your data.
2. Does Ozorys connect to your bank?
What we don't plug in can be neither read, nor profiled, nor breached.
3. What do our servers hold of your data?
“We cannot”, not “we don't look”: that's Zero-Knowledge.
4. The difference between a policy and an architecture?
Our commitments are properties of the system, not revocable words.
5. “What we don't possess…”
Being powerless to read your data is the best protection of all.
6. The right test for any service?
Only what's technically guaranteed holds when interests change.
Today's challenge
Reread the privacy policy of the finance app you use, then ask yourself: is this guaranteed by the engineering, or merely promised by a text that can be changed? The answer says a great deal about who really protects your data.