Your phone remembers a room better than you do.
Visual memory for the real world
- Permissions
- 1
- Content transmitted
- none
- Account required
- no
R17 PLAY · Apps from Graz
Our apps compute on the device and work without a network. Recordings, audio and everything derived from them stay there — unless you explicitly send something. And when you do, you see it happen.
The boundary
Privacy here is not a setting you have to hunt for, but an edge the code never crosses on its own — only you do. This is what it looks like.
Images · Audio · Features
individual analyses
per action, off by default
Advertising · Crash reports
asked first, revocable at any time
In the catalogue
Visual memory for the real world
Every app is listed here before it reaches the store — including its permissions and data flows.
The foundation
Four things we build once, properly — then every app inherits them. That is not a technical detail; it is why we do not have to weigh the same decisions again for every app.
No advertising or analytics service starts before you have been asked. The order is fixed in code and cannot be configured — not even by accident.
One function removes the database, files, caches and key material. An automated test then searches the entire app directory for leftovers.
You sign up with us nowhere. A subscription runs through your Apple ID or Google account — where you already are. We keep no profile anyone could lose or hand over.
Every feature runs without a network. A connection is an addition, never a prerequisite — on a train, in a basement, on a plane.
Verify
For every app you can read which permission it requests and what for — verbatim. The same sentence appears in the privacy policy, because both are generated from the same source as the app itself.
They cannot drift apart: a permission without a stated reason cannot be built in at all.
We build for our own catalogue — and on commission for companies that need something of their own. From the idea to the store.
Start a conversation