Data Safety

What we collect.In plain English.

This page mirrors the Google Play Data Safety form for the GORydz Rider app, category by category. It exists so you can verify what we declare to Play matches what we actually do.

Last Updated: May 13, 2026Full Privacy Policy

Encrypted in transit

Every request between the app and our servers uses HTTPS/TLS. Payment data goes directly to Stripe over an encrypted channel.

Delete your data

Open the app and go to Settings → Account → Delete account, or email [email protected].

Personal info

Information you provide when you create a GORydz account and book rides.

Name

Collected: Yes
Shared with
Shared with the assigned driver for each trip
Status
Required
Purposes
App functionalityAccount management

Email address

Collected: Yes
Shared with
Not shared with third parties
Status
Required
Purposes
Account managementCommunications

Phone number

Collected: Yes
Shared with
Masked relay shared with driver during active trips; never the raw number
Status
Required
Purposes
App functionalityAccount management

User IDs

Collected: Yes
Shared with
Shared with Firebase (Google) and Stripe
Status
Required
Purposes
App functionalityAnalyticsAccount management

Financial info

Payment information. GORydz does not store raw card numbers — payments are processed and tokenized by Stripe.

Payment info

Collected: Yes
Shared with
Stripe (PCI-DSS compliant payment processor)
Status
Required
Purposes
App functionalityFraud prevention, security, and compliance

Card numbers are tokenized by Stripe and never reach GORydz servers in plaintext.

Location

Used to show you the live map, calculate fares, and route the driver to your pickup. Only collected while the app is in use (foreground).

Approximate location

Collected: Yes
Shared with
Shared with the assigned driver during an active trip; Mapbox for map tiles
Status
Optional
Purposes
App functionality

Without location permission the app cannot book a ride. Background location is NOT collected.

Precise location

Collected: Yes
Shared with
Shared with the assigned driver during an active trip; Mapbox for map tiles
Status
Optional
Purposes
App functionality

Photos and videos

Only collected if you choose to upload a profile photo. We do not access your photo library outside of an explicit upload.

Photos

Collected: Optional
Shared with
Not shared with third parties
Status
Optional
Purposes
PersonalizationAccount management

App activity

High-level usage signals — which screens you visit, which buttons you tap — collected via Firebase Analytics.

App interactions

Collected: Yes
Shared with
Firebase / Google
Status
Required
Purposes
Analytics

No clickstream tied to your name. Aggregated to understand which features are used and to detect crashes.

App info and performance

Diagnostics so we can fix bugs and crashes.

Crash logs

Collected: Yes
Shared with
Firebase Crashlytics / Google
Status
Required
Purposes
App functionality

Diagnostics

Collected: Yes
Shared with
Firebase Crashlytics / Google; Mapbox telemetry
Status
Required
Purposes
App functionality

Other app performance data

Collected: Yes
Shared with
Firebase / Google
Status
Required
Purposes
App functionality

Device or other IDs

Identifiers generated by Firebase, Mapbox, and Stripe SDKs. Required for push notifications, crash reporting, map rendering, and payment fraud prevention.

Device or other IDs

Collected: Yes
Shared with
Firebase (Google), Mapbox, Stripe
Status
Required
Purposes
App functionalityAnalyticsFraud prevention, security, and compliance

Includes Firebase Installations ID, FCM device token, Crashlytics installation UUID, Mapbox telemetry token, and Stripe device fingerprint. We do NOT collect Android Advertising ID (AD_ID) — that permission is explicitly removed from the app manifest.

Messages

In-app chat between rider and driver during a trip. Messages are auto-translated when languages differ.

In-app messages

Collected: Yes
Shared with
The other party on your trip
Status
Optional
Purposes
App functionality

Stored for trip-history access for the duration of your account and for safety review if a complaint is filed.

What we do NOT collect

These categories are declared as “not collected” in the Play Data Safety form:

Race or ethnicity
Political or religious beliefs
Sexual orientation
Other sensitive personal info
Health and fitness data
Audio files
Files and documents
Calendar events
Contacts
Web browsing history
Installed apps
Android Advertising ID (AD_ID)

Notice a mismatch?

If anything you see the app doing isn't reflected here, that's a bug — email [email protected] and we'll fix it.

Read the full Privacy Policy