Privacy notice.

This notice uses POPIA-aware principles but does not claim legal compliance. It describes the current implementation and its limits.

What we collect

After payment is verified, the secure intake asks for identity and contact details, target role, career level, industry, CV or work-history content, achievements, search preferences, deadlines and optional links or notes. Payment records retain a reference, payer name and email, product, amount, currency and verification status. The service also stores a user-agent string and may store a one-way salted hash of the connection address when a secret salt is configured; otherwise that hash is not created. Basic visit and conversion analytics use a random session identifier, landing/referrer details, campaign parameters and device category.

Purpose and minimisation

Information is collected for payment matching, CV or job-search delivery, customer contact, security, troubleshooting and aggregated service measurement. Do not submit identity numbers, banking credentials, medical information or other information not needed for delivery. Card and banking details are entered only in encrypted checkout and are not requested by this site.

Access and handling

Intake and payment records are stored in the service database and may be sent to the delivery queue. Access should be limited operationally to people supporting delivery and security. The code does not currently implement field-level encryption for stored intake text, an access-request portal, or a customer-facing export endpoint.

Retention and deletion

A fixed automated retention or deletion schedule is not currently enforced in code. Records remain until an authorised operational deletion is completed. You may request access, correction or deletion through the service contact channel supplied after purchase. Some payment or transaction records may need to be retained where required for accounting, dispute or legal purposes.

Safeguards and limits

The implementation uses verified-payment gating, same-origin form checks, payload limits, bot screening when configured, one-way hashing for connection addresses when configured, and no-store responses for verification pages. No online system can promise absolute security.

Changes and questions

This notice should be reviewed whenever storage, integrations or operating procedures change. Last updated: 28 July 2026.