Driver privacy

RYDCAST Driver Privacy Policy

Version: 2026-07-09

The RYDCAST service for South African businesses is provided by RYDCAST South Africa (Pty) Ltd. The RYDCAST platform technology is developed and licensed by CastTech Inc. RYDCAST™ and the RYDCAST logo are trademarks of CastTech Inc.

This policy explains what driver, vehicle, device, proof, wallet, and payout data RYDCAST stores.

1. Who Controls the Data

RYDCAST South Africa (Pty) Ltd is the responsible party/controller for driver account, device, vehicle, proof-of-play, wallet, payout, safety, support, security, operator, and compliance records in South Africa. CastTech Inc. develops and licenses the RYDCAST platform technology.

RYDCAST may use processors and service providers to operate the app, database, hosting, media-player delivery, mapping, payments, messaging, support, telemetry, security, and audit systems.

2. Account Data We Store

We collect and store your name, contact details, password hash, profile type, account status, login/session activity, consent history, support messages, operator actions, account notes, and security events.

Passwords are stored as PBKDF2-SHA256 hashes. Session tokens are stored as hashes.

3. Device and Vehicle Data We Store

We collect device fingerprints, installation type, operating system, app version, media-player session IDs, display/screen state, playback state, vehicle registration, vehicle class, make/model, pairing records, and device or vehicle status.

We use this to confirm that campaign payloads, proofs, and payouts are linked to the correct participant, device, and vehicle chain.

4. Location, Route, and Proof Data

When earning mode, campaign sync, media playback, QR, or proof validation is active, RYDCAST may process timestamps, GPS or proximity evidence, geofence matches, route context, campaign IDs, proof IDs, playback status, proof quality scores, QR sessions, screen/display telemetry, and hashed or pseudonymous driver/device identifiers.

This data is needed to verify whether an advert was eligible, delivered, billable to the advertiser, and payable to the driver.

5. Media-Player Audience Measurement

RYDCAST media players may locally estimate broad rider audience signals, such as age band, gender band, and whether the screen was viewed, only when a reviewed local detector is enabled to choose eligible adverts and report aggregate campaign performance.

RYDCAST does not identify riders, store face images, store faceprints, store biometric templates, or give advertisers individual viewer records.

Age-restricted adverts must not play when rider age is unknown, likely under 18, or too low-confidence for the configured threshold.

6. Wallet and Payout Data

We store wallet balances, proof-linked earnings, payout ledger rows, payout batch references, reversals, adjustments, payment support notes, tax or compliance references where required, and reconciliation records.

This data is used to calculate payouts, resolve disputes, keep audit records, and reconcile advertiser billing with driver earnings.

7. How Data Is Used

RYDCAST uses driver data to create and secure accounts, pair devices and vehicles, deliver campaign payloads, validate proof-of-play, calculate wallet credits and payouts, prevent fraud, investigate disputes, support drivers, manage safety, operate dashboards, improve reliability, and comply with law.

8. Data Is Not Sold

RYDCAST does not sell driver personal information, contact details, precise route records, vehicle registrations, payout records, proof records, or device data to advertisers, brokers, or unrelated third parties.

RYDCAST may use aggregated or de-identified platform metrics for operations, route planning, pricing, fraud prevention, reliability, investor reporting, and partner reporting, but those reports should not identify a driver unless a lawful dispute, safety, fraud, insurance, tax, or regulator process requires it.

9. Limited Sharing

RYDCAST shares driver data only where needed for the platform or where law allows or requires it. This may include:

Advertiser proof reports should use aggregated, limited, or pseudonymous driver/device references unless a lawful reason requires more detail.

advertisers, through limited proof and billing reports;
RYDCAST operators, for support, compliance, fraud, safety, and payout workflows;
processors such as hosting, storage, payment, mapping, moderation, telemetry, messaging, security, and support providers;
regulators, courts, law enforcement, tax authorities, insurers, and safety bodies where legally required or necessary;
fleet operators or vehicle owners where the account, vehicle, payout, or contract relationship requires it.

10. Storage, Security, and Access

Driver records are stored in the RYDCAST platform database and related operational systems. Access is limited to platform workflows, operators, processors, and audit users who need it for legitimate platform purposes.

RYDCAST uses technical and organisational controls appropriate to the data, including password hashing, session-token hashing, access controls, audit logging, and operational security checks.

11. Retention

RYDCAST keeps driver account, device, vehicle, proof, payout, consent, route, safety, support, and audit records while needed for the platform and afterwards for billing, tax, fraud prevention, dispute resolution, security, and legal obligations.

When records are no longer needed, RYDCAST deletes, de-identifies, or archives them according to retention and backup controls.

12. Your Rights

Subject to law, you may request access, correction, deletion, restriction, objection, export, or withdrawal of consent where consent is the legal basis.

Some records must be retained where needed for contracts, payouts, tax, safety, proof-of-play, fraud prevention, disputes, insurance, regulatory obligations, or legal compliance.

13. Marketing and Service Messages

RYDCAST may send account, safety, payout, campaign, device, security, and service messages.

Direct marketing is sent only where allowed by law, consent, or an existing relationship, with a stop or unsubscribe method where required.

14. Cross-Border Processing

Some processors or infrastructure may operate outside your country. Where driver data is transferred internationally, RYDCAST uses contractual, technical, organisational, or legal safeguards appropriate to the destination and purpose.

15. Complaints and Updates

RYDCAST may update this policy as the app, media players, processors, campaign rules, or laws change. You can contact RYDCAST support to exercise privacy rights or complain to the relevant regulator, including the South African Information Regulator where applicable.