Privacy Policy

We may store account details, contact information, order and invoice records, payment status records, support tickets, chat transcripts, verification workflow records, service metadata, usage and security logs, abuse reports, and audit records.

Security logs may include hashed IP address, hashed user agent, timestamps, login events, failed login events, service actions, payment events, and service usage indicators needed to protect the platform. Blog views should store hashed IP and hashed user-agent values rather than raw visitor identifiers.

We do not store card numbers, banking passwords, wallet recovery phrases, private wallet credentials, or customer desktop contents. User passwords are protected and are not stored as plain text.

Customers should never send recovery phrases, private payment details, identity documents, banking details, or private files through public chat, blog comments, or unsecured support messages unless specifically requested through an approved verification workflow.

Our privacy controls are designed around POPIA and EU data protection principles, including purpose limitation, data minimization, access control, security safeguards, correction rights, retention control, and lawful processing.

Customers may request access, correction, or deletion where legally and operationally possible. Some records may need to be retained for tax, fraud prevention, security, billing, abuse handling, legal defense, or service compliance.

Information is used to deliver services, verify payments, provide support, prevent fraud, detect abuse, monitor availability, create audit records, investigate incidents, and meet operational security requirements.

Internal notes and sensitive operational details are kept separate from customer-visible updates unless specifically written for the customer timeline.

We do not sell personal data. We do not share personal data for unrelated marketing resale.

Data may be shared with payment processors, service partners, email delivery services, support systems, legal/accounting providers, fraud prevention services, or infrastructure vendors only as needed to operate and protect the service.

We respond to data requests only when required by valid legal process, such as a court order, subpoena, warrant, or lawful authority request. We review requests before disclosure and only provide data within the valid scope of the request.

Retention periods should follow legal, tax, fraud-prevention, service, and operational recovery requirements.

Customers should contact support or the published data protection email to request access, correction, restriction, portability where applicable, or deletion where legally and operationally possible.