Minimum necessary
Collect less
Use only the fields needed for the agreed purpose. Do not copy diagnoses, support narratives or Kooee reasons into general notes, analytics, tickets or logs.
Provider responsibilities
Privacy by design
Current permission
Access is temporary
A current assignment, relationship, purpose and permission are required each time. Historical access ends when authority is revoked unless a separately approved record rule applies.
Young person's choices
Consent is not one checkbox
- Explain each purpose before asking.
- Make “Not now” as easy as “Share”.
- Offer accessible supported decision-making.
- Do not infer incapacity from age or disability.
- Record and act on withdrawal or dissent.
Participant rights
See, fix and ask to delete
- Use a verified and accessible request pathway.
- Provide information in the requested practical format.
- Correct inaccurate, outdated or misleading information.
- Explain any lawful refusal or required retention.
- Provide independent privacy-complaint options.
Current product boundary
Do not add without a new PIA
- Precise location, contacts, microphone, camera or biometrics
- Advertising IDs, targeted advertising or behavioural profiles
- AI training, inferred diagnoses or automated risk scoring
- Public profiles, strangers or open text/media messaging
- Exports of supposedly de-identified participant data
LP-05 publication-ready staging
Privacy notice and rights pathway
- Entity: Kooee Tech Pty Ltd
- Privacy contact: Frank Sunthorn — frank@kooee.tech
- Notice version: PP-01 (dated 10 September 2026)
- APP 1: transparent purpose, categories, legal basis and contact disclosure published for the staged notice.
- APP 5: collection-notice scope and retention window stated before any active choice.
- APP 11: deletion pathway includes lawful-hold exceptions and retention explanation.
- Rights targets: acknowledge in 2 business days, progress update within 10 business days, final decision within 30 days where feasible.
- Escalation: ownership transfer and alternate privacy owner path are pre-published in the route’s companion workflow text.
If information is lost or exposed
Treat it as an incident immediately
Protect the young person, contain access, preserve minimum evidence and notify the privacy/security incident owner. Assess whether the event is likely to cause serious harm and whether people and the OAIC must be notified. Never place the incident narrative in an ordinary support queue.
Open incident guidanceThe complete PIA and data inventory remain subject to independent Australian privacy and child-safeguarding review.