DrMobix is a dedicated mobile hardware diagnostics and quality assurance application designed for mobile device refurbishing workstations, repair centers, trade-in operators, and end-users. Its singular function is to evaluate the mechanical, electrical, and sensor health of smartphones and tablets.
Our Core Privacy Commitment:
Hardware diagnostics must never become a conduit for data harvesting. DrMobix is architected on the principle of Privacy by Design and Default (PbD). We do not inspect personal files, we do not require account registration, we do not profile users, and we do not monitor or retain sensitive communications. Every diagnostic check is designed to answer a single technical question: "Is this physical hardware component functional?"
2. Scope of This Policy
This Privacy Policy applies to:
The DrMobix Mobile Application running on iOS and Android operating systems.
The Diagnostic Session Bridge connecting mobile devices to local or cloud-based desktop refurbishing workstations.
The Diagnostic Reporting Web API used to deliver completed hardware reports to a workstation or an enterprise client’s private diagnostic gateway.
Any public-facing website, documentation portal, or customer-facing diagnostics report viewer operated under the DrMobix domain.
This policy governs all diagnostic records, hardware performance metrics, and telemetry generated during testing sessions.
3. Operational Modes & System Architecture
DrMobix operates in two distinct testing contexts:
3.1. Standalone / On-Phone Mode
When a technician or consumer launches DrMobix directly on a device without a connected workstation:
Diagnostic tests are executed locally.
Reports are compiled and saved only in the device’s private application storage.
No network transmission occurs unless the user manually chooses to send the report to a desktop or workstation.
3.2. Workstation / Bench Connected Mode
When DrMobix is launched through a desktop refurbishing suite (for example, via QR code or an app deep link):
The desktop bench may pass session details such as a session identifier, a secure destination address, and optional inventory identifiers such as a device serial number or unique device ID.
When the test suite completes, the compiled diagnostic report is sent over an encrypted HTTPS connection to the designated workstation endpoint.
In both modes, sensors are checked in memory, results are summarized into a hardware report, and that report is either stored only on the device or securely synced to the workstation when the operator chooses or when a bench session is active.
4. Exhaustive Inventory of Diagnostics Data Collected
The DrMobix catalog includes 18 distinct diagnostic probes across 7 functional groups. Below is a breakdown of what each probe tests, what measurements are collected, and the privacy safeguards enforced.
4.1. Display & Touchscreen Probes
A. Touchscreen Digitizer
Hardware Evaluated: Capacitive digitizer matrix and touch controller.
User Interaction: The user drags their finger across a screen grid to cover every cell.
Data Collected:
Test outcome status: pass, fail, review, or skip.
Technical Privacy Safeguards:
Zero Gesture Tracking: The probe only evaluates whether each cell was touched. DrMobix does not record stroke trajectories, touch coordinates, velocity, pressure, or handwriting patterns.
Test Operation: Routes the synthesized test tone through the earpiece speaker channel.
Data Collected:
Test outcome status: pass or fail.
Technical Privacy Safeguards:
Audio output only; no recording occurs.
C. Primary Microphone
Hardware Evaluated: Integrated microphone and audio input path.
Test Operation: The user speaks for about 2 seconds. The app measures peak input volume in real time.
Data Collected:
A coarse volume category such as quiet, speech, or loud.
Test outcome status: pass or fail.
Critical Privacy Safeguards:
No Voice Recording Retention: Any temporary audio buffer created for the check is deleted from the device immediately after the volume level is evaluated.
No Voice Processing: Audio is never analyzed for speech content, identity, or language. No voice recordings or conversations are stored, transcribed, or transmitted.
4.3. Camera & Visual Probes
A. Rear Main Camera
Hardware Evaluated: Rear camera sensor, auto-focus, and image processing path.
Test Operation: Initializes the rear camera and shows a live viewfinder preview.
Data Collected:
Whether the preview started successfully.
Test outcome status: pass or fail.
Critical Privacy Safeguards:
Live Viewfinder Only: DrMobix does not take photos or record video during this test.
No photographs, videos, or optical image data are written to storage or transmitted.
B. Front Selfie Camera
Hardware Evaluated: Front camera sensor and image processing path.
Test Operation: Initializes the front camera and shows an on-screen preview.
Data Collected:
Whether the preview started successfully.
Test outcome status: pass or fail.
Critical Privacy Safeguards:
No Facial Harvesting: No face photographs, selfies, facial recognition data, or biometrics are captured, analyzed, saved, or uploaded.
4.4. Battery & Power Management
Battery State & Fuel Gauge
Hardware Evaluated: Battery health indicators, charging status, and system fuel gauge.
Test Operation: Reads platform battery information from the operating system.
Data Collected:
Battery charge percentage from 0 to 100.
Whether the device is currently charging.
Test outcome status: pass, fail, or review.
Technical Privacy Safeguards:
DrMobix only reads the overall hardware charge level. It does not query per-app battery usage or background process histories.
4.5. Physical Buttons & Haptic Feedback
A. Vibration Motor & Haptic Engine
Hardware Evaluated: Vibration motor or haptic engine.
Test Operation: Pulses the motor briefly or triggers haptic feedback.
Data Collected:
Whether the pulse ran successfully.
Test outcome status: pass or fail.
B. Physical Volume Keys
Hardware Evaluated: Volume Up and Volume Down hardware buttons.
Test Operation: Detects whether the volume buttons respond when pressed.
Data Collected:
Whether each volume button was detected.
Test outcome status: pass or fail.
Technical Privacy Safeguards:
Only volume keys are checked. DrMobix does not monitor passwords, keyboard typing, or other keys.
4.6. Motion & Environmental Sensors
A. Accelerometer
Hardware Evaluated: 3-axis accelerometer.
Test Operation: Detects whether the device moves enough to confirm the sensor is working.
Data Collected:
Whether motion was detected.
Test outcome status: pass or fail.
Technical Privacy Safeguards:
Raw acceleration values and continuous motion patterns are discarded as soon as movement is confirmed.
B. Gyroscope
Hardware Evaluated: 3-axis gyroscope.
Test Operation: Detects whether the device rotates enough to confirm the sensor is working.
Data Collected:
Whether rotation was detected.
Test outcome status: pass or fail.
Technical Privacy Safeguards:
Continuous rotational data is discarded. No gesture identification or spatial mapping is performed.
C. Proximity Sensor
Hardware Evaluated: Proximity sensor near the earpiece.
Test Operation: Detects when an object approaches or moves away from the top of the display.
Data Collected:
Whether the sensor state changed.
Test outcome status: pass or fail.
4.7. Biometric Hardware Controller
Biometric Sensor
Hardware Evaluated: Face ID, Touch ID, or Android biometric hardware.
Test Operation: Asks the operating system to confirm that the biometric sensor responds. The prompt informs the user that nothing is stored.
Data Collected:
Whether the sensor responded.
Test outcome status: pass or fail.
Critical Privacy Safeguards:
Authentication is handled only inside the device’s secure hardware environment.
DrMobix never receives fingerprint images, facial maps, iris scans, or device passcodes. It only receives a yes/no response from the operating system.
4.8. Wireless Radios & Network Interfaces
A. Network Radio Reachability
Hardware Evaluated: Wi-Fi and cellular connection status.
Test Operation: Checks whether the device has network connectivity.
Data Collected:
Whether the device is online.
Test outcome status: pass or fail.
Technical Privacy Safeguards:
DrMobix does not collect IP addresses, MAC addresses, Wi-Fi network names, DNS settings, or cell-tower identifiers.
B. Bluetooth Controller
Hardware Evaluated: Bluetooth radio adapter.
Test Operation: Checks whether Bluetooth is turned on.
Data Collected:
Whether the Bluetooth radio is on.
Test outcome status: pass or fail.
Technical Privacy Safeguards:
Nearby Bluetooth devices, beacons, headphones, or accessories are never scanned, discovered, listed, paired with, or tracked.
C. Location Fix / GPS Receiver
Hardware Evaluated: GPS and related satellite receivers.
Test Operation: Requests a short, low-accuracy location check only to verify that the receiver can obtain a satellite fix.
Data Collected:
Whether a satellite fix was obtained.
Test outcome status: pass or fail.
Critical Privacy Safeguards:
No Coordinate Storage: Latitude, longitude, altitude, speed, heading, and street address are never saved, stored, or transmitted.
5. Device Metadata & Report Attributes
When a diagnostic profile finishes, DrMobix creates a Hardware Report. That report may include:
5.1. Device Identification Data
Device model name reported by the operating system (for example, iPhone 14 Pro or Pixel 8).
Operating system version (for example, iOS 17.5.1 or Android 14).
5.2. Session & Hardware Identifiers
A unique session identifier for the diagnostic run.
Optional device serial number, included only when provided by the workstation for inventory tracking.
Optional unique device identifier, included only when provided by the desktop testing bridge.
5.3. Report Contents
A completed report may also include:
The diagnostic profile name (for example, Full suite).
Start and end times for the session.
Overall verdict and health score.
Per-test results, including test name, status (pass, fail, review, or skip), optional short notes, and limited non-personal measurements such as battery percentage, whether a camera preview started, microphone volume category, or whether GPS obtained a fix.
The report contains hardware test results only. It does not include photos, audio recordings, biometric templates, GPS coordinates, personal messages, or personal files.
6. Explicit Data Exclusions (What We NEVER Collect)
DrMobix is strictly partitioned from user personal content. The following categories are never accessed, extracted, stored, or transmitted:
Personal Identifiable Information (PII): Names, home addresses, personal email addresses, phone numbers, social security or national identity numbers.
Personal Media & Files: Photos in the camera roll, personal video recordings, audio files, documents, downloads, or local app files.
User Communications: SMS messages, instant messages, emails, voicemails, or call logs.
Accounts & Credentials: User passwords, keychain secrets, web credentials, payment tokens, or credit card details.
Browsing & App Activity: Web browsing history, bookmarks, search queries, installed apps list, or cross-app usage telemetry.
Biometric Templates: Fingerprint images, Face ID meshes, or biometric hashes.
Geographic Position: GPS coordinates, Wi-Fi location triangulation, or location history.
7. Local Bench Profile & On-Device Storage
Local Greeting Name: In the DrMobix Profile view, technicians may enter a Bench Name to label the workstation greeting on that phone.
Privacy Protection: This name is saved only on the local device. It is never included in the diagnostic report and is never sent over the network.
Local Report History: Diagnostic reports are saved in the app’s private storage on the device. They remain available to the operator for review until removed or until the app data is cleared or the app is uninstalled.
DrMobix enforces strict transport-layer constraints to protect report transfers:
Mandatory HTTPS Encryption: Reports are sent only over HTTPS. Plain HTTP connections are rejected.
No Embedded Credentials in URLs: Destination addresses that embed usernames or passwords in the URL are rejected to avoid accidental credential leakage.
Endpoint Control: By default, bench sessions may route to DrMobix’s diagnostic reporting service. Enterprise facilities may instead use their own secure workstation endpoint through authenticated launch tokens.
Timeouts & Connection Hygiene: Network requests use short connect and transfer timeouts so connections do not remain open longer than needed.
9. Operating System Permissions Reference & Justifications
The table below lists the main runtime permissions used on iOS and Android, why they are needed, and how privacy is protected:
Permission
Platform
Purpose in DrMobix
Privacy Enforcement & Retention
Camera
iOS / Android
Verifies that the camera preview works.
Viewfinder only; no photos or videos are captured or saved.
Microphone
iOS / Android
Measures ambient volume for about 2 seconds.
Temporary audio buffer is deleted immediately. No voice data is kept.
Face ID / Biometrics
iOS / Android
Verifies that the biometric sensor responds.
Handled by secure device hardware; no biometric images or templates are accessible to the app.
Location While Using the App
iOS / Android
Verifies that the GPS receiver can obtain a satellite fix.
Coordinates are never stored or transmitted.
Bluetooth
iOS / Android
Checks whether the Bluetooth radio is powered on.
Nearby devices are never scanned or tracked.
Motion / Fitness
iOS
Tests accelerometer and gyroscope responsiveness.
Motion vectors are discarded; only a yes/no movement result is kept.
Vibrate
Android
Confirms haptic or vibration hardware.
Functional confirmation only.
Network / Internet
Android / iOS
Checks connectivity and syncs reports to a workstation when requested.
Encrypted transmission only.
Local Network
iOS
Connects to a local desktop diagnostic workstation over Wi-Fi.
Used for local workstation sync only.
10. Legal Bases for Data Processing (GDPR / UK GDPR)
Under the European Union General Data Protection Regulation (Regulation (EU) 2016/679) and UK GDPR, DrMobix processes diagnostic data under the following lawful bases:
Article 6(1)(b) - Performance of a Contract: Processing hardware diagnostics is necessary to evaluate device condition and deliver the diagnostic result requested by the user or technician.
Article 6(1)(f) - Legitimate Interests: We and our enterprise refurbishment partners have a legitimate interest in certifying device functionality, detecting defective components, preventing e-waste, and supporting safe refurbished devices.
Article 6(1)(a) - Consent: Where platform permissions such as Camera, Microphone, or Location are granted, users provide consent through operating system permission dialogs, which can be revoked at any time.
11. California Consumer Privacy Act (CCPA / CPRA) Disclosures
Pursuant to the California Consumer Privacy Act as amended by the California Privacy Rights Act (CPRA):
No Sale of Personal Information: We have never sold, and will never sell, personal information or diagnostic reports to third parties.
No Sharing for Cross-Context Behavioral Advertising: We do not share consumer data for behavioral advertising.
Categories of Personal Information Collected: We collect technical device metrics such as model, operating system, hardware test status, and optional serial or unique device identifiers in refurbishment workflows. We do not collect real names, postal addresses, or biometric templates.
Consumer Rights: California residents have the right to request access to, deletion of, and correction of their diagnostic records, and the right not to be discriminated against for exercising privacy rights.
12. Apple App Store & Google Play Developer Policy Compliance
DrMobix complies with Apple and Google developer requirements:
Apple App Store Review Guidelines (Guideline 5.1.1 - Data Collection and Storage):
DrMobix requests only permissions essential to its core diagnostic functionality. Data collected is limited to what is needed to evaluate hardware performance. Account registration is not required, and permission usage is disclosed in the app’s platform privacy strings.
Google Play Developer Policy (User Data & Device and Network Abuse):
DrMobix follows Google Play disclosure and consent requirements. Bluetooth is used only to check radio power state and is not used for location tracking or nearby-device discovery.
13. Data Retention, Storage Limits & Deletion Rights
On-Device Storage: Diagnostic reports remain on the phone until:
The user or technician deletes the application data in system settings; or
The DrMobix application is uninstalled.
Server-Side Storage (Workstations & Cloud Bridges): Diagnostic reports sent to a refurbishment workstation or cloud reporting endpoint are retained according to that organization’s inventory and warranty needs (commonly 30 to 180 days).
Right to Erasure: If your device was tested during a trade-in or repair and you want server-side diagnostic records linked to your device serial number or session ID deleted, email privacy@drmobix.com. Requests are processed within 30 days.
Q1: Can DrMobix see my personal photos or access my photo gallery?
No. DrMobix has no access to your photo library. The camera test shows a live preview only to check that the camera works. The app never captures, saves, or uploads photos.
Q2: Does the microphone test record my private conversations?
No. The microphone check samples audio briefly only to read volume level. Any temporary audio buffer is deleted immediately. Speech is never recorded, transcribed, or uploaded.
Q3: Does DrMobix access my fingerprints or Face ID geometry?
No. Biometric checks run inside the device’s secure hardware environment. The operating system only returns whether the sensor responded. DrMobix has no access to biometric data.
Q4: Does DrMobix track my location?
No. The GPS check only verifies whether the satellite receiver can obtain a signal lock. Coordinates are never saved, stored, or transmitted.
Q5: Is my personal name or contact list uploaded?
No. DrMobix does not request contacts access and does not require user accounts. The optional Bench Name on the Profile screen stays on the local device only.
15. Changes and Revisions to This Policy
We may revise this Privacy Policy to reflect updates to our diagnostic features, operating system requirements, or applicable laws.
When we make changes, we will update the “Last Updated” date at the top of this document. We encourage users, technicians, and partners to review this policy periodically.
16. Contact & Regulatory Inquiry Information
For inquiries, privacy assessments, data deletion requests, or questions about this Privacy Policy, contact:
