Privacy Policy

Privacy principles

• Collect only what is needed to operate, protect, support, and improve WakaGood.
• Use location, route, payment, document, and support data for clear service purposes.
• Share trip details by ride stage so users receive what they need without unnecessary exposure.
• Store payment details through trusted providers instead of storing full card numbers or security codes in WakaGood.
• Keep sensitive records behind role-based, audited, server-side controls wherever practical.

Information WakaGood collects

• Account information: name, email, phone number, account role, profile photo, language, account status, notification preferences, and support preferences.
• Passenger ride information: pickup GPS or address, destination, stops, timing, vehicle preference, route estimates, fare mode, fare proposals, no-negotiation fare choices, accepted fare, trip status, cancellation context, ratings, support reports, and chat content.
• Rider application information: identity details, date of birth, vehicle details, documents, insurance details, background-check consent, review status, payout status, tax onboarding status, destination preference, and availability state.
• Location information: passenger pickup location, typed addresses, rider active location, rider approach to pickup, ride progress location, GPS freshness, approximate marketplace distance, and ETA.
• Payment information stored as provider references: secure customer, payment method, charge, refund, transfer, subscription, checkout, and payout references. WakaGood does not store full card numbers or card security codes.
• Communications and notices: WakaGood popups, push notifications, in-app notices, SMS, email, call-session metadata, support tickets, safety reports, delivery records, and contact attempts.
• Device, map, and usage information: browser type, app installation state, device permission state, request IDs, route-estimate usage, map tile cost signals, feature flags, security events, reliability diagnostics, and runtime errors.
• Operations records: review notes, support actions, account restrictions, safety decisions, audit logs, payout or payment review status, compliance reminders, and diagnostic events.

Sources of information

WakaGood may collect information directly from passengers and riders, from device permissions, from ride activity, from payment and payout providers, from identity or eligibility providers, from map and routing providers, from support communications, from system logs, and from authorized platform operators performing review or support work.

How WakaGood uses information

• To create, authenticate, secure, restore, and manage passenger, rider, business, and service accounts.
• To publish ride requests, choose fare mode, calculate and recalculate route-based guidance, match passengers and riders, support capped negotiation, display accepted fare, and process trip completion.
• To show the correct map experience, including no-cost fallback maps, request-page maps after addresses are entered, rider approach before pickup, and route lines when available.
• To verify rider eligibility, support background-check workflows, document review, tax onboarding, payout readiness, WakaGood approval decisions, and compliance reminders.
• To process payments, subscriptions, refunds, rider payouts, referral credits, business fees, accounting records, chargeback review, and settlement support.
• To send WakaGood notices, push notifications, SMS, email, support responses, safety messages, ride updates, fare updates, account alerts, and service announcements.
• To detect abuse, investigate incidents, prevent fraud, enforce platform rules, monitor marketplace health, improve reliability, control provider costs, and comply with legal or regulatory duties.

Sharing by ride stage

• Before match: riders may see request details needed to evaluate the trip, such as general pickup context, destination context, estimate, fare mode, and timing. WakaGood should avoid exposing unnecessary passenger detail before match.
• After match: the matched rider and passenger may receive the information needed for pickup, approach tracking, contact, navigation, ride progress, support, and completion.
• After completion: WakaGood may retain matched-party, payment, settlement, rating, support, safety, and audit records for business, legal, accounting, fraud prevention, and dispute purposes.

Sharing and service providers

WakaGood shares information only as needed to operate the platform, comply with law, protect users, resolve disputes, enforce rules, or complete requested services. Service providers may support hosting, authentication, database operations, payments, payouts, rider eligibility checks, background-check workflows, document storage, communications, maps, routing, analytics, security, and support operations under appropriate data-protection obligations.

WakaGood does not sell personal information. WakaGood may disclose information when required by law, court order, valid legal process, safety needs, fraud prevention, business transfer, provider dispute, or to protect the rights, safety, and security of WakaGood, users, or the public.

