This Privacy Policy explains how Inware handles information when you use the Android app. Dylan Roussel is responsible for Inware and the processing described here.
Inware is a device-information app. Information read from your device to display its hardware, software, sensors, and system status is processed locally and is not uploaded by Inware unless you explicitly share it.
Inware stores your settings, including data-sharing choices, on your device. Android may include these settings in cloud backup or device transfer according to your system backup settings.
Inware also keeps a rolling technical log of up to 64 KB on your device. It leaves your device only if you export or share it, or when eligible log entries are attached to a crash report you chose to send.
Some device details require Android permissions, including nearby-device or location permissions. Information read with these permissions is used to display device details locally.
On supported Android versions, Inware may expose selected public device facts through Android App Functions when the feature is available and enabled.
A compatible system service or app may request one of these facts. The requesting service's privacy policy governs any processing after Inware returns the requested value.
Starting with Inware 7.1.0, optional data sharing is divided into Usage analytics and Send crash reports. You can choose either, both, or neither.
These choices are off until a new user saves them. If you previously enabled analytics, Inware keeps that choice for Usage analytics when you upgrade and asks you to review the new controls.
Earlier versions did not provide a separate crash-reporting choice. Starting with Inware 7.1.0, crash report uploads require a separate opt-in.
If enabled, Inware uses Google Analytics for Firebase to understand which screens and features are used and to record app sessions and lifecycle events.
Inware records screen names, changes to Developer options, and developer feature-flag overrides. It does not set a Firebase user ID or attach your name, email address, or account details.
Analytics assigns an app-instance ID and may process app and device information, session statistics, and approximate location derived from a masked IP address.
Inware removes advertising-ID permissions and always denies advertising storage, ad user data, and ad personalization consent.
Performance Monitoring is controlled by the Usage analytics choice. It helps identify slow startup, rendering, and network operations and guide performance improvements.
Firebase may process timings, CPU and memory use, app state, app and device metadata, network type, response codes, payload sizes, and request URLs without query parameters or payload contents.
Firebase also processes a Firebase installation ID and an IP address. The IP address is used to derive the country where a performance event originated.
If enabled, Inware sends crash reports to Firebase Crashlytics so crashes can be identified, investigated, and fixed.
Reports may include stack traces, exception messages, timestamps, app and operating-system versions, device model and architecture, memory and disk information, app state, and installation or session identifiers.
Reports may also contain recent technical logs generated by Inware. These logs describe app state and navigation and are not intentionally used to collect personal content.
Crashlytics automatic upload is disabled. When crash reporting is off, Crashlytics may temporarily keep a report on your device, but Inware asks it to delete unsent reports when these controls next initialize, usually on the next launch.
Inware uses Firebase Remote Config even when optional data sharing is off. It supplies configuration needed to control app features without requiring a new app release.
Remote Config may process country, language, time zone, Android version, app version, package name, Firebase App ID, and Remote Config SDK version.
Remote Config uses Firebase Installations. Firebase creates a per-installation ID and receives basic app and device metadata. The ID identifies an installation, not a person or the physical device itself.
Essential configuration data is used to provide and safely control Inware features. Optional data is used only for usage analysis, performance improvement, and crash investigation.
I do not sell this information or use it for advertising. Google processes it as the provider of Firebase and Google Analytics, including through subprocessors used to operate those services.
Firebase processes data on Google's global infrastructure. Firebase states that data is encrypted in transit, and Crashlytics and Performance Monitoring data is also encrypted at rest.
Firebase states that Crashlytics generally keeps crash data and associated identifiers for 90 days before deletion begins.
Firebase states that Performance Monitoring keeps IP-associated events for 30 days and installation-associated or de-identified performance data for 60 days before deletion begins.
Google Analytics data is retained according to the retention settings and policies of the linked Analytics property.
You can disable either optional choice at any time in Data & privacy. Disabling a choice stops the corresponding future collection from Inware, subject to data already queued or received by Google.
Reset app identity clears Analytics data stored on your device, resets the Analytics app-instance ID, and requests deletion of the current Firebase installation.
Firebase states that data tied to the deleted installation is removed from live and backup systems within 180 days. Remote Config will later create a new, unrelated installation ID.
Reset app identity does not delete Analytics or crash data already stored on Google's servers. Inware has no accounts and sets no user ID, so I generally cannot identify a specific person's historical records.
Optional analytics, performance monitoring, and crash-report uploads are based on your consent. You may withdraw consent at any time without affecting processing that occurred before withdrawal.
Essential Remote Config and installation processing is based on the legitimate interest in operating, configuring, and protecting Inware.
Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing, and to receive portable data. You may contact me to exercise these rights.
Because Inware does not use accounts or set a user ID, I cannot identify Firebase records from your name or email address alone. I can only provide or delete records if you supply an identifier that can be used to locate them.
If no such identifier is provided, the relevant Firebase records cannot be located.
If you are in the European Economic Area, you may also lodge a complaint with your local data-protection authority or with France's CNIL.
Inware may link to external sites that I do not operate. Their content and privacy practices are governed by their own policies.
If you contact me, I receive the address and contents you provide. I use them to respond, handle your request, and maintain necessary records, and retain them only as long as reasonably needed.
I use reasonable measures to limit optional collection and protect data, but no transmission or storage method is completely secure.
Inware is not directed to children under 13, and I do not knowingly collect personal information from children. Contact me if you believe a child has provided personal information through Inware.
I may update this policy when Inware's features or service providers change. The revised policy will be posted on this page with a new effective date, and material changes may also be shown in the app.
Effective for Inware 7.1.0 from 7 September 2026.
Previous version: Privacy Policy effective May 2, 2022.
For privacy questions or requests, contact Dylan Roussel at mail@evowizz.dev.