Privacy Policy
Last updated: November 2, 2026
At Omni Ecosystem, privacy is treated as a core product principle. Many Omni experiences are designed to minimize unnecessary data collection and to give users transparency into when information leaves their device.
1. Introduction
This Privacy Policy explains how Omni Ecosystem ("Omni", "we", "our", or "us") handles information across our products and services, including OmniAsk and related ecosystem applications.
Several Omni products are built with local-first or offline-first principles. However, certain connected experiences may require limited information to be transmitted securely over the internet in order to provide AI responses, synchronization, cloud functionality, analytics, or integrations with third-party services.
Whenever possible, we aim to clearly communicate when information is being shared outside your device and why that transfer is necessary for the requested feature.
2. Information We Do Not Collect
We do not sell personal information. We also do not collect unnecessary personal data from users simply for browsing our websites or using offline-capable experiences.
Certain Omni applications may function entirely on-device and may not require account creation, cloud synchronization, or persistent personal identifiers.
3. Information We May Collect
Some features may require limited data processing to operate correctly. Depending on the service you use, this may include prompts submitted to AI systems, account information, device diagnostics, usage analytics, or synchronization data.
We collect only the information reasonably necessary to operate, secure, improve, and maintain our services.
4. Permissions
Omni applications may request access to device capabilities such as microphones, cameras, local storage, or notifications when required for specific features. These permissions are used solely to support requested functionality.
For example, voice-enabled experiences may request microphone access in order to process speech input.
OmniAsk notification context on Android
Notification access is required for OmniAsk’s Android digital-context experience. At first connection, context covers all apps, including future apps. After authorization, OmniAsk captures notification content Android makes available, including text, app and sender information, timestamps, message sequences, available notification images, progress and action descriptions. This can include personal, financial and other sensitive information. Capture continues through the native notification listener independently of the model download and open Flutter screens, subject to Android delivery and background restrictions.
Captured content is stored in a local database on your device and processed by local models. It is not uploaded to our AI servers, purchase services or analytics as notification content. Brief preparation can run while OmniAsk is open or through background work when local models, configured rules and Android execution conditions permit. New notifications do not each require an inference: collection windows, priorities and schedules determine when eligible work is prepared. Background execution is subject to device resources and Android restrictions. Agent can add tools and suggested actions; a prepared suggestion is not an executed action. Android permissions and the originating app determine which actions remain available.
Captured history is retained for up to 30 days and 10,000 snapshots, with cleanup when capture or history access next runs. Large content and images have resource limits. Notification delivery may have gaps, and this does not provide access to an app’s complete private inbox. Browse captured history in Knowledge → Notifications; manage capture and history deletion through its capture settings or User → Preferences → Connected apps. Disabling capture or revoking Android access stops new collection and returns Android setup to its context step. Saved conversations and prepared workflow results have separate lifetimes and may retain context after captured history is cleared; deleting the source history does not erase those copies.
Local processing does not mean every OmniAsk service is offline. Account sign-in, purchase verification and screen-impression measurement use their respective service providers and app-user identifiers. Downloads require a model source connection. Actions you request may send information to another app or network destination. These service flows are separate from local notification capture.
5. Third-Party Services and Links
Our websites and applications may integrate with or link to third-party services. Omni Ecosystem does not control the privacy practices of external platforms, websites, or providers, and we encourage users to review their respective privacy policies.
6. Account Deletion
Users who created an account on OmniAsk may request deletion of their account and associated data at any time.
To request account deletion, users may contact us directly at support@omniecosystem.xyz. Requests should include the email address associated with the account to help us process the deletion securely and efficiently.
Some limited information may be retained where necessary for legal compliance, fraud prevention, dispute resolution, security, or enforcement of our terms.
7. Changes to This Policy
We may revise this Privacy Policy from time to time as our services evolve. Updated versions will be published on this page with a revised effective date.
8. Contact Us
Questions, concerns, or privacy requests can be directed to support@omniecosystem.xyz.