Legal

Omnesis Mobile App Privacy Policy

Last updated: 2026-07-19

Summary

Omnesis is a local-first personal data indexer. The Omnesis mobile apps (iOS and Android) read data you explicitly grant on your phone and send it only to the Omnesis gateway you paired with the app, running on your own hardware — a machine you control. Adrien Conrath, the developer of Omnesis, does not receive a copy. There is no Omnesis-operated cloud service in that path, and the mobile apps do not send the data directly to any third party. There is no Omnesis account, no server we run, no telemetry, no analytics or advertising SDK, and no advertising identifier.

Cloud inference is off by default. If you enable a cloud model or cloud AI agent for a configured role, Omnesis sends the inputs needed for that role to the provider you choose. That provider's privacy and retention terms then apply.

If you are reading this to review a TestFlight, App Store, or Play Store submission: the short version is local-first, no cloud service operated by Omnesis, no third-party SDK calls.

Who we are

Omnesis is a project that is soon to launch in open source.

It is currently developed and maintained by Adrien Conrath. There is no company or organization operating a shared Omnesis backend or cloud service. Each user runs their own gateway on their own hardware. In this policy, “we” refers to Adrien Conrath as the developer of Omnesis.

What the apps access, and how it is used

The apps access only what you grant, through your operating system's standard permission prompts. Each type is read on your device and used for one purpose: to build a private, searchable index on your own gateway. Every one is opt-in, and you can grant, deny, or revoke each individually at any time — denied types are never read.

• Health (Apple HealthKit on iOS / Health Connect on Android) — body composition, activity, vitals, sleep, nutrition, mindfulness, environmental exposure, and workouts, in the categories you allow. Read on your device and indexed on your gateway. The apps never write back to Apple Health or Health Connect.
• Motion & activity (iOS Core Motion / Android activity recognition) — your motion-activity history (stationary, walking, running, cycling, driving), indexed on your gateway.
• Photos (iOS Photo Library / Android photos & screenshots) — the apps extract text, captions, and metadata from your images to make them searchable. No photo or image itself ever leaves your device — only the extracted text and metadata are sent to your gateway.
• Microphone & speech recognition (iOS) — captures your voice so you can dictate queries to the agent by on-device speech-to-text instead of typing.
• Call log (Android) — your call history (who, when, and duration — not call audio). Indexing it makes calls searchable and places them alongside other activity in your timeline, helping you recover context around a person or period. Omnesis does not access call audio or conversation content.
• App usage (Android) — app-usage statistics, indexed on your gateway.
• Camera — used only to scan the pairing QR code shown by your gateway on first setup. Never recorded, never stored.
• On-device storage (Keychain / app storage) — the gateway URL, pairing token, device identifier, and your per-category settings.

Beyond what is listed above, the apps do not access your contacts, precise location, calendar, or reminders.

Where your data goes

The mobile apps send permitted data directly from your phone to the gateway paired with the app.

• The app sends the data it reads (for photos, only the extracted text and metadata) to the gateway URL you enter at pairing time. You control that endpoint. The gateway provisions TLS, so the connection is normally HTTPS. If you explicitly configure plain HTTP, use it only on a trusted private network.
• The gateway runs on your own hardware. Omnesis does not operate it as a cloud service — each user runs their own.
• There is no Omnesis cloud relay, no third-party analytics, and no cross-device sync through any server we run.

Cloud models are your choice

On your gateway, Omnesis can use AI models for tasks like turning documents into search vectors, transcription, OCR, and answering questions. For each of these you choose where inference runs:

• a local model — runs on your own gateway, so nothing leaves your machine; or
• a cloud model or AI agent — the inputs needed for the configured role are sent to the provider you selected.

Cloud inference is off by default. When you enable it for a configured model role, Omnesis sends the inputs needed for that role to the provider you selected. That provider's privacy and retention terms apply. We recommend choosing a provider and account plan that offers zero data retention for the API you use, and verifying its terms before sending personal data. Omnesis does not verify or enforce a provider's retention policy.

What Omnesis does NOT do

• We never receive or store your data on any server we operate.
• We do not include any third-party analytics, advertising, or crash-reporting SDK.
• We do not use IDFA or any advertising identifier.
• We do not share, sell, rent, or lease your data.
• We do not profile you for any purpose.

Retention

Retention is controlled entirely by you, on your own gateway. On the phone, the apps store only:

• The pairing credentials, until you unpair.
• An offline buffer of batches that failed to upload, capped in size and evicted oldest-first. On successful upload, batches are deleted from the device.
• No indexed content is kept long-term on the phone. The app is a conduit, not a store.

User control

• Revoke any permission at any time in your OS settings (iOS: Settings → Privacy & Security; Android: Settings → Apps / Permissions, and the Health Connect app for health data). Revoked data immediately stops syncing.
• Pause individual categories inside the app — toggle any category off and the sync rotation skips it.
• Unpair — wipes the pairing token and all settings from the device.
• Delete the app — removes all local state, including credentials and the offline buffer.

Data already on your gateway

This policy covers the mobile apps. Data the apps have already pushed to your gateway is under your direct control there — for example, via the Omnesis CLI:

Children

Omnesis is not intended for users under the age of 13 (or the minimum age of digital consent in your jurisdiction, whichever is higher).

Changes to this policy

When this policy changes, the Last updated date at the top of the page moves. Material changes will be reflected on this page.

Contact

Questions about this policy can be emailed to contact@omnesis.dev.