Access-to-records readiness.
Before live portfolio data is accepted, TrustSavi must publish the right PAIA and Information Officer particulars.
Name the accountable route.
TrustSavi must register and publish an Information Officer route before accepting live portfolio data.
The PAIA manual must identify records, request routes, forms, fees, contacts, and available categories.
Access, correction, deletion, objection, and complaint requests must be routed through a controlled process with identity verification, logging, response tracking, and escalation to the Information Officer.
Live portfolio processing needs a retained impact assessment covering purpose, safeguards, retention, deletion, transfers, and residual risk.
What must be visible.
- Full registered name and registration number.
- Physical address, service address, telephone number, and email address.
- Information Officer name or role, registration status, and privacy request contact route.
- PAIA manual access route and request forms.
- Complaint route and escalation process.
- Material operators, processors, or service-provider categories used for live portfolio information.
If these particulars are not published, treat the site as a preview. Do not submit live portfolio data through it.
Use a controlled route.
- Request access to personal information or records required for the exercise or protection of rights.
- Request correction, deletion, or destruction of personal information where the law permits.
- Object to processing where POPIA allows objection.
- Raise a privacy, data-handling, or security concern.
- Ask for the current PAIA manual or prescribed request forms.
Until a dedicated PAIA and privacy contact is published, use the agreed engagement channel. Do not send live files, identity documents, passwords, keys, tokens, or special personal information informally.