This Privacy Policy explains how OmniCode ("OmniCode," "we," "us," or "our") handles information. OmniCode is an AI-powered development and productivity application for macOS. OmniCore Technologies is a project and brand name, not a registered legal entity. References to “the developer of OmniCode” mean the individual developer responsible for the application.
1. Information processed by OmniCode
OmniCode processes information only when you use a feature that needs it. Depending on your choices, this can include prompts and messages, source code, project files, terminal output, documents and attachments, browser page content, voice transcripts, application preferences, and data retrieved from a service you explicitly connect.
The audited application contains no advertising SDK, third-party analytics SDK, tracking pixel, or OmniCode-operated cloud backend for user content. Network requests go directly from your Mac to the provider needed for the feature: for example Google APIs, your selected AI provider, a website you ask the managed browser to access, or a local service such as Ollama.
2. Source code, projects, files, and terminal access
Code Mode can read and modify files and folders that you open or authorize, including source code, configuration, documentation, Git repositories, build output, and files needed for a development task. Terminal features can run commands in the selected workspace and provide relevant command output to the active AI model when needed for your request.
Files outside the current workspace require a user-selected location or an applicable OmniCode and macOS permission. You are responsible for reviewing important changes and keeping appropriate backups.
3. Google Account and Google Workspace data
Gmail, Google Drive, and Google Calendar are optional. OmniCode accesses Google Account information only after you start Google OAuth in the application and authorize the requested services. Authorization occurs on Google’s website. OmniCode does not ask for or receive your Google password.
Basic OpenID identity permission provides your Google account identifier and email address so OmniCode can verify and show which account is connected. OmniCode does not request the Google profile scope. Gmail, Drive, and Calendar permissions are requested incrementally when you connect each feature. Google's Data Access verification is pending; authorization may show an unverified-app warning, be subject to Google's user cap, or be blocked by account or organization policy.
Gmail
If you authorize Gmail, OmniCode uses the https://www.googleapis.com/auth/gmail.modify scope. Depending on the feature you request, it may access message metadata, subjects, sender and recipient information, email bodies, threads, attachments, drafts, labels, and read or unread state.
That information is used for user-requested features such as searching and reading email, summarizing relevant content, working with attachments, creating drafts, sending or replying after the applicable approval, changing read state, archiving, and updating labels. OmniCode retrieves the relevant search result, message, thread, or attachment; it does not send an unrelated inbox to an AI provider.
Google Drive
If you authorize Google Drive, OmniCode uses the https://www.googleapis.com/auth/drive scope. Depending on the feature you request, it may access file names, metadata, folders, file contents, exported Google Workspace documents, and uploads or downloads.
That information is used for user-requested features such as finding files anywhere in Drive, reading supported documents, summarizing a selected document, transferring an attachment, creating folders or files, uploading, downloading, renaming, moving, copying, trashing, or restoring supported items. Search runs before content retrieval, so a request such as “find my resume” does not send the contents of the whole Drive to an AI provider.
Google Calendar
If you authorize Calendar read access, OmniCode requests calendar.calendarlist.readonly, calendar.events.readonly, and calendar.events.freebusy Google API scopes. It may read calendar names, event details, attendees, locations, descriptions, and availability needed for your request. A separate calendar.events grant enables user-directed event creation, editing, and deletion. Calendar writes remain subject to OmniCode's action approvals; authorizing Calendar does not automatically authorize unrelated Google services.
GitHub and MCP servers
If you connect GitHub, OmniCode can access repositories you select for its GitHub App, including code, issue and pull-request content, and Actions information. Authorized writes can create or change issues and pull requests with OmniCode's normal action approvals. GitHub access is subject to the account and repository permissions you grant.
If you explicitly configure an MCP server, OmniCode may send your tool arguments to that server and receive its tool results, resources, or prompts. A local server runs with your macOS user permissions; a remote server processes information according to its operator's policies. Newly discovered tools are disabled until enabled by you. MCP credentials are stored separately in macOS Keychain; OmniCode does not copy Google or GitHub connector tokens into MCP settings.
4. Google data use and Limited Use
OmniCode uses Google user data only to provide or improve the user-facing feature that you request. OmniCode does not sell Google user data, use Google user data for advertising, or use Google user data for credit or lending decisions. OmniCode does not use Google user data to train or improve a generalized AI model.
The application applies a trusted main-process provider policy before Google Workspace tools can run. If the selected provider configuration is not approved for Google Workspace content, the transfer is blocked and the application explains that you must select a compatible provider. When a compatible provider is selected, OmniCode sends only the context required for the request.
5. AI providers and Google Workspace data
You choose the AI provider and model. When a cloud provider is selected, your prompt and the minimum relevant context can be transmitted directly from your Mac to that provider. OmniCode shows whether the selected route is local, cloud, or blocked for Google Workspace data.
| Selected route | Google Workspace data | Provider handling used by OmniCode |
|---|---|---|
| Ollama local model | Allowed when the model is served locally | Inference happens on the Mac. OmniCode does not create provider-side prompt storage. Google API traffic still communicates with Google, so the overall workflow is not offline. |
| OpenAI API | Allowed for minimum task context | OmniCode uses the API Chat Completions endpoint with store=false. OpenAI states API data is not used for training by default. Default abuse-monitoring logs may be retained for up to 30 days; eligible account controls can differ. |
| Anthropic API | Allowed for minimum task context | OmniCode uses Anthropic’s commercial Messages API. Anthropic states commercial/API data is not used for generative-model training by default and is automatically deleted within 30 days by default, subject to its stated safety, legal, feedback, and agreement exceptions. |
| Gemini Developer API | Blocked | Paid and unpaid Gemini API services have different data-use terms, and OmniCode cannot verify the billing tier from an API key. Google Workspace tools are therefore unavailable on this route. |
| Ollama cloud model | Blocked | An Ollama model identified as cloud-hosted is not treated as local inference. Google Workspace tools are unavailable because OmniCode does not verify that hosted configuration. |
Provider terms and account settings can change. The current classifications were last reviewed on September 23, 2026 against the providers’ published documentation. Relevant sources include OpenAI API data controls, Anthropic training practices, Anthropic retention, Gemini billing and data use, Gemini data logging and retention, and Ollama privacy information.
6. Credentials and authentication tokens
Google and GitHub access credentials, MCP server credentials, and API keys for supported AI providers are stored in macOS Keychain under the current macOS user. OmniCode does not intentionally store these credentials in project files, preferences, browser local storage, or diagnostic logs.
Credential-like values are redacted from normal diagnostic and tool-result paths. No security control can guarantee absolute protection.
7. Voice and speech
Omni listens only after you activate voice input using the microphone button or global shortcut. The current build does not include an always-listening wake-word service.
On supported Macs, the native speech helper requires Apple’s on-device speech recognition. It receives microphone frames while listening and returns text transcript events. OmniCode does not write voice audio to a file and does not send that audio to an AI provider for speech recognition. If on-device recognition is unavailable, voice input is unavailable rather than silently switching to cloud recognition.
A transcript that you submit becomes message text. It may be retained in the applicable local conversation or task history and sent to the AI provider you selected.
Spoken responses use an installed macOS voice by default. If you explicitly connect and select ElevenLabs, OmniCode sends the prepared response text and selected voice/model settings to ElevenLabs for synthesis; its API credential is stored in macOS Keychain. ElevenLabs may charge for usage. OmniCode does not silently switch from local speech to ElevenLabs.
8. Cursor Mode, macOS permissions, and browser interaction
Cursor Mode uses macOS Accessibility permission to inspect structured information about supported interface elements and to perform approved clicks, typing, menu selection, scrolling, and other interactions. The audited build does not capture, store, or send screenshots for Cursor Mode. It does not require Screen Recording permission for this behavior.
Other features can request microphone, speech recognition, notification, file-and-folder, app-automation, or launch-at-login permission when applicable. macOS controls these permissions, and you can change them in System Settings.
The managed browser can process URLs, visible page text, and user-requested form information. Relevant page text can be sent to the selected AI provider to complete your request. Its isolated browser partition is memory-only; cookies, cache, and site storage from that managed session are not intentionally kept after the app session ends.
9. Local storage and retention
- Work conversations: user and assistant messages, attachment metadata, assistant summaries, and bounded connector result cards are stored in a permission-restricted local file until you delete the message or conversation. Result cards can contain limited fields such as an email subject, Drive filename, calendar event title, or repository name; they do not store raw tokens, binary bytes, or full raw connector responses.
- Imported Work attachments: selected text and source files are copied to permission-restricted local storage. They are removed when explicitly removed or when their last owning message or conversation is deleted. Orphaned copies are pruned at startup.
- Temporary Gmail and Drive transfers: downloaded attachment or file bytes use a permission-restricted transfer directory. They are deleted after a successful save, email attachment use, or Drive upload; otherwise they expire within one hour and are cleared at normal shutdown or pruned at startup.
- Temporary AI context: connector results used during a request exist in process memory and the provider request. OmniCode does not keep a separate raw AI-context cache. Conversation messages, summaries, and bounded result cards can remain as described above.
- Work activity: a bounded local action history of up to 500 entries remains until you clear it. It records action metadata and concise results, not OAuth tokens.
- Omni activity: task history is local and uses the retention period selected in Settings: off, 7, 30, 60, or 90 days. The default is 30 days. Clearing history removes completed entries.
- Code-agent activity: bounded local task summaries remain until cleared. Active terminal sessions and most transient command output are held for the session; relevant summaries or model messages can remain in task history.
- Voice and screenshots: microphone audio and screenshots are not written to local history by the current implementation. Submitted transcripts can remain as messages or tasks.
- Diagnostics: redacted lifecycle and error diagnostics are stored locally in a rotating log limited to approximately 512 KB plus one backup. They are not automatically sent to the developer.
- User-saved files: a Gmail attachment or Drive file saved to a location you choose remains there until you delete it.
Cloud-provider retention is governed by the provider route described above and by your provider account or agreement.
10. Disconnecting Google
When you choose Disconnect Google, OmniCode stops using the stored authorization, clears the in-memory access path used by Gmail, Drive, and Calendar, attempts to revoke the token with Google, deletes the local Google token record from macOS Keychain even if the revocation request cannot reach Google, resets the Google connectors, and displays them as not connected.
Disconnecting does not erase previously saved Work messages, assistant summaries, bounded result cards, or files that you deliberately saved. Remove those separately using conversation, activity, attachment, and file controls. You can also review or revoke OmniCode from your Google Account security settings.
11. Data disclosure
OmniCode does not sell personal information. Information is disclosed only to a service needed for a feature you choose, as described in this policy; when required to comply with applicable law; or to protect users, the application, or the public where legally permitted. No advertising disclosure occurs.
12. Your choices and controls
You choose whether to connect Google, which AI provider and model to configure, which local folders to open, which macOS permissions to grant, and which supported actions to approve. You can disconnect Google, remove provider credentials, delete Work conversations and attachments, clear activity histories, change Omni activity retention, and revoke macOS permissions.
13. Children
OmniCode is a general-purpose development and productivity application and is not specifically directed to children. Users must follow applicable law and the age and account requirements of any connected service.
14. Changes to this policy
We may update this policy when OmniCode’s features, provider rules, or data practices change. The publication date at the top will be updated when a revised policy is posted.
15. Contact
Questions or privacy requests can be sent to [email protected].