Privacy Policy

Effective 1 September 2026. This policy describes the current OmniIntel application.

1. Who operates OmniIntel

OmniIntel is a private intelligence workspace operated under the OmniIntel identity. There is no separate legal entity name published in this application. Privacy and support contact: omniintel@eproz.business.

2. Information users provide

Depending on role, users may provide:

Email address used to sign in or receive an invitation.
Username, display name and workspace preferences.
Password, or use of a magic-link sign-in sent to that email.
Followed topics, watchlists, saved items and similar product choices stored in the workspace.

3. Account and authentication information

Sign-in is handled by Supabase Auth. OmniIntel stores session state in cookies, membership and role in the workspace database, and optional profile fields such as username and appearance. Authentication email is sent using the configured OmniIntel sender omniintel@eproz.business.

4. Google account information

If an authorized administrator connects Gmail, OmniIntel receives from Google the mailbox email address, the Google account identifier (subject), granted OAuth scopes, and OAuth tokens needed to keep the connection working. That identity is stored on the workspace Gmail connection record. Product readers do not see the raw mailbox address; Admin masks it.

5. Gmail data accessed

OmniIntel currently requests the Google scope https://www.googleapis.com/auth/gmail.readonly, which is read-only Gmail access. In operation OmniIntel may:

Read the Gmail profile used to identify the mailbox and sync cursor.
List labels and resolve the configured newsletter label.
List or incrementally watch messages that carry that label, including mail that is already read or archived, because the label is the ingestion boundary — not inbox or unread state.
Download the complete MIME of those labeled messages.

OmniIntel does not request a Gmail send scope and does not use Gmail access to send mail.

6. Why Gmail data is accessed

Gmail is used only so newsletters that arrive in the connected mailbox can be ingested into the OmniIntel intelligence corpus when they carry the configured newsletter label (default OmniIntel/Newsletters). That is the newsletter-ingestion workflow. Gmail is not used to provide a general personal inbox, advertising, or unrelated mailbox search.

7. How Gmail data is processed

A scheduled or manual sync authenticates with the stored tokens, finds labeled message IDs, claims each message once, downloads MIME, parses the issue, classifies it, and extracts candidate stories (titles, links, publishers). Direct publisher feeds are a separate path and do not use the Gmail API. Historical import is an administrator-triggered backfill of labeled mail; it is not the same as the recurring incremental sync.

8. What Gmail-derived information may be stored

OmniIntel may store:

OAuth credentials: refresh and access tokens as encrypted ciphertext, expiry, key version, and granted scopes.
Connection metadata: mailbox email, Google account subject, label name and id, sync timestamps and error summaries.
Sync cursors such as Gmail history identifiers, so later runs can proceed incrementally.
Ingestion records: Gmail message identifiers, sender fields, subject material used for processing, dates, and processing status.
Message payloads: raw MIME and HTML/text bodies, retained so a later parser change can reprocess without calling Gmail again.
Extracted intelligence: candidate stories, publisher records, and related feed discovery derived from those messages, which authorized workspace members may then read in the product.
Operational logs of sync and processing runs, including error text.

The customer product does not expose raw Gmail addresses, Gmail message ids, raw subjects, OAuth tokens, or raw MIME. Those remain in internal tables used to operate ingestion.

9. Data retention

Encrypted Gmail tokens are kept while the mailbox stays connected. Extracted intelligence is kept as the workspace corpus; it is not age-purged by a running job. Raw newsletter payloads are retained for reprocessing; the documented retention rules for payloads are currently disabled, so those bytes are not automatically cleared. Some operational and diagnostic records are described by an internal retention policy, but no automatic deleter is wired to that policy today.

10. Data deletion

Disconnecting Gmail from Admin → Gmail sets the connection to disconnected and deletes stored refresh and access tokens so API access stops. Disconnect does not by itself delete previously stored payloads or extracted intelligence, so reconnecting the same mailbox does not force a full re-download of already claimed messages. To request deletion of stored Gmail-derived records or an account, contact omniintel@eproz.business.

Google user data is not sold and is not used for advertising. OmniIntel does not share Gmail content with other workspace customers. Data is processed by infrastructure OmniIntel already uses to run the application (see third-party providers below). Authorized workspace administrators can see operational Gmail connection status and ingestion diagnostics needed to run the service.

12. AI processing

OmniIntel includes optional entity-synthesis features that, when enabled and when a permitted user requests them, may send selected text from the intelligence corpus — including stories that originally came from newsletters — to configured model providers (currently OpenAI and Google Gemini). OmniIntel does not send raw Gmail MIME or OAuth tokens to those providers. Those features are not on by default for every account; they require configuration and access. Unreleased products are not described here.

13. Security

Gmail OAuth tokens are encrypted with AES-256-GCM before storage. The encryption key is held in server environment configuration, not in the database. Application tables that hold tokens and payloads are protected so ordinary signed-in roles cannot read them through the database API. Privileged server access is required to run ingestion. Outbound fetches of publisher URLs go through a guarded HTTP client that refuses private network targets.

14. User controls and revocation

An authorized administrator can:

Connect Gmail explicitly via Google's consent screen.
Disconnect Gmail in Admin → Gmail, which removes stored tokens.
Revoke OmniIntel access from the Google Account permissions page, which will cause later token refresh to fail until the mailbox is connected again.

Invited members can sign out. Account and access changes for the workspace are handled by administrators; contact omniintel@eproz.business for help.

15. Cookies and session information

OmniIntel uses cookies to keep a signed-in Auth session. During Gmail connect, a short-lived httpOnly cookie holds the OAuth state value to prevent CSRF. Appearance preferences may be stored on the account. Public pages do not require cookies to display this policy.

16. Third-party service providers

Supabase — authentication and the application database.
Google — OAuth, Gmail API, and optional Gemini model calls.
OpenAI — optional model calls when entity synthesis is used.

Hosting of this application is the environment where OmniIntel is deployed. Those providers process data as needed to provide the service.

17. Google API Services User Data Policy

OmniIntel's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Gmail data is used to provide the newsletter-ingestion features the connecting administrator enables, not to serve ads, and not to train generalized models unrelated to that service.

18. Changes to this policy

If this policy changes, the updated text will be published at this URL. Material changes to how Google user data is used will be reflected here before those changes are relied on.

19. Contact

Privacy questions: omniintel@eproz.business. See also the About page and Terms of Service.