Privacy Policy

Who we are

Omega Ex, Inc. ("Omega Ex", "we", "us") is a Delaware corporation with its principal office at 58336 Overseas Highway, Marathon, Florida 33050, United States. We are the controller of the personal information described here.

Questions, requests, or complaints: [email protected]

Omega Ex is a desktop assistant for macOS. This policy covers the Omega Ex application, our hosted workspace, and this website.

The short version

• Omega Ex runs mainly on your own computer. Your conversations, memories, meeting transcripts, notes, and dictation history are stored in a database file on your device, not on our servers, unless you turn on our hosted workspace.
• We do not sell your personal information, and we do not share it for advertising. We run no advertising, no analytics, and no trackers of any kind in the application.
• We do not use your content to train, fine-tune, or evaluate any AI model.
• To answer you, the app sends your request to an AI provider. That is how the product works. Section 7 names every provider and says what each one receives.
• Voice features that can identify a person are off until you turn them on. See Section 6.
• You can export everything we hold from inside the app, and delete your account there unless it uses company sign-in. See Section 13.

The rest of this policy is the detail behind those statements.

Where your data actually lives

On your device (the default). Omega Ex stores your data in a local database file and in folders belonging to the app: your chats and messages, extracted memories, meetings and transcripts, notes, tasks, documents, generated images, dictation history, and an activity log of actions the assistant took.

That local data is protected by the security of your own computer and your macOS account. We recommend enabling FileVault, macOS full-disk encryption. The Omega Ex database file itself is not separately encrypted, so anyone with access to your unlocked Mac account can read it.

On our servers (only if you enable it). If you sign in to the hosted workspace, your data also syncs to our servers so it survives losing a device and can follow you between machines. The hosted workspace runs on Amazon Web Services in the United States, in the us-east-2 region in Northern Ohio, where your data is held in a database file on an encrypted volume. Current versions encrypt credentials before saving them, on your device or the hosted workspace. Provider keys saved by older versions, before this encryption was added, can still be stored unencrypted.

Sent to AI providers (per request). To produce an answer, the content of that request goes to the AI provider handling it. Providers do not receive your whole store, only what a given request needs. See Section 7.

What we collect, and why

We collect only what a feature needs to work.

We do not collect: analytics, usage tracking, behavioural profiles, advertising identifiers, session recordings, heatmaps, or location.

Diagnostics are opt in and off by default. Logs stay on your device unless you press the button to send them.

Voice recordings and speech to text

Omega Ex turns speech into text in three different places, and they do not all keep your audio on your computer. Which one applies depends on how you are running Omega Ex, so this section says what each one does rather than making a single promise that would be wrong for some of you.

The desktop app running its own engine on your Mac. Local, end to end. The app builds one speech engine from its configuration, and every configuration we ship selects the on-device engine. There is no cloud fallback: if the configured engine cannot be built, the app raises an error rather than quietly substituting a different one. Push-to-talk dictation and meeting capture are transcribed on your machine, and the audio is not sent anywhere.

The desktop app connected to our hosted workspace. Audio goes to our own server. A build that is pointed at the hosted workspace does not run a speech engine locally. It sends the recorded audio to the workspace, where it is transcribed with Whisper, a speech engine Omega Ex runs itself on its own server, hosted by Amazon Web Services in the United States. No speech company receives the audio. On that build, audio leaves your machine on the ordinary push-to-talk key, with nothing to select and nothing to switch on. The two builds look the same in use, so if this matters to you, ask us which one you have before you rely on it.

The hold-to-speak button on notes, in a web browser. Audio goes to your browser vendor. That button does not use either engine above. It uses the speech recognition built into the browser itself. In Google Chrome and Microsoft Edge, that feature works by sending the captured audio to Google's speech service and returning text, so your voice reaches Google. This happens inside the browser, before Omega Ex receives anything, and there is no setting in Omega Ex today that turns it off or asks you first. If you would rather that did not happen, do not use the hold-to-speak button on notes. Typing the note does the same thing and sends no audio anywhere.

What we keep is the transcript. Where audio reaches Omega Ex, what we store is the text. On the browser path the audio never reaches us at all, so what happens to it there is governed by your browser vendor's terms rather than by this policy.

A speech provider Omega Ex no longer uses. Until 1 October 2026, Omega Ex used Deepgram, Inc. for speech. Deepgram received dictation, conversation and meeting audio sent to it for transcription, and the text of spoken replies and recording disclosures that it turned into speech when a cloned voice was not used. From 1 October 2026, Omega Ex sends none of your audio or text to Deepgram. Audio and text sent to Deepgram before that date remain subject to Deepgram's own terms.

