Privacy publication gate
A privacy policy needs operating facts, not placeholder language.
This review surface records the policy sections and product facts that must be approved before Clarient publishes a privacy policy. It is intentionally not presented as the final legal policy.
Entity and contact details
The final policy must identify the responsible legal entity, applicable trading names and a monitored privacy contact. Those facts are not yet approved and are not invented here.
- Legal entity and ABN or other required identifier
- Registered or service address where required
- Monitored privacy contact and escalation owner
- Effective date and version owner
Information collected and why
The policy must map each public and product intake to its purpose, required fields, optional fields and source. The collection notice shown at the point of entry must agree with this policy.
- Walkthrough and purpose-routed contact details
- Account, company and authorised-user records
- Investor questions, follows, preferences and relationship records
- Provider connection, delivery and activity records
- Security, abuse-prevention and audit information
- Analytics events only when the approved measurement configuration is enabled
Use, disclosure and connected services
The final text must distinguish Clarient's own use from information handled on a customer's instructions and explain which connected services receive information for an approved purpose. It must state the actual provider and overseas-disclosure position rather than rely on a generic cloud-services clause.
Provider readiness and customer approval are product states. A disconnected or preview service must not be described as if information is already being sent through it.
Security, retention and deletion
The policy must align with implemented access controls, encryption boundaries, logs, backups, retention schedules and deletion or de-identification procedures. No hosting-region, certification or absolute-security claim is made until evidence is approved.
OAIC Australian Privacy PrinciplesAccess, correction and complaints
The final policy must explain how a person can request access or correction and how a complaint is handled. The Contact page already separates correction and privacy purposes in the interface, but those routes stay closed until monitored owners, fallback handling and response procedures are approved.
The process must not force a person to use a sales route or provide unrelated company details to exercise a privacy right.
Need to review the privacy workflow?
Use the privacy purpose on Contact after the monitored owner and legal text are approved.