• Home
  • Security & Privacy
  • How MayaAI handles patient information, supports your clinic's privacy obligations and keeps administrative assistance separate from clinical judgement.

    ISO 27001 certified

    Information security management

    APP compliant

    Australian Privacy Principles

    Encryption at rest

    Encrypted connections for data in transit

    Stored in Australia

    Platform data, recordings and transcripts

    Personal information collected

    The information involved depends on your clinic's configuration, the caller's enquiry and the services being used.

  • Caller identity and contact details needed for the enquiry or appointment workflow.
  • Appointment information, messages and information a caller provides, which may include sensitive health information.
  • Call metadata such as the date, time and duration; transcripts and recordings where enabled.
  • Practice contact details, service preferences, billing information and support communications.
  • Website enquiry information and usage information described in our Privacy Policy.
  • Clinic instructions should limit collection to what is necessary for the administrative task. Our Privacy Collection Notice explains collection and privacy rights.

    Purpose and permitted use

    MayaAI uses information to deliver configured reception workflows: answer routine enquiries, manage appointments, take messages and route calls to the practice. Information is also handled for service administration, support and purposes described in our Privacy Policy.

    Practices remain responsible for approving their workflows and ensuring collection, use and disclosure are permitted under applicable law. A caller providing health information does not authorise unrelated uses.

    Patient data is not used to train AI models. This is covered in our data processing agreement.

    Data storage, processing and encryption

    Platform data, call recordings and transcripts are stored in Australia. Data is encrypted at rest and transmitted over encrypted connections. Encryption controls also apply to data processing.

    Australian storage does not mean all processing or access occurs only in Australia. Our Privacy Policy describes circumstances in which third-party providers may access or receive information overseas.

    For a review of processing locations and the encryption controls relevant to your proposed workflows, contact our team before deployment.

    Retention and deletion

    Our Privacy Policy states that personal information is kept only as long as needed for the purposes of collection or as required by law. When it is no longer needed, it is securely destroyed or de-identified.

    Clinics choose whether to store call recordings. That choice is separate from retention of transcripts, appointment information and other records.

    Before onboarding, request the retention and deletion arrangements applicable to your practice, including recordings, transcripts, backups and any legal retention requirements. A single fixed retention period or backup-deletion deadline is not specified on this page.

    For access, correction or deletion enquiries, email human@mayaai.com.au. Deletion requests may be subject to legal record-keeping obligations.

    Third-party providers and subprocessors

    Delivering the service can involve third-party providers and connections to your clinic's practice management system. Our Privacy Policy explains the categories of recipients and overseas disclosure arrangements.

    For provider and subprocessor information relevant to your clinic, including the purpose of access and applicable locations, contact our team as part of your vendor assessment. Australian data storage alone is not an assurance that every provider operates solely in Australia.

    Access controls and authentication

    Our Privacy Policy describes access controls based on job requirements. Authentication and access permissions are distinct from encryption: encryption protects data, while access controls govern who may use it.

    During your security review, request the authentication options, user permissions and access-management arrangements applicable to your clinic. This page does not assert a specific multi-factor authentication, single sign-on or audit-log configuration.

    Call recording, disclosure and consent

    Each clinic decides whether call recordings are stored. If your clinic chooses to store recordings, it must announce recording before recording begins.

    The practice is responsible for the wording of the notice and for meeting applicable consent and recording-law requirements. An announcement should not be treated as a substitute for consent where consent is legally required.

    Agree how callers who do not wish to be recorded will be handled before enabling recording. Turning off recording storage should not be assumed to remove transcripts or other call records.

    Maya identifies herself as an AI assistant on every call. AI disclosure and recording disclosure are separate requirements.

    Human escalation and operational safeguards

    Maya's role is administrative and patient communication: routine enquiries, appointment workflows, messages and clinic-directed call routing. Maya does not provide clinical diagnosis, medical advice or replace clinical judgement.

    What Maya recognises and how she responds depends on the instructions and policies approved by your clinic. Practices define their own rules for transferring calls to staff and handling enquiries outside those instructions.

    Maya is not an emergency service. Callers describing a medical emergency are directed to call 000. Each practice defines its own rules for escalating urgent calls to its team.

    Onboarding is clinic-specific: agree requirements, configure the assistant, connect the practice management system and phone number, then use a phased rollout with review and improvement.

    Incidents and breach notification

    Report suspected security incidents or privacy concerns to human@mayaai.com.au. Avoid sending patient records or other sensitive information in your initial email.

    Before going live, request the incident-response arrangements applicable to your service: reporting contacts, assessment and containment responsibilities, clinic communication and notification procedures.

    Where the Australian Notifiable Data Breaches scheme applies, eligible data breaches require notification to affected individuals and the Office of the Australian Information Commissioner. Not every incident is an eligible data breach; applicable legal thresholds must be assessed.

    This page does not promise a specific incident-response or notification timeframe.

    Australian privacy obligations and certification

    Legal compliance — Australian Privacy Principles

    MayaAI is APP compliant and designed to support practices' obligations under the Australian Privacy Principles. Each practice remains responsible for how it configures and uses the service, including obligations under the Privacy Act 1988 and applicable state or territory health privacy and recording laws.

    Independent certification — ISO 27001

    MayaAI is ISO 27001 certified. ISO 27001 concerns information security management; it is not a clinical certification or a substitute for a practice's legal compliance obligations.

    Internal policies

    Our Privacy Policy, collection notices and data processing agreement describe information handling. Clinic-approved instructions govern administrative workflows and escalation.

    Technical controls

    Encryption at rest, encrypted connections and access controls protect information. These controls are distinct from certification and do not remove the need for appropriate collection, consent and use.

    Read our Privacy Policy, Privacy Collection Notice and Terms of Service.

    Security and privacy enquiries

    Need a vendor security questionnaire completed or information for your practice's privacy review? Email human@mayaai.com.au.

    Published by Nutire Pty Ltd (ABN 55 671 343 856), the operator of MayaAI. Last reviewed 14 October 2026.