Voice and biometric information

Some Omega Ex features can create a voice signature, a mathematical pattern derived from a person's voice that can distinguish one speaker from another. Under Illinois, Texas, Washington, and certain other laws, that is a biometric identifier, and under the EU GDPR it is a special category of data. We treat it that way.

6.1 We ask first

Both features below are off until you switch them on in Settings, Privacy. Nothing creates a voice signature and nothing creates a voice clone unless you have turned that specific feature on. Turning it off again stops it.

6.2 What the two features do

Speaker separation in meetings. To label who said what, Omega Ex can compute a voice signature for each stretch of speech and group similar ones together.

• The signatures exist only in memory, only for the duration of that one meeting. They are never written to disk and never sent to a server.
• They are destroyed when the meeting ends, and are not reused, not stored, and not matched against any other meeting or any other person.
• If you leave this feature off, Omega Ex still separates speakers using a simple pitch measurement, which is not a voice signature and cannot identify anyone.

Cloned voice replies. If you have set up a cloned voice, reply text is sent to ElevenLabs, which returns speech in that voice. Creating a clone requires voice samples of the person being cloned, and their consent. If you leave this feature off, nothing is sent to ElevenLabs: the desktop app on a Mac uses a voice built into the Mac, and the web app does not speak replies. On the hosted service (the web app, and a desktop app connected to it), a reply built from content read from a connected account in the same chat is not sent for the cloned voice either. Instead, the desktop app on a Mac says it in a voice built into the Mac, and otherwise it is shown as text. A reply built from such content carries a mark Omega Ex puts on it (see the box in Section 7). Omega Ex marks a reply only while the mail or calendar content it read is still in the chat history it works from, and earlier replies that repeat that content do not pass the mark on, so once Omega Ex trims a chat's history to fit, which in a spoken conversation can happen within a few turns, or reloads it from storage, which can happen at any point, a later reply built from those earlier replies may not carry it, and its text would then be sent. On a desktop install running its own backend, nothing holds those replies back from the cloned voice: the app's own speaker, which speaks replies in Conversation Mode and in Companion Mode (the on-screen helper), never checks the mark, so replies built from connected-account content can still be spoken in the cloned voice.

6.3 Our retention and destruction schedule

Required by Illinois BIPA and published here for that reason:

We do not sell, lease, trade, or otherwise profit from biometric information, and we do not disclose it except as required by law or with your consent.

6.4 Other people in your meetings

If you record a meeting, other participants are not our customers and have not agreed to anything with us. You are responsible for telling them and for getting whatever consent the law where they are requires. Many US states require the consent of every party to a recording. Omega Ex shows a visible recording indicator and can announce a disclosure for you, but the legal obligation is yours. See our Acceptable Use Policy.

AI providers, and what each one receives

Omega Ex cannot answer you without sending your request to an AI provider. The current, live list is published on our Subprocessors page and the app also shows it in Settings, Privacy, generated from your actual settings rather than from a written list, so it cannot drift from what the software really does. The avatar provider, a client-specific beta, is named here and on the Subprocessors page but is not yet in that in-app list.

In summary:

About training. We do not use your content to train any model. Whether a given provider may use content sent to it depends on the account and service tier we or you are using with that provider, and those terms are set by the provider, not by us. We publish the current position for each provider on the Subprocessors page and update it when it changes. If a no-training commitment matters to you, check that page before relying on it.

We do not send your content to any provider not listed on that page.

Google user data, and our Limited Use commitment

This section applies when you connect a Google account. If you never connect one, nothing here is about you. Company sign-in with Google, which is separate from connecting an account, is described in Section 9.

The Limited Use requirements mean information received from Google APIs must be:

• Used only to provide or improve the features you asked for, the ones the permission was granted for, and visible to you in the app.
• Transferred only where it is necessary to deliver those features, to comply with the law, or as part of a merger or acquisition with notice to you.
• Never used for advertising, of any kind, by us or by anyone we send it to.
• Never used for credit decisions, lending, or any similar determination.
• Never sold, and never shared for cross-context behavioural advertising.
• Never used to develop, improve, or train any generalised or general-purpose AI or machine learning model, by us or by anyone we send it to.
• Not read by humans, except with your specific agreement for a named purpose such as support you asked for, to investigate abuse or a security incident, or where the law requires it. Where we must, we handle the smallest amount of data that answers the question.

The Google permissions we request

The Google scope tier is set per installation. The identity tier and the dated hosted pilot have different permissions. The pilot is a limited test, not a general launch or a claim that Google verification or a CASA assessment has been completed.

Ordinary Google connection

