RIDERADAR

Privacy Policy

Version 2026-08-16 · Effective 16 August 2026

This policy describes the RideRadar mobile app and related APIs. Play Console “Data safety” must stay consistent with this page.

1. Controller

PVK TECHNOLOGIES PRIVATE LIMITED, K SHIRE BUILDING A-1704, PLOT B ANDC SR NO 13/1, Punawale, Pune City, Pune- 411033, Maharashtra, India.

Grievance / data-protection contact: Prasad Kutarekar, support@rideradar.in. We aim to respond within 15 days.

2. What we collect

Account

Email (login and OTP), name, username, birthdate (18+ gate), optional profile photo, optional background photo, optional bio, bike and rider-type tags.

Phone (optional)

Country code + local number. Shown on your own profile and to admins of groups you join, for ride coordination. Not sold. Not required to create an account.

Social and riding data

Follows, group memberships, trips, waypoints, schedules, hosts and co-hosts, events, tracks, expenses and settlement ledgers, awards and ride stats (distance, ride count, longest ride), reports you file, and support tickets (including optional screenshots).

Live location

Only while a ride is active and you have not hidden your pin: GPS coordinates, speed, heading, and battery. Shared with other participants of that ride over a realtime channel, with a periodic fallback. Pins are purged when the ride ends. The app may use background location and a foreground location service so the pack can still see you if the screen is off. We show an in-app disclosure before the system permission prompt. Hide-my-location stops broadcasting without leaving the ride.

Media

Images for profile, group, event, trip, track, and support attachments. Stored in AWS S3. You attest upload rights on first pick.

Device and notifications

Push token (Firebase Cloud Messaging), app version, OS, and device model on support tickets. Crash or diagnostic data may be collected by the platform.

Pillion intercom (Android)

Microphone audio is processed on-device / peer-to-peer for the call. We use Bluetooth and nearby Wi-Fi devices to find and link the other phone. READ_PHONE_STATE is used so an incoming cellular call can mute the intercom. We do not keep a library of your intercom recordings as account data.

3. Why we use it

Legal bases under Indian law include providing the service you asked for, legitimate safety/moderation needs, and consent where the OS permission dialog is required (location, microphone, nearby devices, notifications).

4. Who sees it

We do not sell personal data. We do not run third-party advertising SDKs in the current app.

5. Retention

Account and content stay until you delete the account or we close it for a violation. Live-location pins are removed when the ride ends. Media is deleted in the account-deletion cascade. Some records (for example anonymised references or legal holds) may remain where the law requires.

6. Your rights

You can also complain to the Grievance Officer and, where applicable, to the Data Protection Board of India.

7. Children

RideRadar is 18+. We do not knowingly create accounts for children. If you believe a minor registered, email us and we will delete the account.

8. Security and transfers

Traffic uses HTTPS. Credentials are handled by Amazon Cognito. Servers may process data in AWS regions outside India. We still remain the Indian operator responsible for your request.

9. Changes

If this policy changes in a material way we bump the in-app privacy version and ask you to accept again.