Effective Date: September 24, 2026
Last Updated: September 24, 2026
Summary: Driver Jarvis is built with a strict Air-Gapped Privacy by Design architecture. All facial vigilance analysis and vehicle motion telemetry execute 100% locally in your device's temporary, volatile RAM. No video or photographs are ever saved, recorded, or transmitted off your device. Driver Jarvis contains zero third-party advertising SDKs, zero user tracking libraries, and maintains no external cloud servers.
1. Core Privacy Philosophy & Offline Architecture
Driver Jarvis ("the Application", "we", "our") is engineered from the ground up to provide vital automotive vigilance and driver alertness assistance without compromising user privacy. The application functions entirely offline and does not require user registration, email addresses, phone numbers, or account creation.
2. Camera Feed & On-Device Computer Vision
To detect driver drowsiness, prolonged eyelid closure, yawning, and head drooping, Driver Jarvis requests access to your device's front camera (android.permission.CAMERA):
- Volatile RAM Processing Only: Incoming camera frames are analyzed instantaneously in temporary memory using on-device ML Kit models to calculate Eye Aspect Ratio (EAR) and facial orientation angles.
- Zero Storage or Recording: Video frames are immediately overwritten and wiped from memory in sub-second cycles (approx. 30–45 milliseconds). Driver Jarvis never records video, captures photos, or creates biometric identification profiles.
- Zero Network Transmission: The camera stream never leaves the physical device and is never uploaded to any remote server or third-party cloud.
3. Device Motion Sensors (Crash & Rollover Guard)
The Application utilizes your device's built-in accelerometer and gyroscope hardware:
- Real-Time Dynamic Filtering: Motion data is processed strictly on-device to distinguish normal driving dynamics (speed bumps, sudden braking) from severe vehicular impacts or rollover events.
- Zero Continuous Logging: Sensor readings are processed purely in real-time execution memory and are not logged, profiled, or retained over time.
4. Location Permissions (GPS Emergency SOS)
Driver Jarvis requests access to location services (ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION) solely for emergency roadside dispatch:
- Emergency Trigger Only: Geographic coordinates (latitude, longitude, and map link) are retrieved strictly when an emergency event occurs (such as a confirmed severe vehicle impact or manual Emergency SOS activation).
- Pre-Filling Native Dispatch: Location coordinates are used exclusively to pre-populate an emergency dispatch message draft within your device's native messaging app for one-tap sharing with your designated emergency contacts.
- No Background Tracking: Driver Jarvis does not track your driving route, does not maintain a travel history, and never transmits location coordinates to any remote server.
5. Emergency Contacts & Native Messaging
- Local Storage of Contacts: Any emergency contact phone numbers you choose to save are stored exclusively in your device's private Android SharedPreferences storage (
driverjarvis_contacts). This data is completely isolated from other applications and never leaves your device. - User-Controlled Native Intents: Driver Jarvis omits dangerous background SMS permissions (
SEND_SMSis strictly removed). All communications are initiated through standard Android user intents (Intent.ACTION_SENDTOandIntent.ACTION_DIAL), ensuring that you always maintain explicit control over any message transmission.
6. Zero Third-Party Advertising & Analytics
Driver Jarvis contains:
- NO Advertising SDKs: We do not display banner, interstitial, or rewarded ads.
- NO Analytics SDKs: We do not include Google Analytics, Firebase Analytics, Facebook SDK, or behavioral tracking libraries.
- NO Device Fingerprinting: We do not collect or monitor IMEI numbers, MAC addresses, or Android Advertising IDs (AAID).
7. Google Play Data Safety Compliance
In accordance with Google Play's Data Safety Declaration guidelines:
- Data Collected: None (0 bytes).
- Data Shared: None (0 bytes).
- Data Security: All processing is strictly contained within the physical Android device.
- Data Deletion: Because no data is collected or hosted on external servers, uninstalling the app permanently purges all local cached preferences and user-configured contacts.
8. Children's Privacy & Age Restriction
Driver Jarvis is intended specifically for licensed motor vehicle drivers aged 18 and over. The Application does not knowingly collect any information from children under 13, in strict adherence to COPPA and global child privacy regulations.
9. Modifications to this Privacy Policy
We may update this Privacy Policy from time to time to reflect operational or regulatory improvements. Any revisions will be published immediately with an updated Effective Date at this URL.
10. Developer Contact Information
For questions or inquiries regarding this Privacy Policy or Driver Jarvis, contact developer support at:
📧 Email: support@driverjarvis.ai
🌐 Developer Center: Legal & Developer Center