On an installation configured for the identity tier, connecting a Google account asks for one permission.

That is the whole of the ordinary connection. At this level Omega Ex cannot read or send your mail, cannot see or change your calendar, and cannot open or save your Drive files, because it has not been granted permission to do any of those things. Connecting a Google account tells Omega Ex which account you connected, and nothing more. Connecting does not sign you in. Omega Ex does not look at connected accounts when it decides who may sign in, so connecting or disconnecting a Google account does not create or remove an Omega Ex account, and does not change whether Omega Ex lets you sign in.

Company sign-in with Google, where we offer it, is separate from connecting a Google account. It is its own request to Google, apart from the one made when you connect an account and from the staged levels of access this section describes, and it asks for three permissions: openid, email and profile. Of the three, only openid is also part of connecting a Google account: no stage of connecting asks for email or profile. Company sign-in does not connect your Google account, and it gives Omega Ex no access to your mail, your calendar or your Drive files.

Company sign-in never creates an Omega Ex account. It works only for an account set up for it in advance, by us or by an administrator of your organization, and only when your Google account belongs to an organization's domain that we have also set up for it. An account set up this way has no Omega Ex password, so you sign in to it only through Google. If we move an existing Omega Ex account to company sign-in, its password stops working, the hosted workspace ends every session signed in with that password, and the account keeps the data it holds. A desktop app signed in with that password stays signed in on that computer, but can no longer sync with the hosted workspace, until you sign out of it.

When Google returns a sign-in to Omega Ex, including one that Omega Ex then refuses, Omega Ex reads these details about you from Google's reply: your Google account identifier, your email address and whether Google has verified it, your organization's domain, and your name. It does not use anything else about you in that reply. On every sign-in, Google must confirm that the address is verified and that the account belongs to that domain. On the first sign-in, Omega Ex also checks that the address matches the one on the account that was set up, then adds your Google account identifier to that account. Later sign-ins are matched to that identifier, not to an email address. If no account has been set up for you, the sign-in is refused and nothing from Google is added to any account. The identifier is the only thing from Google that Omega Ex adds to your account: it does not store your name, and it keeps no Google token from the sign-in.

Because company sign-in leaves Omega Ex no Google token, and Omega Ex does not ask Google again whether you may stay signed in, withdrawing Omega Ex's access at Google does not end a session that has already started. In a web browser signed in to the hosted workspace, a session started with Google lasts at most 72 hours, and after that you sign in with Google again.

If you use company sign-in in the desktop app connected to our hosted workspace, the sign-in takes place in your web browser, and the app then receives its own session from the hosted workspace. While you use the app, it checks that session with the hosted workspace when it can, and treats you as signed out once a check finds that the hosted workspace no longer accepts it. The hosted workspace stops accepting that session 72 hours after you signed in, so the app treats you as signed out at its first check after that. If the app gets no confirmation, it treats you as signed out 72 hours after the last one, counting the sign-in itself. On a computer that has been offline, that can be more than 72 hours after you signed in.

Dated hosted mail and calendar pilot

The pilot covers one invited client and founder test accounts. It ends when the hosted store moves to row-level security, or on 7 March 2027, whichever comes first. We do not send a 30-day material-change notice for it, because the pilot admits only invited accounts, and no data access changes for an account that does not connect Google. It is not active merely because this policy describes it. For your account it starts only with your separate agreement in the app as you connect Google, then Google's consent, then our separate activation approval.

The hosted pilot uses the mail_calendar tier and requests exactly these three permissions. If the hosted service is switched to this tier, the Google connection row and consent screen show these permissions to every hosted account. Only users listed as test users for Omega Ex's Google OAuth app, which is in Google's Testing status, can authorize the connection; other hosted accounts are not admitted to the pilot:

gmail.modify is a restricted Google scope. This pilot requests no Drive scope: Omega Ex cannot open your Drive files through this connection. Nor does the pilot request the Google email or profile scopes. To show you which account is which, Omega Ex asks Gmail for the address of each mailbox you connect, using the Gmail permission above and no other. If you allow Calendar but not Gmail, the account is listed without its address. We use the OAuth app in Testing with explicitly listed test users; the client's Google Workspace administrator must trust the client ID. Testing grants require reconnection after seven days. There is no public enrolment in this pilot.

