POPIA Policy

Responsible processing purposes

• Account creation, login security, role management and dashboard access.
• Customer and worker verification before high-risk booking or job actions.
• Booking creation, job matching, worker status updates and customer completion confirmation.
• Paystack payment verification, transaction logs, refunds, wallet ledger records and withdrawal review.
• Support tickets, disputes, safety reviews, audit logs and fraud prevention.
• Legal, tax, accounting, regulatory, platform security and recordkeeping duties.

Collection limitation

The platform should collect personal information directly from users where practical and only where the information is needed for a legitimate platform purpose. Verification, payment, booking and support records should not be collected for curiosity, unrelated marketing or unnecessary profiling.

Information quality

Users must keep their account, contact, address, worker skill, availability, payout and verification information accurate. Admins may request corrections or re-upload of documents when records are incomplete, expired, unclear or inconsistent.

Openness

The platform explains important processing through the Privacy Policy, POPIA Policy, terms, verification consent, payment and payout policy, support processes and admin settings. Users can contact support for privacy questions, access requests, correction requests or deletion requests.

Security safeguards

• Role-based access is used for admin, finance, verification and support functions.
• Private documents are protected from public access and should be viewed only through controlled admin access.
• Sensitive document views, status changes and admin decisions can be recorded in audit logs.
• Forms use validation, CSRF protection, rate limits and file upload restrictions where configured.
• Payment references and webhook records are stored for finance review, but card details are handled by Paystack-supported payment flows.

Data subject participation

Users may request access to their personal information, correction of inaccurate information, deletion or destruction of information no longer authorized for retention, or objection to certain processing where POPIA allows. The platform may need to verify the requester's identity before responding.

Retention under POPIA

Some records must be kept even after a user asks for deletion. Examples include tax records, transaction evidence, booking disputes, fraud prevention logs, safety incident records, legal claims, audit logs and worker payout records. Records should be deleted, destroyed or de-identified when there is no longer a lawful reason to keep them.

Security compromise response

If a confirmed security compromise affects personal information, Joy Domestic Services should investigate, reduce harm, preserve evidence, notify affected users where required and follow applicable Information Regulator processes.

Complaints and contact

Users should first contact support@joydomesticservices.com or use platform support. POPIA-related complaints can also be raised with South Africa's Information Regulator where the law allows.