Roaded Privacy Policy

1. Who is responsible

Roy Digital App Studio (Proprietorship), GSTIN 09ALRPR8561K1Z1, at Gaur City 2, Greater Noida West, Gautam Buddha Nagar, Uttar Pradesh 201301, India, is responsible for Roaded. Privacy and grievance requests may be sent to roy@roydigital.in.

2. Information Roaded handles

• Account: Firebase user ID, email, display name, sign-in provider and account timestamps when you sign in. Choosing Skip for now does not create an account.
• Vehicle records: vehicles, odometer readings, fuel and expense entries, maintenance, reminders, document details, emergency contacts, trips and GPS route points you choose to record.
• Photos: vehicle, document, receipt or invoice images you select or capture.
• Location: coordinates used for a trip you start, nearby-place search, reverse geocoding or an emergency map link.
• Diagnostics: pseudonymous app-instance, device, approximate-region, interaction and crash information processed by Google Analytics for Firebase and Crashlytics. Roaded does not attach your Roaded UID or email to those services.
• Purchases: product and purchase status received from Google Play. We do not receive full card or bank details.

3. Local storage and optional cloud backup

Roaded stores records in private app storage on your device. If you sign in and enable cloud features, it synchronises your records to a private Firebase account area. Backed-up photos are stored under your Firebase user ID. Firebase Cloud Messaging may store a device token for notifications.

4. Feature-specific processing

Maps, nearby places and sharing

When you start Nearby, Roaded sends coordinates and your selected category to the configured provider: Google Places or the OpenStreetMap Overpass service. Roaded does not keep a server-side Nearby-search history. Emergency sharing creates a map link on your phone and opens the Android share sheet; you choose the receiving app and recipient.

Fuel-price contribution

Roaded asks before the first contribution. If you agree, it sends city, state, country, fuel type and price per unit. The shared daily aggregate contains no account ID, vehicle, registration number, station or precise coordinates. You can turn contribution off.

Security

Firebase App Check uses device/app attestation, including Play Integrity on Android, to help reject unauthorised clients.

5. Permissions

• Location: nearby searches, map links and GPS trips you start. On Android, a visible foreground-service notification remains during trip recording. Roaded does not request “Allow all the time”.
• Camera and selected photos: images you choose to capture or select, plus the emergency torch. Roaded does not request access to your entire gallery.
• Notifications: reminders and Roaded notifications you allow.
• Internet/network: sign-in, backup, maps, fuel estimates, purchases, security and diagnostics.

6. Why data is processed

We process data to provide features you request, maintain and secure the service, remember choices, perform optional backup, restore purchases, diagnose failures, comply with law and answer support or privacy requests. Where consent is the applicable basis, you may withdraw it.

7. Service providers and disclosures

We do not sell personal data. Roaded uses Google Firebase (Authentication, Firestore, Storage, Messaging, Analytics, Crashlytics and App Check), Google Play, and Google Places/Maps or OpenStreetMap Overpass for features you start. The app you select from Android's share sheet receives only the content you choose to share. We may disclose information where lawfully required or necessary to protect rights and security.

8. Storage locations and international processing

Roaded's Cloud Firestore is configured in Google's nam5 United States multi-region. Firebase Authentication is operated from US data centres. Firebase and mapping providers may process data on global infrastructure, subject to their terms and applicable cross-border rules.

9. Retention

• Device records remain until you delete them, clear app storage or uninstall Roaded.
• Account data, cloud records and backed-up photos remain until deleted, subject to secure backup-system deletion intervals.
• Crashlytics crash traces and associated installation identifiers are retained by Google for 90 days.
• Analytics user and event data follows the configured 2- or 14-month standard-property retention setting; aggregate reports may remain longer.
• Support and deletion correspondence is normally kept up to 12 months after closure unless law, security or a dispute requires longer.
• City/day fuel aggregates may remain because they contain no account ID and cannot reasonably be separated back to an individual.

10. Deletion

Use Profile → Account → Delete account to delete your Firebase account, private Firestore records, device tokens and backed-up Storage photos. This does not erase device-only records; clear Roaded's app storage or uninstall it. You can also follow the web deletion instructions. Cancel any active Google Play subscription separately.

11. Security

Roaded uses TLS in transit, Firebase encryption at rest, per-user Firestore and Storage rules, App Check and private app storage. Images are compressed and metadata-stripped before upload. No system is risk-free.

12. Your choices and rights

You may ask for information, correction, erasure, consent withdrawal or grievance handling by emailing roy@roydigital.in. We may verify ownership. Applicable statutory escalation routes remain available, including the Data Protection Board of India when the relevant provisions apply.

13. Children

Roaded is for people aged 18 or older and is not directed to children. Contact us if you believe a child supplied personal data.

14. Important notice

Roaded is a private record-keeping app. It is not affiliated with or endorsed by an RTO, the Ministry of Road Transport and Highways, an insurer, workshop or emergency service, and it does not verify documents against government systems. In an emergency in India, call 112.

15. Changes

We may update this policy when Roaded, its providers or applicable law changes. The last-updated date identifies the current version; material changes will be highlighted where required.