Location privacy

WakaGood uses location to find nearby rides, calculate distance and ETA, support fare guidance, support navigation, verify arrival or trip progress, and let matched passengers track rider approach before pickup. Location accuracy depends on device settings, browser permissions, network state, GPS signal, and provider data.

• Passengers can type pickup and destination addresses or use current location when permission is granted.
• Riders share live location while active, approaching pickup, arrived, or performing an accepted ride.
• Passenger request maps are intended to load real map tiles only after pickup and destination are entered.
• Matched approach maps are intended to reuse loaded tiles and show rider movement to pickup without refreshing the whole map every second.
• WakaGood may use map kill switches, tile limits, caching, and fallback maps to control cost and protect reliability.

Payment and financial privacy

WakaGood uses payment and payout providers to collect cards, create payment references, process completed-ride charges, support refunds, manage rider payout readiness, and handle rider access or subscription billing where enabled. WakaGood stores provider references and status values needed to operate the service, not full card numbers or card security codes.

Financial records may be retained for accounting, tax, chargeback, fraud prevention, dispute, provider, and legal obligations. Riders remain responsible for their own tax filings and business expense records unless a specific law or written WakaGood program says otherwise.

Support, safety, and dispute records

WakaGood may review ride details, location history, fare proposals, payment references, support tickets, safety reports, messages, ratings, documents, notices, and diagnostic events to resolve problems, investigate misconduct, verify claims, protect users, and enforce platform rules.

Retention and deletion

WakaGood keeps records for as long as needed for rides, payments, tax and accounting obligations, safety investigations, dispute resolution, legal compliance, fraud prevention, security monitoring, support, and service reliability. Some records may be retained longer when required by law, provider requirements, accounting needs, active disputes, safety incidents, or abuse prevention.

When information is no longer needed, WakaGood aims to delete, anonymize, aggregate, or restrict it according to retention rules, provider limits, backup cycles, and legal requirements.

Security

WakaGood uses layered access controls, provider-hosted payment collection, server-side eligibility checks, private document storage, masked contact, audit logs, security monitoring, protected configuration, and limited public app surfaces. No system can be guaranteed completely secure, but WakaGood designs the platform to reduce unnecessary collection, narrow access, and protect sensitive information.

Operations access and audit

Authorized operations users may review account, ride, payment, support, safety, compliance, and diagnostic records when needed to operate WakaGood. Operator actions should be permissioned and auditable, and support access should be limited to the work being performed.

Your choices and rights

• You can update account and profile details in the relevant Passenger or Rider profile area.
• You can choose whether to grant browser location and notification permissions, subject to features that require those permissions.
• You can stop sharing live rider availability by deactivating rider availability.
• You can choose Negotiate before publishing if you do not agree with the no-negotiation fare displayed for a passenger request.
• You can contact WakaGood support to request access, correction, deletion, export, or review of your account information, subject to identity verification and legal, safety, accounting, dispute, fraud, or retention needs.
• You can unsubscribe from nonessential marketing messages where available. Transactional, safety, payment, ride, and account notices may still be sent.

Cookies, local storage, and device permissions

WakaGood may use browser storage, local storage, service workers, cache storage, cookies, and device permissions to keep users signed in, remember role state, support offline install behavior, cache static assets, reduce map cost, deliver notifications, and improve reliability. Clearing browser data or denying permissions may limit some features.

Children

WakaGood is not intended for children. Users must be old enough to create a binding account and, for riders, old enough to satisfy driving, licensing, insurance, background-check, and platform eligibility requirements.

Policy updates

WakaGood may update this policy as services, providers, service areas, laws, safety practices, or platform features change. Material changes should be posted in the app or on the website as appropriate.

Contact

Questions about privacy can be sent through WakaGood support inside the app or through the support contact channel published in the active WakaGood workspace.