Reniic Device Diagnostics Privacy Policy

1. Overview

Reniic Device Diagnostics (RENIIC) is a device diagnostic and inspection utility. This policy explains how the app handles information during tests, in saved reports and when you choose to share a report.

RENIIC requires no Reniic account. Device diagnostics, report history and temporary test media are processed locally and are not automatically transmitted to Reniic or a remote diagnostic server. The app includes Internet access for Google Play Billing and supporting Google components used to retrieve products, process or restore purchases, and verify RENIIC Pro ownership. Diagnostic results and reports are not sent through the billing connection. RENIIC includes no advertising, behavioral analytics or cloud crash-reporting service. Information can also leave your device when you deliberately share an exported report using another app or service.

2. Information and device capabilities the app accesses

RENIIC uses public Android APIs to examine device capabilities and run tests you choose. Depending on the test and Android version, it may request camera, microphone, location or Nearby devices permission. You can decline permissions or change them in Android Settings; affected tests may then be unavailable or incomplete. Denying permission is not evidence of faulty hardware.

Other diagnostic access includes Wi-Fi and network state, NFC, vibration, sensors, display and touch input, buttons, battery, charging, memory, storage capacity and Android biometric APIs. The app does not require root access or manufacturer secret diagnostic codes. Permission access and diagnostic evidence are described below.

3. Camera testing

Camera permission allows a live preview and temporary still captures so you can inspect image quality. Camera characteristics, capture success and your assessment can become diagnostic evidence. Captured photos are stored in app-private temporary cache storage, not your photo library.

The app deletes captures when they are replaced, accepted and no longer needed, explicitly deleted, or the test is finished or left. Recovery after an interruption is explained in section 11. Test photos and their private file paths are not included in saved reports, exported PDFs or report QR payloads, and are not automatically uploaded.

4. Microphone testing

Microphone permission allows a short test recording for playback and your assessment. The app processes audio locally and temporarily stores the recording in app-private cache storage. It retains diagnostic measurements such as recording duration, signal levels, clipping and audio-route information, together with your observation; it does not create a speech transcript.

Temporary audio is deleted when replaced, when no longer needed, or when you finish or leave the test. Interruption recovery is described in section 11. Test recordings and their private file paths are not included in saved reports, PDFs or report QR payloads, and are not automatically uploaded.

5. Location and GPS diagnostics

The location diagnostic may access precise or approximate location, depending on your permission choice and available providers, to check whether Android can obtain a fix. Android may deliver a location object containing coordinates during this test. RENIIC discards the coordinate fields inside its diagnostic adapter rather than passing them into reports.

Automatically obtained latitude and longitude are not retained in diagnostic results, the report database, PDFs, QR payloads or app logs. Retained evidence may include fix success, provider, accuracy, time to obtain a fix, location-service state and whether altitude or speed information was available, but not those coordinate values. The app does not perform ongoing location tracking. Android's own location services and providers operate according to your device settings and their own practices.

6. Bluetooth, Wi-Fi and NFC

Bluetooth diagnostics inspect capability and adapter state. If you start the optional nearby Bluetooth Low Energy scan, the app briefly receives advertisements and uses device addresses in memory to count distinct devices. Those addresses are not saved in reports. This test does not automatically pair with or connect to nearby devices. Android may require Nearby devices permission, or location permission on older Android versions, for this scan.

Wi-Fi diagnostics inspect whether Wi-Fi is supported, enabled and currently used as a network transport. They do not read or save Wi-Fi network names (SSIDs), access-point identifiers (BSSIDs), passwords or network traffic.

NFC diagnostics inspect capability and adapter state. The optional tag test detects a presented tag and counts its reported technologies. It does not read tag message contents, save tag identifiers or perform payments. The tag observation is shown during the test; the saved automatic result describes capability and state.

Audio inventory can separately include the Android-reported product names of connected input/output accessories, including Bluetooth audio accessories. Such labels may identify an accessory and can appear in saved diagnostic evidence and exported reports.

