How long FounderZA retains each category of personal information.
This schedule sets FounderZA's normal retention periods. FounderZA keeps personal information only while a lawful operational, contractual, security, evidential or statutory purpose requires it. A legal hold, unresolved complaint, security incident, tax requirement or active dispute may require a longer period for the affected records. When the reason ends, the record is deleted, de-identified or restricted.
| Record category | Normal retention period | Reason and end action |
|---|---|---|
| Active account and profile | While the account is active | Needed to provide the account and selected services. Delete or separate retained records when the account closes. |
| Closed account operational copy | 30 days after confirmed closure | Allows FounderZA to complete closure, correct an accidental request and separate records that must be kept for another lawful reason. Delete or de-identify after 30 days unless an exception applies. |
| Public and subscriber profile content | While published, then 30 days | Allows removal, correction and closure administration. Search or cache copies are removed through the normal technical cycle. |
| Business listings | While active, then 3 years after withdrawal or closure | Supports complaint handling, publication history and defence of claims. Restricted after withdrawal and deleted or de-identified when the period ends. |
| Verification result and reference | While the account is active, then 2 years | Supports fraud prevention, review and proof of the check. Raw biometric capture is not retained by FounderZA unless necessary, lawful and separately disclosed. |
| Company, mandate and authority evidence | While relied upon, then 3 years after the authority or related account ends | Supports proof of permission and investigation of disputed actions. |
| Signed NDA, completion certificate and signing evidence | 5 years after the last disclosure or the end of related access, whichever is later | Supports enforcement, defence and proof of electronic signature. Retain longer only for a legal hold, dispute or surviving legal obligation. |
| Confidential access request, decision, scope, expiry and revocation | 5 years after access ends | Links the disclosure decision to the recipient, documents and agreement or direct-access acknowledgement. |
| Confidential files uploaded by an owner | Until the owner deletes them, the listing ends or the service closes | Remove from active access promptly. Protected backup copies follow the normal backup cycle, targeted at no more than 90 days unless a legal hold applies. |
| Messages and enquiries | 3 years after the conversation closes | Supports user history, complaints and dispute resolution. Longer retention requires a documented reason. |
| Orders, invoices, payment, refund and reconciliation records | 5 years after the transaction or longer where tax law requires | Supports accounting, tax, refunds, chargebacks and transaction records. |
| Company accounting records | 7 years | Supports Companies Act and accounting recordkeeping. |
| Security, login and document-access logs | 24 months | Supports security monitoring, incident response and proof of access. Restrict and retain an incident subset longer while an investigation or claim is active. |
| Support tickets and ordinary complaints | 3 years after closure | Supports follow-up, service quality and dispute evidence. |
| Privacy, PAIA and regulatory requests | 5 years after closure | Supports proof of statutory handling and decisions. |
| Marketing consent, source and objection | While relied upon and for 5 years after the last relevant communication or objection | Proves the communication basis. Keep the minimum suppression record while needed to honour an unsubscribe or objection. |
| Cookie choices | For the duration shown in the live cookie register | The actual cookie register controls. Optional choices must not be retained longer than their stated duration. |
| De-identified or aggregated research information | While useful for the documented research purpose | Must not reasonably identify a person. Review periodically and delete when no longer useful. |
| Backups | Normal rolling cycle, targeted at no more than 90 days | Backups remain protected and are not restored for ordinary use after a deletion request except for disaster recovery, followed by reapplication of deletion controls. |
The 30-day account-closure period is an operational buffer, not permission to continue using the account for marketing or marketplace activity. Access ends according to the closure decision. During the buffer, FounderZA separates statutory and evidential records from data that can be deleted. A valid urgent deletion request is completed sooner where there is no lawful reason to retain the information.
The separate 30-day period in ECTA section 44 is the outer deadline for paying a qualifying cooling-off refund after cancellation. It is not a data-retention rule and does not extend the account-closure period.
The Information Officer reviews this schedule at least annually and when material processing changes. Deletion jobs, backup expiry, legal holds and manual exceptions are recorded. A user may ask which period applies through the Privacy Notice contact route.