Privacy Policy for OmniEye
Effective date: August 15, 2026
Last updated: August 26, 2026
App name: OmniEye
App Package: com.jimp.omnieye
Developer / Publisher: OmniEye (package com.jimp.omnieye)
Contact: apphelp2000@outlook.com
This Privacy Policy explains how OmniEye ("we," "us," or "the App") handles information when you use the Android application distributed on Google Play.
OmniEye is an offline app permission and resource inspector. It is designed around on-device analysis and local storage. We do not operate an OmniEye cloud account system, and we do not collect, upload, or store your audit lists, storage snapshots, permission reports, or usage-derived metrics on our servers.
The only third-party service we intentionally integrate for data-related purposes is Google Mobile Ads (AdMob) on Android (sponsored banner and, where configured, rewarded ads). That SDK may collect and process certain device and advertising-related data under Google's control, as described below.
By using OmniEye, you agree to this Privacy Policy. If you do not agree, please do not use the App.
1. WHO WE ARE
OmniEye (Android package com.jimp.omnieye) is published on Google Play. Contact: apphelp2000@outlook.com.
For privacy questions, email: apphelp2000@outlook.com
2. CORE PRIVACY PRINCIPLES
1. No OmniEye account — The App does not require email, phone number, or OmniEye registration to use audit features.
2. Local storage — Watchlists, storage snapshots, settings, and related audit data are stored on your device (for example, a local SQLite database and app storage).
3. No OmniEye audit backend — We do not run a server that receives, indexes, or retains your installed-app audit results for our own analytics or advertising.
4. Third-party ads exception — On Android, sponsored ads may be shown using the Google Mobile Ads SDK. Google (and its advertising partners) may collect data as described in Section 6. We do not send your audit reports, watchlists, or usage-derived metrics to the ad SDK for targeting.
5. Minimal permissions — OmniEye does not request MANAGE_EXTERNAL_STORAGE or READ_EXTERNAL_STORAGE. Storage insights use system APIs (such as StatFs and StorageStatsManager). Usage Access is requested only after prominent disclosure and is used for on-device calculations.
3. INFORMATION THE APP PROCESSES ON YOUR DEVICE
The following information is created and/or read locally on your device to provide the App's features. Unless otherwise stated, this information is not transmitted to OmniEye developer servers (we do not operate such audit servers).
Installed apps you choose to audit
- Examples: package name, app label, icon (where available), permissions declared/granted
- Purpose: build your audit list and permission review screens
- Shared with OmniEye servers: No
Usage / resource metrics (when Usage Access is granted)
- Examples: storage stats (app/data/cache), network traffic summaries, foreground/background activity signals, permission-use frequency, derived privacy/battery indices
- Purpose: rankings, detail screens, and local trend history
- Shared with OmniEye servers: No
Device storage overview
- Examples: used and total device storage from system file-system stats
- Purpose: dashboard storage overview
- Shared with OmniEye servers: No
Local history and settings
- Examples: daily storage snapshots, monitored-app list, preference flags (for example, background snapshot toggle state)
- Purpose: trends and continuity when you reopen the App
- Shared with OmniEye servers: No
Optional share exports
- Examples: a screenshot/image of an audit view you choose to share, plus a short caption you may post
- Purpose: user-initiated sharing via the Android share sheet or social intents
- Shared with OmniEye servers: No (shared only with the destination app/service you select)
Domains found inside audited apps (External domains & IPs module)
- Examples: domain names and IP addresses discovered in an app's APK, plus their DNS resolution status, RDAP registration details (registrar, creation/expiry), and optional port-probe reachability
- Purpose: show where an app's code may connect; lookups are on-demand and results are cached locally in the global domain knowledge base
- Shared with OmniEye servers: No (the queried domain names are sent to public DNS resolvers / registries only when you open this module; see Section 3.1)
Advertising identifiers (via Google Mobile Ads, when ads are shown)
- Examples: Advertising ID / App Set ID and related ad signals processed by Google
- Purpose: serve and measure sponsored ads
- Shared with OmniEye servers: No (processed by Google as described in Section 6)
3.1 Permissions
Depending on the Android version and features you use, the App may request or rely on permissions / special access such as:
- PACKAGE_USAGE_STATS (Usage Access) — Compute traffic, storage breakdown, permission-use frequency, and related rankings locally after you enable access in system settings. We show an in-app disclosure before directing you to Settings.
- QUERY_ALL_PACKAGES — List installed applications so you can add them to your audit watchlist (subject to Play policy for this permission).
- Internet / network access — Load sponsored ads (Google Mobile Ads) when configured; and perform on-demand lookups for the External domains & IPs module: DNS resolution of domains found inside an app's APK (via the system resolver), RDAP registration queries (via the IANA bootstrap file and the relevant TLD registry), and optional port probes against a domain's resolved IPs. These lookups are user-triggered, do not involve OmniEye servers, and their results are cached locally.
- AD_ID — Advertising ID access used by the Google Mobile Ads SDK for ad serving and measurement where applicable.
- Background fetch / task scheduling — Optionally write local storage snapshots on a periodic schedule so trends remain available when the App is not open.
We do not use these permissions to build a cloud profile of you on OmniEye servers.
3.2 What we do not request
OmniEye does not request broad external storage permissions such as MANAGE_EXTERNAL_STORAGE or READ_EXTERNAL_STORAGE for its audit features.
4. INFORMATION WE (THE DEVELOPER) COLLECT
We do not collect personal audit data, watchlists, storage snapshots, permission reports, or usage-derived metrics onto OmniEye developer servers.
We do not provide an OmniEye user account that syncs your history to the cloud. Therefore:
- We do not sell your audit data.
- We do not use your on-device audit results for advertising profiling on our side.
- We do not maintain a central database of your installed apps or usage history.
If you contact us by email for support, we will receive whatever information you voluntarily include in that email (for example, your email address and message text) and use it only to respond to your request.
5. CHILDREN'S PRIVACY
OmniEye is not directed at children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children onto our servers. If you believe a child has provided personal information to us via support email, contact us and we will delete that correspondence where applicable.
Note: Google Mobile Ads and Google Play have their own policies regarding ads and audiences. See Section 6.
6. THIRD-PARTY ADVERTISING — GOOGLE MOBILE ADS (ADMOB)
6.1 What we use
On Android, OmniEye may display a sponsored banner using the Google Mobile Ads SDK (via AdMob / Google advertising services). Where configured, the App may also offer rewarded ads (for example, to temporarily hide the banner). We do not use your audit content to personalize ads on our side. Current ad requests may request non-personalized ads only where the App configures that option.
6.2 What Google may collect
The Google Mobile Ads SDK may automatically collect and process certain information, which typically can include (subject to Google's product behavior, your device settings, region, and consent choices):
- IP address (which may be used to estimate general location)
- Device and advertising identifiers (such as Android Advertising ID / App Set ID)
- App interaction and ad interaction data (for example, ad views and clicks)
- Diagnostic / performance information related to the SDK and ads
Google may use this information for advertising, measurement, analytics, fraud prevention, and related purposes under Google's policies.
Important: This advertising-related collection is performed by Google and its partners, not by an OmniEye audit backend. We do not control Google's full data processing. We do not intentionally send your audit reports, watchlists, or local usage metrics to Google for ad targeting.
For Google's disclosures about data collected by the Mobile Ads SDK, see:
- Google Play data disclosure for Google Mobile Ads SDK:
https://developers.google.com/admob/android/privacy/play-data-disclosure
- Google Privacy Policy:
https://policies.google.com/privacy
- How Google uses information from sites or apps that use our services:
https://policies.google.com/technologies/partner-sites
6.3 Your choices for ads / advertising ID
You can limit personalized advertising and manage advertising identifiers through Android / Google settings, for example:
- Reset or delete your Advertising ID in Android settings
- Adjust ad personalization in your Google Account / Ads Settings:
https://adssettings.google.com
- Review Google's ad and activity controls:
https://myactivity.google.com
Availability of controls may vary by device, OS version, and region (including additional consent requirements in the EEA/UK/Switzerland where applicable).
6.4 Google Play Data safety
When completing the Play Console Data safety form:
- Treat OmniEye audit / watchlist / snapshot data as stored on-device / not collected by the developer to a server; and
- Treat Google Mobile Ads SDK data as data that may be collected and shared by a third party (Google) for advertising and related purposes, consistent with Google's published SDK disclosure guidance.
You (the developer) remain responsible for ensuring the Data safety answers match the App's actual configuration.
7. DATA SHARING
Apps / services you choose when sharing
- What may be shared: audit screenshot and caption you initiate
- Why: user-initiated share
Google (Mobile Ads SDK)
- What may be shared: advertising, device, and diagnostic data as collected by the SDK
- Why: show sponsored ads; ad measurement; fraud prevention
Public DNS resolvers / domain registries (when you open the External domains & IPs module)
- What may be shared: the domain names found in an audited app's APK (queried on demand)
- Why: DNS resolution and RDAP registration lookups; results are cached locally and not shared with OmniEye servers
OmniEye developer servers
- What may be shared: none for audit/watchlist data (no audit cloud)
- Why: not applicable
Law enforcement
- What may be shared: only if legally required regarding information we actually hold (for example, support emails)
- Why: legal compliance
We do not sell your personal information.
8. DATA RETENTION
- On-device app data is retained on your device until you delete it within the App (for example, remove an audited app), clear app storage, or uninstall the App.
- Support emails you send us are retained only as long as needed to handle your request, then deleted or minimized in ordinary course.
- Google Ads data is retained according to Google's retention practices, which we do not control. See Google's Privacy Policy.
9. SECURITY
We design OmniEye so that audit data remains on your device in local app storage. Sensitive system stats are read only after you grant Usage Access through Android settings.
No method of electronic storage is 100% secure. You are responsible for the physical security of your device and for screenshots or reports you choose to share.
10. INTERNATIONAL USERS
The App stores primary audit data on your device. If you use Google advertising services, Google may process data in locations where Google operates. See Google's Privacy Policy for details.
11. YOUR RIGHTS
Depending on your jurisdiction (for example GDPR, UK GDPR, CCPA/CPRA), you may have rights to access, delete, or restrict certain personal data.
Because OmniEye does not keep your audit data on our servers:
- Deleting app data we hold on servers: generally not applicable for audit content (we do not host it).
- Deleting on-device data: uninstall the App or clear the App's storage (see our Data Deletion instructions).
- Advertising data held by Google: use Google's tools and settings described in Section 6.3, or contact Google as described in Google's Privacy Policy.
To exercise rights regarding information you emailed to us, contact apphelp2000@outlook.com.
12. CHANGES TO THIS POLICY
We may update this Privacy Policy from time to time. The "Last updated" date at the top will change when we do. Continued use of the App after an update means you accept the revised policy, to the extent permitted by law.
13. CONTACT
App: OmniEye
Email: apphelp2000@outlook.com
Developer / Publisher: OmniEye (package com.jimp.omnieye)