7. Sensors and optional step diagnostics

RENIIC uses available motion, light, proximity, pressure and other device sensors for hardware diagnostics. Local reports can contain sensor names, vendors, capabilities, sample counts, ranges and response measurements. Touch tests record grid coverage and interaction counts, not text typed in other apps.

RENIIC does not request Android's physical-activity permission. On Android 10 and newer, step-counter and step-detector sensors are intentionally outside RENIIC's current diagnostic scope: the app does not offer the step test or collect protected step readings. On Android 6 through Android 9, the guided test may observe step-sensor events while the test is open because those versions do not require that runtime permission; initial and final Android step-counter values may be saved as diagnostic evidence. These can be cumulative counter readings, not just steps taken during that test. RENIIC does not build an ongoing activity history or provide fitness tracking.

8. Biometrics

RENIIC uses Android biometric capability and authentication APIs. Android handles authentication; RENIIC does not receive raw fingerprints, face templates or other biometric templates, and does not store them.

Capability, enrollment availability and related Android status codes can be saved as diagnostic evidence. An optional authentication check displays Android's success, cancellation or error outcome on screen; it does not save biometric samples or an authentication history in the report database.

9. Device and diagnostic information

Saved sessions include manufacturer, model, Android device codename, Android version/API level, display properties, memory and storage capacity, battery information, hardware inventory, test results, measurements, timestamps and operator observations. Inventory may include Android camera identifiers and characteristics, sensor information and audio-device labels. These are device diagnostic details, not manufacturer certification.

The current app also reads Android ID, an Android-provided device identifier, and stores it locally in saved session data. It can be viewed on the Device Information screen. It is not included in the exported PDF or offline QR reference/digest, and is not automatically sent to Reniic. The app does not read IMEI, MEID, hardware serial numbers, phone numbers, subscriber identifiers or account information.

RENIIC keeps local permission and error troubleshooting logs. They can include device model/Android version, permission requests and states, timestamps, error messages and stack traces. These logs are not automatically uploaded and are not part of normal PDF reports. They are periodically rotated as newer entries accumulate, with no fixed age-based retention period. Developer/test builds can additionally capture uncaught errors and offer an explicit log export; these extra developer controls are not enabled in the production release.

10. Reports and local storage

Completed reports and accepted Individual Test results are saved in the app's private local database. Individual Test history stores the test name, final status, timestamp, manufacturer/model, Android version, and the diagnostic summary, evidence and measurements produced at completion; it does not store Android ID. Device Inspection may also save information you enter, such as customer/reference name, job reference, inspector name, technician notes, declared faults, reported issues, repairs and replacement parts. This contextual information does not override measured diagnostic evidence.

Only enter information you are authorized to include. Free-text fields are not a personal-information filter: names, contact details or other sensitive information you type may appear in the saved report and PDF. Review a report before sharing it.

The app disables Android cloud backup and its declared device-transfer rules exclude the report database and private files. Operating-system or device-manufacturer transfer behavior outside these app rules is not controlled by Reniic. App preferences and permission-request state are also kept locally.

11. Temporary diagnostic media

Camera captures and microphone recordings use a dedicated, app-private diagnostic cache area with session-owned opaque filenames. Normal completion, replacement and exit paths clean up this media. Leaving a media test or an activity interruption can end that attempt rather than preserve its private capture or recording.

An operating-system process kill, sudden shutdown or storage failure may prevent immediate deletion. On the next launch, RENIIC attempts recovery cleanup of its stale diagnostic media. If deletion fails, the app warns that cleanup could not be completed and retries on a later launch. Temporary media may remain in private app storage until cleanup succeeds or app data is removed; the app does not promise deletion while it is unable to run. Recovery targets diagnostic media, not saved reports or exported PDFs.

12. Sharing reports and offline QR references

Export creates a PDF in the app's private report cache. Sharing is a separate, explicit user action: Android's sharing interface gives the selected PDF to the app or service you choose, with temporary read access to that file. RENIIC does not automatically upload reports. A receiving app may store the PDF locally or send it elsewhere under its own practices. Reniic does not control that transferred copy.

