Private by architecture.
Ormiko is a relationship memory that lives on your phone, not on our servers. Your conversations, the people in them, and everything Ormiko learns are stored in an encrypted database on your own device. The only thing that ever leaves is the audio or text we send to Google Gemini to transcribe and understand it.
Last updated: June 13, 2026
At a glance
The whole policy in six commitments. The detail follows below.
On-device knowledge graph
Everything Ormiko knows about your relationships is stored locally in SQLite — not on our servers.
One cloud dependency
Audio and text go to Google Gemini for transcription and extraction. Nothing else is sent anywhere.
Location on-tick only
Place triggers check your location at the moment of a nudge — there is no continuous background tracking.
No call-log scraping
We deliberately dropped the Android call-log permission. Your phone history is none of our business.
No biometrics
Ormiko stores no facial-recognition or voiceprint templates. Camera frames, if ever used, are processed then discarded.
Export & delete
Export your entire knowledge graph to JSON at any time, or wipe it. It's your memory to keep — or take away.
01The short version
- Your data lives on your phone. People, places, projects, commitments, durable facts and your raw transcripts are stored in an encrypted database on the device. Ormiko runs no servers that hold this graph.
- One thing leaves the device: the audio or text we send to Google Gemini to transcribe and understand it — under your own Gemini API key.
- No call-log scraping and no biometrics. We don't read your Android call history and we store no face or voiceprint templates.
- Location is checked on-tick only, coarsened to roughly city level, and has an off switch. There is no continuous background tracking.
- You're in control. Export your whole knowledge graph to JSON, or wipe everything, whenever you want.
02What Ormiko captures
Ormiko works from the conversations you bring it. That can be a phone call you choose to record, a voice note, a clip from your Wear OS watch, or a typed text note. You decide what goes in — Ormiko does not silently harvest everything around you.
From each capture, Ormiko derives a private knowledge graph: who was involved, the topics and places discussed, the commitments made, and durable facts worth remembering (roles, deal terms, life events). It keeps the full transcript alongside that graph so a later recap is grounded in what was actually said.
03Where your data lives
Everything above — the people, places, projects, commitments, facts and raw transcripts — is stored locally in an encrypted SQLite database on your phone. There is no Ormiko cloud account holding your conversations, and no Ormiko server that stores your relationship graph. We cannot read your data, because we never receive it.
The behavioural history that tunes your nudges — which reminders you act on and when — is part of this on-device store and never leaves the device.
04The one thing that leaves your device — Google Gemini
To turn audio and text into a transcript and a structured understanding, Ormiko sends that captured audio or text to Google's Gemini API. This is Ormiko's single cloud dependency. Nothing else — not your knowledge graph, not your nudge history, not your contacts — is sent to any third party.
You supply your own Google Gemini API key, so this processing happens under your own Google account and is governed by Google's Gemini API terms. Your relationship with Google for that processing is direct; Ormiko is simply the app that formats the request and files the result back into your on-device graph.
Camera frames, on the rare path where vision is used, are sent for that single processing step and then discarded — they are never stored as images or turned into biometric templates.
05Location & context
Some nudges are place-aware — a reminder that makes sense as you arrive at the office, for instance. To make those work, Ormiko checks your location on-tick only: at the single moment a context nudge is being evaluated. There is no continuous background location tracking, and Ormiko does not build a history of where you've been.
Any location or weather coordinates used for context are coarsened to roughly city level. Location is optional, and like every sensitive sensor it has an off switch in Settings → Privacy.
06Permissions we request — and exactly why
Ormiko asks only for what a given feature needs, and several of these are strictly opt-in. You can run the core of the app without granting the optional and opt-in ones.
- Microphone
- To record voice notes and watch clips, and to capture calls you choose to record.
- Notifications
- To deliver right-moment nudges and your pre-call briefs.
- Draw over other apps (overlay)Opt-in
- To show the pre-call brief card on top of the dialer at ring time.
- Call screening / redirection roleOpt-in
- To know a call is starting so the brief can appear the instant the phone rings or you dial out.
- LocationOptional
- For on-tick place triggers — checked only at the moment a nudge is evaluated, never tracked in the background.
- CalendarOptional
- For meeting-prep nudges that surface the right context before an upcoming meeting.
The overlay and call-screening roles power the pre-call brief card. They are opt-in — Ormiko will not show the brief at ring time unless you turn them on. Notably, that native brief reads from a snapshot and never opens your encrypted database directly.
07What we deliberately don't do
- No call-log scraping. Ormiko deliberately does not request the Android
READ_CALL_LOGpermission. Your phone history is none of our business. - No biometrics. Ormiko stores no facial-recognition or voiceprint templates. Camera frames, if ever used, are processed and then discarded.
- No selling your data. We don't sell, rent or broker your conversations, contacts or graph. There's nothing to sell — it lives on your device.
- No ad tracking. Ormiko isn't an advertising business and doesn't build an ad profile of you.
- Your nudge-learning stays put. The history of which reminders you act on never leaves the device.
08Your controls
- Export everything. Export your entire knowledge graph to JSON at any time — it's your memory to keep and take with you.
- Delete everything. Wipe all of your data from the device whenever you choose.
- Per-sensor switches. Every sensitive sensor, location included, has its own off switch in Settings → Privacy.
09Children's privacy
Ormiko is a tool for working adults and is not directed at children under 16. It is not designed for, marketed to, or intended for use by children, and we do not knowingly collect information from them.
10Changes to this policy
As Ormiko evolves, this policy may change. When it does, we'll update the “last updated” date at the top of the page. The architecture described here — on-device by default, with Gemini as the single cloud dependency — is the principle we intend to keep.
11Contact
Questions about privacy, or anything in this policy? Reach us at hello@ormiko.app.
A note on this page. This describes how Ormiko approaches your privacy as a product — on-device by default, with Google Gemini as the single cloud dependency under your own key. It reflects how the app is built today and isn't legal advice. If a specific guarantee matters to your situation, write to us and we'll be straight with you about exactly how it works.