Google Play Data Safety Draft
This page is a working guide for the Rider Recall Play Console Data Safety form. Verify the final answers against the actual production backend, SDKs, and release build before submission.
Data types likely collected
| Play category | Rider Recall examples | Purpose |
|---|---|---|
| Personal info | Email address, display name, handle, profile text, social links users add. | Account management, app functionality, user communications. |
| Photos and videos | Avatar, bike photo, ride/feed images. | Profile, social posts, rider identity. |
| Location | Precise/approximate location when using map presence, nearby riders, weather, ride calls/events. | App functionality and safety-related presence features. |
| Messages | Community chat, crews, event chat, DMs, Pit stop messages. | App functionality and user communications. |
| App activity | Posts, friend requests, RSVPs, check-ins, road alerts, event actions. | App functionality, safety, moderation. |
| Device or other IDs | Push notification token, purchase token, platform/device diagnostic identifiers where used. | Notifications, subscriptions, fraud prevention, diagnostics. |
| Purchase history | Google Play Event Host subscription token/status. | Subscription entitlement verification. |
Security practices
- Use HTTPS for public web/app API traffic in production.
- Do not disclose precise user location except through explicit visibility features.
- Provide privacy policy URL in Play Console and inside the app.
- Provide in-app account deletion path and this public web account deletion link.
- Verify Google Play subscription purchases on the backend before granting Event Host access.
Recommended Play Console URLs
- Privacy policy:
https://riderrecall.com/privacy.html - Account deletion:
https://riderrecall.com/delete-account.html - Support:
https://riderrecall.com/support.html