PDFs can include approved device details, diagnostic results, measurements and inspection notes. They do not embed test camera photos or microphone recordings. They may include an offline QR reference containing a report identifier and digest derived from selected report fields. It contains no raw test media, location coordinates or Android ID. The QR is not an online verification service or independent authentication of the report.

13. RENIIC Pro and Google Play Billing

RENIIC can connect to Google Play Billing to retrieve locally appropriate product descriptions and prices, open Google's purchase flow, acknowledge qualifying purchases, restore purchases and check whether the Google Play account owns an active RENIIC Pro subscription or lifetime product. Google Play processes the payment. RENIIC does not receive or store your payment-card number or other full payment credentials.

The billing integration handles product identifiers, localized offer information, purchase state, acknowledgement state and a Google Play purchase token while checking ownership. Purchase tokens are kept in memory for that processing and are not stored in RENIIC's report database or local entitlement preference. The app stores only the most recently verified Pro tier and verification time in app-private preferences so recently verified access can remain available for a limited period when Google Play is temporarily unavailable. This local record is rechecked with Google Play and is not an indefinite or independent proof of ownership.

Core diagnostics and existing inspection continuation and retest features remain available without Pro. Google Play and its payment services handle billing information under Google's own privacy practices. RENIIC does not attach diagnostic reports, temporary media, location fixes, Android ID or operator notes to billing requests.

14. Retention and deletion

Saved reports and Individual Test history have no automatic expiry. They remain until you delete them in History or remove the app's data. Deleting an entry removes that database record; deleting a report does not delete previously generated PDFs, revoke previously shared copies or remove local troubleshooting logs. The limited billing-entitlement preference remains until ownership is refreshed, it expires under the offline-access rule, or app data is removed. Google Play purchase records are managed through Google Play and are not deleted by clearing RENIIC's local history.

There is no separate in-app control to delete individual cached PDFs. Android may reclaim cache files, and Android's app storage controls can clear the app's cache. Clearing cache is different from clearing app data: clearing app data removes local report history, preferences and logs as well. Uninstalling the app removes its local app data. Temporary diagnostic media is also subject to the cleanup described in section 11.

Copies you save or share to another app, storage provider or recipient remain there until removed through that destination. RENIIC cannot recall them. There is no RENIIC account or cloud report account to delete.

15. Data security

RENIIC uses Android app-private storage for reports, logs and temporary media. Its sharing provider exposes only the report-cache area, not the diagnostic-media area, and normal PDF sharing grants read access to the selected PDF only. These safeguards reduce unintended access; they are not a promise of absolute security or app-level encryption. Protect your device and choose report recipients carefully.

16. Third-party software and services

RENIIC includes AndroidX/CameraX, Kotlin, Gson, ZXing, the Google Play Billing Library and supporting Google components. You can read applicable open-source notices under Settings → About → Open-source licenses. Google Play Billing communicates with Google Play for purchase and entitlement operations; this is separate from sharing diagnostic data. The app includes no advertising, behavioral-analytics or cloud-reporting SDK.

Other apps you select for sharing, Android services and email providers have their own privacy practices. If you email Reniic, your email provider sends the message and any attachments you choose to include. Reniic uses that correspondence to respond to your request. Avoid sending unnecessary private diagnostic details or media. Deleting app data does not delete email correspondence; contact Reniic about privacy or deletion requests concerning information you send by email.

17. Intended audience

Reniic Device Diagnostics is a device diagnostic utility for consumers and technicians. It is not designed specifically for children.

18. Changes to this policy

Reniic may update this policy when the app or its handling of information changes. The governing policy will identify its effective date. Check the policy available in Settings and the published policy when reviewing an app update.

19. Contact us

Developer and publisher: Reniic

For privacy questions, support or requests concerning information you have sent to Reniic, contact: reniicmelville.sbc@gmail.com