How ScooterGo uses your information
This is a plain-language summary of features visible in the current local prototype. It is not a complete legal privacy notice and does not replace the operator's obligations. The operator identity, legal basis for each use, retention schedule, data-subject request contact, hosting regions and verified access rules have not been supplied in this project copy.
Information used by this prototype
Account registration uses your name, date of birth, email address, phone number and full home/billing address. If you apply to rent, the app can collect identity, driving licence and address-card / official address-document images for manual review, booking and payment status, pickup and return condition and fuel photos, and reports you submit about a scooter.
Location information
A report can include a phone location after you choose to share it. For an overdue return, the app can save your submitted GPS coordinates, accuracy and capture time in Supabase, together with the booking's verified parking location, calculated distance and a proposed fee range. Staff can review this evidence and any dispute. An overdue return without GPS assessment is also queued for staff review. These records persist after you close the page. A proposed fee is not automatically charged, and phone GPS is not proof of physical return.
Why the app uses this information
The app uses account and document information for manual account review, the billing address to prepare invoice recipient details, booking information to manage rentals, submitted photos and reports to document vehicle condition and incidents, and payment status to decide whether a confirmed rental can start. Stripe Checkout processes test payments. Supabase stores Checkout and PaymentIntent references, payment attempts, refund observations and review history. ScooterGo does not collect card details in its own forms.
Storage and access
Supabase provides authentication, database records and private file storage. Customers can view their own submissions; authorized staff can review them. Submitted rental evidence cannot be deleted through customer upload cleanup. Failed, unrecorded uploads can be removed by their owner. A staging cleanup tool supports a dry run and explicit deletion of expired fictional test documents. No production retention schedule or automatic production deletion is configured. Operator identity, legal bases, hosting regions, retention periods and a verified rights-request contact still need operator approval before real customer data is collected.
Before launch, the service operator must replace or complete this summary with verified controller and contact details, purposes and legal bases, recipients and transfers, retention periods, user rights and complaint routes. The app does not currently provide a configured receipt or in-app payment dispute workflow. A real service needs a verified customer support route before accepting payments.
Back to registration