Your device details. Clearer choices.
Core device readings and diagnostics are processed on your device. Advertising services and an optional public-IP lookup involve third parties. Reports are saved to a destination you choose.
1. Scope and release status
Owlsnowy (“we,” “us,” or “our”) is developing Device Dash, an Android device information and diagnostic app (the “App”). This policy describes the pre-release Android build reviewed on October 12, 2026. Device Dash is not yet publicly available on Google Play. We will update this policy to reflect the final release before launch.
The reviewed build uses Google test advertising units. It does not offer an Owlsnowy account system, cloud synchronization or in-app purchases. This policy does not describe an iOS edition of Device Dash. Website and email practices are covered by our Website Privacy Policy.
2. Device information
The App reads hardware and software information through Android APIs and available system sources to display device, chipset, CPU, GPU, memory, storage, battery, display, camera, sensor, thermal and connectivity information. Some values are unavailable or restricted depending on the device, Android version and permissions.
Device and network details may include model, manufacturer, Android version, build fingerprint, Android ID, network addresses, Wi-Fi information, operator information and installed-app details. On older Android versions, telephony features may access an IMEI or subscriber identifier where Android permits this and you grant the relevant permission. Restricted identifiers are not bypassed.
Installed-app and permission features inspect app names, package names, versions, permissions and component information on the device. Usage features can read screen-time and network-usage statistics when you enable the required special access. Sensor and supported heart-rate features read available sensor measurements when the necessary permissions are granted.
These features process their readings locally. We do not use the App's own code to upload your installed-app list, device reports, microphone recordings or local test results to an Owlsnowy server in this reviewed build. The third-party processing described below is separate.
3. Permissions and special access
The App requests permissions or access needed for the features you use. Android availability and wording vary. You can review permissions in Android Settings; denying a permission can limit the corresponding feature.
| Permission or access | Purpose |
|---|---|
| Camera | Camera and flashlight checks. |
| Microphone | Recording and playback during a microphone test. |
| Location and Wi-Fi state | Nearby Wi-Fi scanning where required by Android. These Wi-Fi features do not use GPS coordinates for an Owlsnowy location history. |
| Phone state | Telephony information and permitted older-Android mobile-data queries. |
| Bluetooth, motion and supported body sensors | Connectivity information and supported sensor checks or readings. |
| Biometrics | A system-managed authentication check. The App receives the result; it does not receive fingerprint templates. |
| Installed-app visibility and usage access | App information, permission inspection, screen-time and network-usage views. |
| Display over other apps, foreground service and notifications | An optional floating device monitor and its ongoing service notification. |
| Package deletion requests | Opening Android's confirmation flow when you choose to uninstall an app. |
| Network access, vibration, audio controls and boot events | Advertising and chosen online features, hardware tests, and widget updates. |
Usage access and overlay access are enabled separately in Android Settings. Access is not a guarantee that every reading will be available. Disable the floating monitor from its controls or revoke overlay access if you no longer want it.
4. Local data and reports
The App stores preferences, diagnostic results, widget settings and monitor configuration in local app storage. Cached chip metadata can also be stored locally. The reviewed build disables Android app-data backup in its application configuration.
Microphone tests create a temporary recording in the App's cache for local playback. The App attempts to remove that file when the test screen is paused or destroyed. An interrupted process may leave cache files until Android removes them or you clear the App's data. The App does not upload these test recordings.
When you choose to export a report, the App prepares a TXT or PDF file and writes it to a destination selected through Android's document picker. A temporary staging file is removed after the export attempt. Reports can contain device identifiers, installed-app names, network details and test results according to the categories you select. Review a report before sharing it.
If you choose a cloud-storage provider or later share an exported file, that destination or recipient processes the file under its own practices. Exported files are separate from the App's internal storage.
5. Advertising and privacy choices
The reviewed build integrates Google's Mobile Ads SDK for native and interstitial ads, and Google's User Messaging Platform (UMP) for advertising privacy messages. It currently uses Google test ad units. Test ads do not mean that no information is processed by Google.
When advertising services are allowed to run, the SDK can send your IP address, advertising or other device identifiers, app/ad interactions and technical performance information to Google and its advertising services. IP addresses may indicate approximate location. This processing supports ad delivery, measurement, diagnostics and fraud prevention. Personalization and identifiers depend on service configuration, applicable requirements and your choices.
Where required and configured, UMP provides a privacy message. Advertising privacy options are exposed in App Settings when UMP requires them. You can also use Android's advertising controls to reset or delete your advertising ID and review Google's advertising preferences. Limited or non-personalized ads can still involve data processing.
Google provides more detail in its Privacy Policy, information about apps that use Google services, and Mobile Ads data disclosures. No separate Firebase Analytics or Crashlytics integration is configured in the reviewed App source; advertising SDK processing still applies.
6. Optional online features
Public-IP lookup
If you select the public-IP lookup in the network view, the App requests information from api.seeip.org. That service receives your public IP address and request information and returns IP-related information such as organization, country and time zone. This lookup is triggered by your action; it is separate from local device readings. See the SeeIP service website. Skip this feature if you do not want to contact that service.
Chip information
The reviewed build uses a bundled chip catalog. Its optional remote chip endpoint is not configured, so no chip lookup is sent to an Owlsnowy server in this build. We will update this policy before enabling a remote service that changes these practices.
8. Retention and deletion
Local preferences, test results and configuration remain until reset, cleared or removed with the App. The Settings reset feature clears preferences and saved diagnostic results; it does not necessarily remove every widget, monitor or cache record.
Delete all internal App data
- Open Android Settings → Apps → Device Dash (or the app label used by your pre-release build).
- Select Storage or Storage & cache.
- Select Clear storage or Clear data and confirm.
Clearing cache alone does not remove all saved preferences and results. Uninstalling also removes internal app data, subject to Android or device-provider behavior. Owlsnowy cannot remotely erase your on-device files.
Exported reports and provider records
Delete exported reports separately in your chosen file or cloud-storage application. Clearing App data does not remove those files, copies sent to others or provider backups. It also does not automatically delete information already handled by Google or SeeIP. Use the relevant provider's controls and policies for its retained records.
Support correspondence is kept while needed to answer and resolve an inquiry, handle follow-up or disputes, or meet obligations, and is deleted when no longer needed for those purposes. You can contact us about information handled by Owlsnowy.
9. Your rights and choices
You can decline optional permissions, avoid online lookups, choose which report categories to export, manage advertising choices where available, and clear local data. These choices may affect related App features.
Depending on applicable law, you may have rights to access, correct, delete or receive a copy of personal information, restrict or object to processing, withdraw consent, or complain to a data-protection authority. Contact us for requests concerning Owlsnowy's handling of information. We may need enough information to identify a relevant record and verify the request. Do not send passwords or full payment details.
10. Security and children
Android's app sandbox protects internal app storage. Exports are protected by the destination you choose. Online requests in the reviewed source use HTTPS; Google states that its Mobile Ads data is encrypted in transit using TLS. No method provides absolute security. Keep your device and exported reports secure.
Device Dash is a general device utility and is not specifically designed for children. If you believe a child has provided personal information to Owlsnowy, contact us so we can investigate and take appropriate action.
11. Changes and contact
We will revise this page when App practices change, including when release advertising or online services are configured. The date and release scope above will be updated. Where required, significant changes will also be communicated in the App or through another appropriate notice.
Developer brand: Owlsnowy
App: Device Dash (Android pre-release)
Privacy and support: support@owlsnowy.com