Google Data Safety Mapping

Every data type declared in the Google Play Data Safety form is mapped below to the exact API endpoint that collects it. If it exists in the API — it is disclosed.

Policy: Every field collected by any backend endpoint must appear in the Data Safety form. This document is the authoritative source of truth.

Name

/user

Backend Function(s)

getUser / deleteUser

Fields Collected

full_nameemail

Purpose

Account identification and service personalization

Shared With

Service providers (drivers/scrappers)

Disclosed in Google Play Data Safety form

Precise Location

/location

Backend Function(s)

locationUpdate / updateDriverLocation

Fields Collected

latitudelongitudeaccuracyspeedheading

Purpose

Real-time driver matching and pickup logistics coordination

Shared With

Service providers, partner scrap yards

Disclosed in Google Play Data Safety form

Photos and Videos

/upload

Backend Function(s)

uploadImage

Fields Collected

image_urlphotos[]

Purpose

Scrap material identification, pricing, and pickup documentation

Shared With

Service providers, partner scrap yards

Disclosed in Google Play Data Safety form

Financial Info / Payments

/payment

Backend Function(s)

paymentCharge / processDriverPayout

Fields Collected

amountcurrencypayment_method_idpayment_intent_id

Purpose

Payment processing, payout distribution, and transaction logging

Shared With

Stripe (payment processor)

Disclosed in Google Play Data Safety form

Summary — Data Safety Form Checklist

Name/user
Disclosed
Precise Location/location
Disclosed
Photos and Videos/upload
Disclosed
Financial Info / Payments/payment
Disclosed
base44
Edit with Base44