The pilot stays in Suggest. Google actions are proposed for your review; the pilot does not authorize unattended mail or calendar writes. Its Google capabilities must remain at Suggest, including after reconnection. This is a required pilot setting. At Ask first or Auto, an instruction hidden in an email Omega Ex read earlier in the chat could lead it to label or archive mail, or at Auto send it, without asking you first. You may connect up to five Google accounts to one Omega Ex account. Omega Ex stores each account's address with its connection and shows it to you in Settings and, when more than one Google account is connected, on the approval card for a draft or a send, so you can tell the accounts apart. Every draft or send waits for your approval, and when more than one Google account is connected, it names the account it acts on. Disconnecting an account deletes its connection and the address stored with it. Client sessions take place with the client present and their agreement recorded; founder tests use founder data.

On the hosted service, replies built from connected mail or calendar content are not spoken in the cloned voice or the avatar. On the hosted service (the web app, and a desktop app connected to it), when Omega Ex builds a reply from mail or calendar content it read from a connected account, that reply is held back from the cloned voice and from the avatar: the desktop app on a Mac says it in a voice built into the Mac, and otherwise it is shown as text (the web app does not speak replies). The hosted hold-back works by marking the reply when it is built. Omega Ex marks a reply only while the mail or calendar content it read is still in the chat history it works from, and earlier replies that repeat that content do not pass the mark on, so once Omega Ex trims a chat's history to fit, which in a spoken conversation can happen within a few turns, or reloads it from storage, which can happen at any point, a later reply built from those earlier replies may not carry it, so it may still be spoken in the cloned voice or shown on the avatar. On a desktop install running its own backend, replies built from connected-account content are held back from the avatar, subject to the same trim and reload gap, but the app's own speaker, which speaks replies in Conversation Mode and in Companion Mode (the on-screen helper), never checks the mark, so they can still be spoken in the cloned voice.

Mail and calendar results can remain in messages, activity rows and derived memories in the hosted store and in synced copies. Disconnecting Google stops new access; it does not erase those copies. Pilot data must be deleted at offboarding or the pilot's end. Section 12 explains the limits of in-app deletion, including backups and provider copies.

Broader access planned for later

Outside the dated pilot, wider Google data access remains subject to the matching Google review and updated disclosures before activation. The following is the planned sensitive tier, not an additional pilot grant:

The ordinary connection cannot read an inbox. The hosted pilot can, under the restricted scope and operating limits above. Future wider tiers must not be enabled on the strength of this pilot's consent.

You can revoke this at any time, in Settings, Connections inside Omega Ex, or directly with Google at myaccount.google.com/permissions. Revoking stops all further access to a connected account immediately.

Microsoft and other connected accounts

You can also connect a Microsoft account, or a mailbox that uses an app password, such as Yahoo. These are your own accounts answering you on your instruction, and the same commitments apply.

The Microsoft permissions we request

When you connect a Microsoft account, the consent screen lists exactly these permissions and no others.

Sending and deleting are not silent. Sending mail as you, and deleting a calendar event, are classed as irreversible actions, so by default they are queued and happen only after you approve them. You can raise that to full autonomy for a capability in Settings, Connections, which is what that setting means: it will then act without asking you first. In the reply that reads an email, a web page or other connected-account content, that content cannot make Omega Ex change a connected account on its own: any change that reply then asks a connected account to make waits for your approval, whatever the setting. A later reply is not always held that way, including a later part of a message that Omega Ex handles separately, so at Ask first or Auto a change prompted by earlier content can run without asking.

We never use information from these accounts for advertising or credit decisions, never sell it, and never use it ourselves to train, fine-tune, or evaluate any AI model. Marked content follows the provider limits in Section 7. History and derived material without a mark can reach a provider on a key you added yourself, under your agreement with that provider; Omega Ex cannot guarantee whether it trains on that material. Information from these accounts is not read by humans except on the same narrow terms set out in Section 8.

You can disconnect any account at any time in Settings, Connections. That deletes the stored credential, so Omega Ex stops having access. Microsoft does not offer a revocation API, so after disconnecting you should also remove Omega Ex Connectors at myaccount.microsoft.com/privacy. An app password can be revoked directly with your mail provider, which cuts access immediately.

What we never do

• We do not sell your personal information, and we have not in the preceding twelve months.
• We do not share your personal information for cross-context behavioural advertising.
• We do not use your content to train, fine-tune, or evaluate AI models.
• We do not run advertising, analytics, trackers, session recording, or behavioural profiling in the application.
• Our staff do not read your content. Access is restricted and audited.
• We do not use your data to build products for anyone else.

How long we keep things

On your device, until you delete it. Omega Ex does not delete your history on a timer unless you ask it to. You can set retention windows per category in Settings, Privacy, for your activity log, chats, memories, meetings, imported history, and dictation history. By default every category is set to keep forever, because deleting your data without being asked would be its own kind of failure. Anything past a window you set is removed automatically.

