1. Purpose and available rights
This page tells you how to access, correct, export or delete data; object to eligible uses; withdraw consent; close an account; and understand records we may lawfully retain. It implements relevant rights under Malawi's Data Protection Act, 2024 and applies alongside our Privacy Policy. RYDZ cannot avoid these rights by merely terminating an account or calling a record anonymous.
2. How to submit a request
Send an email to support@rydzmw.com with subject Privacy / Account Deletion Request, or, for deleting a rider account, use the in-app route described in section 5. State whether you seek access, correction, portability, withdrawal of consent, erasure, restriction, objection, account closure or an explanation. Include only information needed to locate your account and verify identity. Do not email your password, PIN or OTP. We may ask for proportionate proof when the request exposes personal information or relates to money, but we will not demand unnecessary identity scans. The apps do not currently offer a self-service data export; copies of your data are provided on request.
3. Access, portability and correction
Eligible requests to access data and obtain a copy will be handled within legally required periods, including the Act's general 30-day access provisions. The Act also contains 30-day portability and 14-day correction provisions where their conditions apply. We will describe the categories and purposes of data, appropriate recipients and other transparency information. A person requesting information about another passenger or driver must demonstrate valid legal authority; a ticket purchaser does not automatically gain access to all a fellow passenger's personal information. Many profile details can also be corrected directly in the app.
4. Objection, restriction and withdrawal of consent
You may request restriction or object where permitted by law, including to qualifying direct marketing. Consent for optional promotional messages or other consent-based processing may be withdrawn prospectively, for example by switching off "Offers and promotions" in the app's notification settings; necessary service messages and records required for a lawful booking may continue on their independent legal basis. Location permission can be changed in device settings, which may prevent live tracking/dispatch. We will explain any legally valid reason a request cannot be fully met.
5. Deleting a user account
Riders can delete their account in the RYDZ app: open Settings and choose Delete account, then confirm. The account is deactivated and you are signed out straight away, and your in-app notifications are deleted. For 30 days you can change your mind: sign back in and choose to recover the account. After the 30 days, RYDZ permanently deletes the account; this is carried out by RYDZ staff, so it can happen some time after the 30-day period ends rather than at the exact moment it ends. Before deleting an account, use or ask about any remaining RYDZ Wallet balance and any unused tickets by contacting support@rydzmw.com.
Captains cannot yet delete their account in the RYDZ Captain app. To close a Captain account, email support@rydzmw.com with the subject Account deletion request from the email address or phone number registered on the account.
RYDZ authenticates the request, checks pending journeys, unredeemed tickets, disputes, refunds, wallet balance and legal holds, and explains any practical action needed before closure. We disable access after processing the request, remove data lacking an ongoing legal basis and instruct relevant processors to erase covered records where required. Closure does not extinguish valid tickets, lawful payment claims or accrued Captain/Operator earnings. Our legal obligations may require retention of transaction, tax, fraud or safety records for a justified period. When a rider account is permanently deleted:
| Deleted | Kept |
|---|---|
| The rider profile, including name, email address, phone number, photo, preferences and saved emergency contacts | Completed and cancelled ride records and payment transactions, for financial, tax and dispute purposes |
| The sign-in account, which ends every session | Ticket bookings, with the link to your account removed, for Operator and financial records |
| Rides that had not finished | A restricted deletion record: a copy of the profile as it was when deletion was requested, and an audit entry of the request |
6. Captain and Operator account closure
A Captain's account may include licensing, payout and incident information that needs a different retention period from ordinary passenger profile data. An Operator may be subject to obligations involving passenger manifests, tax and reconciled ticket reports. We will distinguish personal data of staff from business records and use minimization or de-identification when continuing retention is no longer necessary.
7. Retention schedule
RYDZ has not adopted fixed retention periods in years for most categories. The table below describes how each category is kept today; we do not invent obligations or claim a schedule that is not applied.
| Data type | Guiding principle | Current practice |
|---|---|---|
| Account/profile and device sessions | Account life plus lawful closure period | Kept while the account is open. A deleted rider account is recoverable for 30 days and then permanently deleted as described in section 5. |
| Precise GPS traces and dispatch events | Keep only for safety, incident resolution or verified operational need | Kept with the ride and usage records they belong to; no separate shorter period has yet been set. |
| Ride and ticket receipts, invoices, ledgers | Tax/accounting, consumer evidence, statutory duties | Kept, including after account deletion, for as long as needed for tax, accounting and disputes. |
| Captain ID, licence and vehicle documents | KYC, permits, safety; reduce copies after verification | Kept in private storage while the Captain account is active and handled on request when it is closed. |
| Payment and payout dispute evidence | Chargeback/statutory claim limits and fraud controls | Kept with the transaction records it relates to. |
| Complaints and serious incidents | Safety, insurance and legal requirements, restricted access | Kept with restricted access for as long as a safety, insurance or legal need remains. |
| Cookies, device logs and support tickets | Operational purpose, defined expiry | Website cookies expire as listed in the Cookie Policy. Error reports from the RYDZ Business app are deleted after 90 days. Support emails are kept in the support mailbox. |
| Encrypted backups | Cycled and purged via validated schedule | Backups follow the rotation of RYDZ's hosting provider; data removed from live systems disappears from backups as they expire. |
8. Legal holds, backups and third parties
An erasure request may be partially restricted by legal obligations, active legitimate disputes, statutory retention or other specific exemptions. We will explain the reason, extent and review route where lawful. Backup copies may expire through controlled rotations; active systems stop using data due for deletion. Shared passenger data may also be independently held by a carrier with a lawful retention duty; we will explain the separate Operator contact when relevant and assist appropriately.
9. Response, complaint and escalation
We will acknowledge requests, provide decisions within statutory deadlines and identify how to contest a refusal. Where necessary, a data subject may complain to the Data Protection Authority, https://www.dpa.mw (opens in a new tab), without losing access to competent courts. Contact: support@rydzmw.com, +265 222 247 247.