The rules, in plain language.

• Account details such as name, email address, phone number, role, and authentication metadata.
• Booking and property information such as service type, suburb, address, schedule, notes, add-ons, photos where uploaded, and booking status.
• Sensitive household access information only where needed for a booking, such as gate, alarm, parking, pet, and access instructions.
• Xooter onboarding information such as identity, verification, training, screening, document, location-coverage, and payout-readiness data.
• Payment metadata, reconciliation references, XootCred ledger entries, Care+ membership status, and provider event metadata.
• Support, safety, fraud, device, diagnostics, push-token, email-delivery, and app-usage data needed to operate and secure Xoot.

Xoot uses information to create accounts, verify users and Xooters, price and manage bookings, process payments through providers, route support, protect sensitive household data, prevent fraud, send transactional notifications, improve reliability, and prepare legally required records.

Xoot does not sell personal information. Marketing communication should be consent-based or otherwise lawful, and users must be able to opt out where required.

Where Xoot enables the live-journey feature, an accepted Xooter may explicitly choose to share their device's precise foreground location for an active, en-route booking. The assigned customer and MFA-verified Xoot dispatch administrators can view the latest location. Sharing stops when the Xooter chooses Stop, leaves the foreground sharing screen, or the job ends. This is optional, and Xoot does not use this feature to collect background movement history.

Xoot keeps only one current GPS position for an eligible booking. A position becomes unavailable to readers no later than 60 seconds after its capture; a database cleanup job runs each minute to remove expired records. If you open an authorised journey map or request a road-time estimate, the displayed position and, for directions, the booking destination are sent to Mapbox. Mapbox SDK usage may involve map-related telemetry under Mapbox's applicable policies. Road-time estimates reflect provider routing at request time and are not guaranteed arrival times.

This functionality remains subject to a separate launch approval and appropriate international-transfer, service-provider, security and privacy checks before being enabled.

Xoot uses Supabase and trusted operational providers for authentication, database, storage, Edge Functions, notifications, payment workflows, support, monitoring, and automation. Service-role keys and provider secrets must never be exposed in the website, Expo app, public JavaScript, screenshots, or support chat.

• Row Level Security and role checks restrict access to account, booking, payment, Xooter, support, and property data.
• Sensitive household access fields are intended to be time-locked and logged when revealed to assigned Xooters.
• Admin actions must be typed, auditable, and protected by role checks and MFA where available.
• Payment success is verified server-side and never trusted from the frontend alone.
• Push notifications, Live Activities, widgets, and emails must avoid full addresses, access codes, private complaints, payment references, and identity documents.

You may request access, correction, deletion, objection, or restriction of your personal information where applicable under South African law. Some records may need to be retained for safety, fraud prevention, tax, payment, dispute, or legal reasons.

See the POPIA Notice and Account Deletion page for the operational process.