Our safeguarding boundaries
What Yindi does for any call involving a child.
Does not engage substantively with student callers
Callers who identify as students are politely directed to the appropriate staff member, not handled by the AI.
Escalates any wellbeing or safety concern immediately
Any mention of safety, harm, distress, abuse or wellbeing goes straight to your designated staff (Child Safety Officer, principal, or wellbeing lead per your policy) — never handled by Yindi. Safety information is offered where appropriate (Kids Helpline 1800 55 1800, Lifeline 13 11 14).
Never discusses individual student information
Not with any caller whose identity hasn't been verified through your school's standard process.
Operates within your child-safety framework
Configured with your school during onboarding, around your existing policies and escalation paths.
What Yindi does NOT do
Compliance you can verify
The standards we work to.
Child Safe Standards
Yindi's configuration supports your obligations under the National Principles for Child Safe Organisations and state-based Child Safe Standards (e.g. Victorian Child Safe Standards under Ministerial Order 1359; the NSW Child Safe Scheme).
Mandatory reporting
Yindi does not replace any mandatory reporting obligation. Any disclosure indicating potential harm to a child is escalated immediately to your designated child safety officer, who handles it under state mandatory-reporting laws.
Privacy Act 1988 (Cth) & the APPs
Yindi handles personal and student information in line with the Privacy Act and the Australian Privacy Principles, administered by the OAIC. Student information is treated as sensitive information.
Australian data residency (stated precisely)
Call recordings and transcripts are stored onshore in Australia — in Melbourne, with AWS Sydney backup. Voice and language-model processing is performed by specialist providers that may process data outside Australia (United States and/or European Union). These sub-processors are disclosed in our Privacy Policy. We tell you exactly what stays in Australia and what doesn't — rather than implying everything does.
This is general information, not legal or compliance advice. Schools should verify their obligations with their Child Safety Officer, principal, and the relevant regulator (e.g. the VRQA, the NSW Office of the Children's Guardian, or their Department of Education). Full detail on data handling is in our Privacy Policy.
Why Yindi is different
More than a generic AI receptionist.
Part of your phone system — not a forwarded number
Yindi runs on your school's existing phone infrastructure, set up by Zero3 Communications, with 35+ years installing phone systems in Australian schools. It's built into your phone system, not a separate AI service you forward calls to.
Keeps answering when your phones go down
If your line, internet or phone system becomes unavailable, calls can fail over to Yindi so absences are still logged and parents still get through — even during an outage. A forwarded-number service goes dark with the line.
Built for the daily absence rush
Yindi is built for the busy morning absence period — collecting absence details and handing them to your office, ready for the system you use. You control when it answers: on demand, after hours, as overflow, 24/7, or as outage backup.
Australian-built, hosted and supported
Built and run in Australia, supported by an Australian team. Founders Jason and Mark, Melbourne.
How your data is handled
Clear about what stays in Australia.
Stored onshore
Call recordings and transcripts are stored in Australia — Melbourne, with AWS Sydney backup.
Overseas processing, disclosed
Voice and language-model processing is handled by specialist providers that may process data in the US and/or EU. We disclose these sub-processors rather than imply everything stays onshore.
Encrypted & access-controlled
Data is encrypted in transit and at rest, and access is controlled and logged.
You are the data controller
Yindi captures information on your school's behalf and hands it to your authorised staff and systems.
Retention & deletion
Schools can request deletion of call data; retention periods are set to your needs.
Our full sub-processor list and data practices are set out in our Privacy Policy.
Common questions
Child safety & data, answered.
Will Yindi interact with student callers?
No. Student callers are politely directed to qualified staff. Yindi is configured for adult callers — parents, staff, suppliers and contractors.
How does Yindi handle safeguarding concerns?
Any mention of safety, harm, distress or wellbeing is escalated immediately to your school's designated staff. Yindi does not handle the concern itself, and provides safety information where appropriate (Kids Helpline 1800 55 1800, Lifeline 13 11 14).
Does Yindi work with our student information system?
Yindi works alongside whatever system your school runs — Compass, Sentral, XUNO, CASES21 or TASS. It sits in front of your phones, captures the absence or message, and sends it to your office ready to enter into your system. Direct write-back integrations are on our roadmap.
Where is our data stored?
Call recordings and transcripts are stored onshore in Melbourne, with AWS Sydney backup. Voice and AI processing is carried out by specialist providers that may process data overseas (US/EU); these are disclosed in our Privacy Policy. Data is encrypted in transit and at rest, and access is controlled and logged.
Does Yindi discuss individual student information?
No — not with callers whose identity hasn't been verified through your school's standard process.
Does Yindi make decisions about students or enrolment?
No. It captures information and passes it to your staff to action. It does not assess or approve anything.
What happens if our phone system goes down?
Calls can fail over to Yindi so absences are still logged and parents still get through during an outage — this is our Redundancy capability.
Is Yindi Australian?
Yes — built, hosted (call records onshore in Melbourne with AWS Sydney backup) and supported in Australia.
When Yindi might not be the right fit
If you want an AI to handle student welfare conversations directly, Yindi isn't it — by design, it escalates those to your staff and never counsels students itself.
And we'll always tell you the current status of an integration rather than imply one exists. If your school depends on automatic write-back to a specific system today, ask us where that integration is up to before you commit.