When you delete your account, deletion removes your owner-scoped rows from the active store handling the request, ends your sessions, and attempts to remove your library, document and image files. Your account record, including its email address, is kept and marked as deleted. The safety gate's separate log is not removed. File-removal failures, copies on other installations, exported copies, backups and content already sent to providers are outside this deletion's reach.

Forgetting one thing. Forget removes the selected memory and records its identifier and deletion time without its content. This record travels through sync to prevent the same memory row from being copied back. Any source chat you keep remains and can still be read. Omega Ex can learn the fact again from conversations you keep, and a memory the deleted entry replaced or absorbed can return.

Backups and provider copies. In-app deletion does not erase operational backups or content already sent to providers. We have not confirmed a maximum retention period for hosted backups. Provider copies follow the provider's retention terms, which can include safety and legal exceptions.

Anthropic's standard API retention. Anthropic's published policy deletes API inputs and outputs within 30 days, with exceptions for agreed terms, services with longer retention, safety enforcement and legal requirements. Content flagged as a Usage Policy violation may be kept for up to two years, and safety classification scores for up to seven years. We do not claim that zero data retention is enabled for Omega Ex's Anthropic organization.

Your controls

In the app, under Settings, Privacy:

• See who receives your data. Generated from your live settings.
• Turn voice and biometric features on or off. Off by default.
• Set retention windows per category, with a preview of what a change would remove.
• Export everything we hold as a single file.
• Delete your account and all of your data. The reach and limits of deletion are in Section 12. An account that uses company sign-in has no Omega Ex password, so it cannot use in-app deletion yet. To delete one, email us at [email protected]: we stop it signing in the same day and delete its data within 30 days.

You can also disconnect any connected account at any time, which revokes our access to it.

Your rights

Everyone. You may ask us for a copy of your data, to correct it, or to delete it. The fastest route is the in-app controls above, which are immediate, except that an account using company sign-in is deleted by email (Section 13). Otherwise write to [email protected] and we will respond within 30 days, or 45 where the law allows an extension.

California (CCPA/CPRA). You have the right to know, delete, correct, and opt out of sale or sharing. We do not sell or share personal information, so there is nothing to opt out of, but you may still exercise the other rights, and we will not discriminate against you for doing so. You may use an authorised agent with written authorisation. We honour Global Privacy Control signals on this website.

Illinois, Texas, and Washington. See Section 6 for our biometric policy, retention schedule, and destruction guidelines.

EU and UK. Omega Ex is offered to customers in the United States and is not marketed in the EU or UK. Our servers are in the United States. If you use the product from outside the United States, your data is transferred to and processed in the United States. Where GDPR applies to you, our lawful bases are performance of our contract with you (to run the product you asked for), consent (for biometric features), and our legitimate interests in keeping the service secure. You may object, restrict, port, or complain to your supervisory authority.

To verify a deletion request we confirm control of the account email, and for deletion we require the account password as a second factor, except on an account that uses company sign-in, which has none.

Security

• Current versions encrypt connected-account credentials and provider keys before saving them. Provider keys saved by older versions can still be stored unencrypted; current saves do not prove that all earlier rows have been migrated.
• Traffic to us and to providers uses TLS.
• Access to production is restricted, and administrative access is logged.
• Activity-log rows and messages can sync to the hosted store. A request made on the hosted workspace is handled there; mail content in its results or activity rows can therefore remain there too.

No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and any regulator required, without undue delay and within 72 hours of becoming aware where the law requires it.

To report a vulnerability, write to [email protected]. We will not pursue legal action against good-faith research that respects our published scope.

Children

Omega Ex is for adults. It is not directed to children, we do not knowingly collect information from anyone under 18, and you must be 18 or older to use it. If you believe a child has given us information, write to us and we will delete it.

This website

This site uses only the cookies needed to make it work. We do not run advertising or retargeting pixels. If we add an analytics tool we will say so here and, where required, ask first.

Changes

We post changes here with a new "Last updated" date and keep previous versions. Material changes take effect at least 30 days after notice by email and in the app. If a change adds access to Google data or changes how we use, retain or share it, we also ask you to agree in the app before the new access or use begins for your account. Declining or ignoring the request does not authorize it. No 30-day material-change notice is sent for the dated hosted mail and calendar pilot. For your account it starts only with your separate agreement in the app as you connect Google, then Google's consent, then our separate activation approval (see the dated hosted mail and calendar pilot in Section 9).

Contact

Omega Ex, Inc., 58336 Overseas Highway, Marathon, Florida 33050, United States.

• Privacy questions, requests, and complaints: [email protected]
• Security and vulnerability reports: [email protected]
• Telephone: 385-505-6179