VRTrickee Privacy Policy
How the VRTrickee Android application handles driver identity, location, voice input, vehicle, trip, and operational information.
Last updated 25 August 2026
1. Scope and access
This policy applies to the public VRTrickee Android application, package com.trickee.vrtrickee, and the Trickee services used to authenticate drivers, show fleet data, receive driver actions, process optional voice input, and provide trip and vehicle guidance.
Google Sign-In verifies identity. Fleet, vehicle, and role access is granted separately by Trickee or an authorized fleet administrator.
2. Data we process
- Account data: name, email address, Google account identifier, authentication status, role, and session identifiers.
- Fleet and vehicle data: fleet, driver, vehicle, order and trip identifiers; assignments; vehicle status; battery state; and operational alerts.
- Foreground location: latitude and longitude, accuracy, speed, timestamp, and trip context while the app is open and location permission is granted.
- Voice input: a short audio clip recorded only after the driver taps the voice control and grants microphone permission. It is sent to Trickee for transcription and assistant processing.
- Driver actions: trip, charging, waiting, SOS, issue-report, assistant-message, and alert acknowledgement events.
- Technical data: app and operating-system version, network and request metadata, error details, and security logs.
3. Permission behavior
VRTrickee requests foreground location for live driver and trip features, microphone access only when voice input is used, and notification access for quick actions and alerts. The current Play build does not request background-location access.
You can deny or revoke an optional permission in Android settings. The related feature will be unavailable or less accurate.
4. Why we use data
- Authenticate users and enforce fleet, driver, vehicle, and role access.
- Show live vehicle, order, trip, charging, route, battery, and safety information.
- Record authorized driver actions and location-assisted operational events.
- Transcribe optional voice input and generate relevant assistant responses.
- Secure the service, troubleshoot failures, prevent misuse, and meet legal or contractual duties.
5. Sharing and advertising
Authorized fleet personnel may see information associated with their drivers, vehicles, orders, and trips. Authentication, transcription, hosting, database, monitoring, and delivery providers may process data on our behalf under their applicable safeguards.
VRTrickee does not contain third-party advertising and does not sell driver location, voice, account, vehicle, or trip data for advertising.
6. Storage, retention, and security
Data is transmitted over encrypted connections. Authentication tokens are stored using Android-protected application credentials. Operational records are retained only as needed for fleet operations, safety, support, security, contracts, backups, and legal obligations. Voice clips are submitted for the requested transcription workflow and are not intended to become a reusable voice profile.
We use access controls, authenticated APIs, scoped infrastructure access, encrypted transport, and operational monitoring. No system can be guaranteed completely secure.
7. Choices and contact
- Revoke location, microphone, or notification access in Android settings.
- Sign out to remove the active application session from the device.
- Ask your fleet administrator to correct an assignment or operational record.
- Request access, correction, deactivation, or deletion, subject to lawful retention requirements.
VRTrickee is intended for authorized adult drivers and fleet personnel and is not directed to children.
Privacy requests: privacy@trickee.co.in. Support: support@trickee.co.in.