Privacy Policy

Last updated: November 2026

Omnesis is built so your data stays under your control. This policy explains, in plain language, what we collect today (very little) and how the Omnesis app handles your data once it's installed.

The short version

Email updates

If you enter your email address in the sign-up form, we use it for one purpose: to email you about Omnesis product updates. We process and store these emails through Kit (formerly ConvertKit), our email provider. We do not sell your email address or share it with anyone else. Every email we send includes an unsubscribe link, and you can ask us to delete your address at any time (see Contact below).

The Omnesis app

Omnesis connects to the sources you choose (such as email, messages, notes, calendar, files, and health data) and builds a searchable index of them. That index, and the data in it, lives on hardware you control. We don't receive a copy of it.

Omnesis supports encryption at rest for its main local databases and supported secrets. Enable it with omnesis secure; we also recommend keeping FileVault or LUKS enabled for full-disk protection.

Omnesis uses AI models for tasks like turning documents into search vectors and answering questions. Local models keep processing on your machine. Cloud inference is off by default; if you enable a cloud model or external AI agent, Omnesis sends the inputs needed for the configured role to the provider you choose. 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.

Source icons. To show each source's logo, the gateway downloads the icon from the address its source declares, usually the provider's own website (the Gmail logo, for example, comes from Google). It does this when a source reports its details and when the portal lists the sources you can add, including ones you haven't connected. The converted icons are cached, and a restarted gateway downloads them again. These requests contain none of your indexed data, but each provider sees your gateway's IP address and a request that identifies itself as an Omnesis gateway. There is no setting to turn these downloads off.

The Omnesis mobile apps and browser extension have their own detailed privacy policies — see the Omnesis mobile app privacy policy for the device permissions the apps use, and the Omnesis browser extension privacy policy for the browser data the extension reads.

Optional Omnesis account

Some builds of the gateway and apps offer an optional Omnesis account. It lets you reach your gateway from outside your own network through the Omnesis relay at relay.omnesis.app, and add a device to your gateway by signing in. You sign in with Google or with a passkey. The relay stores a random account identifier, your passkeys' public keys and labels, a one-way digest of your Google account's identifier, and the names of the gateways you connect. It does not store your email address; when sign-up is by invitation only, it uses the Google account's email address once, to ask Google whether it belongs to the invitation group. Traffic to your gateway stays encrypted end to end, so the relay never receives your indexed data. Like any relay, it sees connection metadata such as IP addresses, timing, and sizes. relay.omnesis.app is served through Cloudflare. You can delete the account yourself from its account page. The mobile app privacy policy describes all of this in full.

This website

This website does not run analytics or set advertising cookies. You can submit an email for updates or participate in public blog discussions. Your theme preference (light or dark) is stored locally in your browser. When you load comments, the widget receives the current theme so it can match the page. The site loads a few third-party assets — web fonts and the brand logos shown in the product illustrations — which means your browser contacts those providers to fetch them; this is standard for loading external images and fonts and is not used to track you.

Blog comments and reactions

Blog discussions use Giscus. The comment widget loads only after you choose Show comments; your browser then contacts giscus.app and GitHub to display the discussion. You can read comments without signing in. Posting a comment or reaction requires GitHub authentication. When you sign in, Giscus stores an encrypted authentication token in your browser to keep you signed in.

Comments and reactions, including your GitHub profile identity, are public and stored in GitHub Discussions. They can be read on both this website and GitHub. Do not include private information in a comment. These interactions are subject to Giscus's privacy policy and GitHub's privacy statement. Manage your comments and reactions on GitHub; contact us about moderation or removal.

Your choices

Changes

Omnesis is evolving, so this policy may change. We'll update the date at the top when it does.

Contact

Questions about this policy or your data? Email contact@omnesis.dev.