Data Handling
Clear Summary of Stored Data
This page summarizes what we store, why we store it, and how you can ask for deletion. It is written as a practical companion to the privacy policy and POPI notice.
| Data Type | Why We Store It | Examples |
|---|---|---|
| Account data | Authentication, verification, and account support | Name, email, phone, password hash, email verification records |
| Planning data | Save tool inputs and progress between sessions | Budget, debt, retirement, tax calculator values, learning progress |
| Operational submissions | Respond to user requests and schedule sessions | Contact form entries, booking records |
| Security and audit data | Protect accounts and prevent abuse | CSRF tokens, rate-limit logs, consent event logs, IP/user-agent metadata |
| Document vault metadata | Manage member file uploads and secure retrieval | Original filename, file type, upload timestamp, owner linkage |
| Membership and payment records | Reconcile an optional checkout and determine account access | Plan, amount, currency, reference, payment state, period and redacted gateway identifiers |
| Browser preferences | Remember colour theme, tour state, and tool display preferences on this browser | Theme, generic message/tour state, tool display mode, and last-saved time; saved financial payloads remain in account storage |
How to Make a Privacy Request
If you have an account, sign in and use Privacy requests. Submission requires your current password and records only the request type, not a free-text copy of your financial information.
You may also email zane3rskine@gmail.com. Do not send passwords, identity numbers, documents, or financial values by email. We verify identity before processing and review what can be corrected, provided, deleted, anonymised, or must be retained.