Privacy Policy
This policy covers omega2ai.com, contact with Omega AI LLC, and Sign in with Google / Google Workspace used by the Omega 3.0 runtime.
1. Who we are
Omega AI LLC builds autonomous AI systems. Omega 3.0 is a local-first metacognitive runtime. Contact: noahlee@omega2ai.com.
2. Website and direct contact
On this website we only process information you voluntarily send (for example via email or a contact form): name, email, company, and project description. We do not sell personal data. We do not use advertising cookies or third-party ad trackers on omega2ai.com for this purpose.
Contact submissions may be retained up to 24 months for business development. You may request deletion by emailing noahlee@omega2ai.com.
Project-inquiry forms are processed by Netlify on Omega AI LLC's behalf so the submission can be delivered to our company contacts. Netlify may process the fields you submit and technical request data as described in its own privacy documentation.
3. Google Sign-In and Google Workspace (Omega 3.0)
When you use Sign in with Google from an Omega 3.0 installation, Omega requests only the OAuth scopes required for the product ceiling:
- OpenID identity (
openid,email) - Gmail (
gmail.modify) — read and bounded changes; no permanent-delete scope - Calendar, Tasks, and Drive — as enabled in your connection settings
What Omega stores, and where
| Data | Storage |
|---|---|
| Google OAuth client secret (owner-configured once) | AES-256-GCM connector vault on the Omega host |
| Refresh / access tokens | AES-256-GCM connector vault, bound to your connection passphrase |
| Connection contract (capabilities, authority, retention) | Local guardian state — configuration only, no message bodies |
| Raw Workspace observations on intake | Local SourceLedger (plaintext before Guardian screening) |
| Derived memory after screening | Local Omega memory (episode SRAM → DeepSleep → filesystem/graph) |
| Action / sync operational state | Local ledgers: IDs, revisions, cursors, counts, digests — not Workspace payload content |
Google Workspace payloads and secrets are not placed in application logs, test output, Git, provider cursor state, or HUD progress labels.
How Omega uses Workspace data
- Ingest selected mail, calendar, tasks, and files into local memory.
- Align standing work after you approve a package.
- Act only inside the connection contract and, for autonomous standing work, an exact approved grant. Send-class Gmail operations require send authority and revision-bound approval when configured that way.
Omega does not sell Workspace data or use it to advertise to third parties.
Sharing
Omega does not transmit your Workspace content to Google beyond the API calls you authorize, and does not share that content with other product vendors as part of this connection.
Retention and deletion
- Retention follows the connection contract you set in Omega.
- Disconnect revokes Omega’s Google authority, then clears local credentials and connector state according to that contract.
- You can also remove Omega from Google Account → Connections.
4. Children
Omega’s Google Workspace integration is not directed at children under 13 (or the equivalent minimum age in your jurisdiction).
5. Contact
Privacy questions: noahlee@omega2ai.com · https://omega2ai.com/