Privacy Policy
Your privacy and the security of your health information is our priority.
Last updated: 13 October 2026 | Version: 1.3 (draft for legal review)
Slay Pty Ltd (ABN 59 686 642 366) trading as PreConsult ("PreConsult", "we", "us", or "our") is committed to protecting your privacy and ensuring the security of your personal and health information. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our patient-information collection and clinical documentation service.
1. Scope of This Policy
This Privacy Policy applies to:
- Patients who use PreConsult to provide health information before medical appointments
- Healthcare practitioners who use PreConsult to receive and review patient information
- Healthcare organisations that subscribe to PreConsult services
- Visitors to our website and marketing materials
The healthcare organisation collects information for your care and maintains your medical record. Slay Pty Ltd receives and holds information to provide PreConsult and handles account, security and website information for its own stated purposes. Each entity is responsible for the privacy obligations that apply to its activities. Australian privacy law does not provide a general exemption for a service provider described as a data processor.
2. Information We Collect
2.1 Patient Health Information
When patients use our pre-consultation interview service, we collect:
- Identifying information: Name, date of birth, contact details, appointment information
- Health information: Symptoms, presenting complaints, medical history, current medications, allergies, family history, social history
- Demographic and optional registration information: Age, sex, language preferences, address, Indigenous status, Medicare and DVA details, private health fund details, emergency contacts and referring or usual practitioner details, where the clinic enables registration. Paper intake form scans may contain these details and other health information.
- Communication records: Chat transcripts, voice recordings and transcripts (if voice interview feature is used)
- Referral letters: Referral letters uploaded by the healthcare organisation, forwarded by email to the organisation's PreConsult referral address, or (where the organisation enables it) uploaded by the patient, together with details extracted from them, such as the reason for referral, medications, allergies, investigations and referral dates
- Forwarded emails: Appointment confirmation emails and referral emails (including attachments) that a healthcare organisation sends or forwards to its PreConsult email addresses
2.2 Practitioner and Organisation Information
For healthcare practitioners and organisations, we collect:
- Account information: Name, email address, professional credentials, organisation affiliation
- Authentication data: Login credentials, multi-factor authentication details
- Usage data: Session activity, features used, time spent reviewing patient information
- Preferences: Notification settings, clinical workflow preferences
2.3 Technical and Device Information
We automatically collect:
- Device information: Device type, operating system, browser type
- Connection information: IP address, referring URLs, pages visited
- Usage analytics: Feature usage, session duration, interaction patterns
2.4 Practitioner-Created Clinical Content
When practitioners use PreConsult to document their own clinical decisions, we collect:
- Decision Notes: The practitioner's typed or dictated shorthand describing their assessment and plan, the note written from it, and the approved version the practitioner copies into their clinical system
- Dictation audio and transcripts: Audio recorded when a practitioner dictates is sent for transcription and deleted from transcription storage once the transcript is returned; the transcript is kept as part of the note
- Letters: Letters drafted and finalised by practitioners, including replies to the practitioner who made a referral
- Details of referring practitioners: Name, practice, address and provider number of the practitioner who wrote a referral letter, used to check referral validity and to address reply letters
2.5 Website Visitors and Marketing Attribution
When you visit our marketing website, we collect:
- Visit information: Pages visited, landing page, referring site and approximate country (derived from your connection, not precise location)
- Campaign information: Campaign parameters in the link you followed (such as UTM parameters) and, if you arrived from a Google ad, the Google click identifier (gclid), used to measure which campaigns lead to signups
- Google advertising and analytics data: Only if you accept all cookies, the Google tag collects information about your visit for Google Ads conversion measurement and Google Analytics (see Section 11 and our Cookie Policy)
- Enquiries: Information you provide in contact forms, signup forms, demo bookings and the website chat assistant
3. How We Use Your Information
3.1 Primary Purposes
We use your information to:
- Facilitate pre-consultation health history collection through AI-guided interviews
- Provide structured clinical summaries to healthcare practitioners
- Extract details from referral letters and show practitioners whether a referral appears valid for Medicare purposes (an administrative check that practitioners and staff should confirm)
- Write up the practitioner's own stated assessment and plan as a note (Decision Notes), and draft letters, including replies to referring practitioners, for the practitioner to review and approve
- Suggest billing codes for practitioner review
- Enable secure communication between patients and healthcare providers
- Maintain and improve our patient-information collection and clinical documentation service
3.2 Secondary Purposes
With appropriate safeguards, we may also use information to:
- Maintain the service and investigate errors where permitted by privacy law
- Conduct quality assurance and clinical safety monitoring
- Develop analytics on clinical narrative trends and service improvement only with an established lawful basis and appropriate de-identification assessment; retained narratives are not assumed anonymous, and intake narratives alone do not establish diagnostic accuracy or treatment effectiveness
- Measure which marketing campaigns lead website visitors to sign up (website visitor data only, never patient or health information)
- Comply with legal and regulatory requirements
- Investigate software errors and security incidents affecting the service
3.3 What We Do NOT Do
- We do not sell, rent, or trade your personal or health information
- We do not use or share patient or health information for advertising or marketing. Google receives website visitor data for advertising measurement only if a visitor accepts all cookies on our marketing website (see Section 11)
- We do not use patient information to train AI models
- We do not make automated decisions that produce legal or similarly significant effects without human oversight
4. Legal Basis for Processing
For Australian users, collection of sensitive information ordinarily requires consent and reasonable necessity, unless an applicable legal exception permits it. Use and disclosure must have a basis under the applicable privacy and health-information laws. Contractual necessity, legitimate interests and vital interests are not independent Australian permissions to handle health information.
The clinic must establish a lawful basis for appointment feeds, referrals and staff uploads before sending them to PreConsult; later interview consent does not retrospectively authorise collection. Optional registration fields may be left blank and provided directly to the clinic. Indigenous status is sensitive information. Government identifiers may only be used or disclosed where an applicable APP 9 exception permits it; consent alone does not override APP 9.
5. Use of AI-Powered Services
5.1 How AI Is Used
PreConsult uses artificial intelligence, including large language models (LLMs), to:
- Conduct conversational health history interviews with patients
- Extract and structure clinical findings from patient responses
- Generate clinical summaries for practitioner review
- Extract details from referral letters, forwarded emails and uploaded appointment information
- Transcribe practitioner dictation (speech-to-text)
- Write up the practitioner's own stated assessment and plan (Decision Notes) and draft letters, intended to preserve the practitionerโs stated decisions and available source facts, subject to verification for AI errors or unsupported additions
- Suggest billing codes for practitioner review
PreConsult does not use AI to rank possible diagnoses or to recommend treatments. Clinical suggestions generated by earlier versions of PreConsult may remain visible, read-only, in records created before this change.
5.2 AI Processing Location
We use enterprise-grade AI language model services from leading providers. Depending on your location and the services you use:
- Australian users: By default, AI processing uses Anthropic Claude and Amazon Nova models through Amazon Bedrock in Australian AWS regions, and practitioner dictation is transcribed by Amazon Transcribe in the Sydney region
- US-hosted models: A healthcare organisation's account may be configured to use OpenAI models hosted in the United States. Where this applies to patient-facing features, patients are asked for consent before their interview starts
- Other regions: AI processing may occur in the United States or other jurisdictions with appropriate safeguards
- Website chat assistant: Messages sent to the chat assistant on our marketing website are processed by OpenAI in the United States
- Clinical Terminology: SNOMED coding via regional terminology servers, which receive clinical terms only and no patient identifiers
The interview notice explains AI use and possible overseas processing. SMS, email, voice and their downstream providers can involve overseas processing even when the language model is hosted in Australia. Ordinary AI consent is not a waiver of APP 8 safeguards or overseas-recipient accountability. Provider arrangements must be assessed for each enabled service; we do not use patient information for model training.
5.3 AI Data Use Commitments
- Your identifiable health information is not used to train AI models
- Provider retention, diagnostic logging, support access and deletion depend on the specific service and its contractual settings. Australian primary hosting does not establish zero retention or exclusively Australian processing
- All AI outputs are drafts or suggestions only and require practitioner review before clinical use; practitioners must review and approve documentation before clinical use, copying or export; PreConsult does not verify filing in an external clinical record
- Practitioners review clinical documentation and remain responsible for their clinical decisions
5.4 De-identified Data for Service Improvement
Long-term analytics are intended to examine clinical narrative trends and service improvement, without model training. They require an established lawful basis and an assessment of whether a person remains reasonably identifiable in the dataset and access environment. Any future outcomes feedback or linkage needs a separate assessment; intake narratives alone do not establish diagnostic accuracy or treatment effectiveness.
The current identifier-redaction process does not prove that retained narratives are anonymous. Rare conditions, dates, relatives, locations and linkage may still identify a person. Retained information must continue to receive privacy protection unless effective de-identification is established. Gated preparation of AI-assisted redacted derivatives is implemented, but real-data processing and release remain unapproved pending explicit source permissions, provider verification and independent privacy and clinical assessment. A fixed-choice follow-up survey remains a future proposal.
6. Information Sharing and Disclosure
6.1 Healthcare Providers
Patient health information is shared with:
- The healthcare practitioner conducting the appointment
- Authorised staff at the healthcare organisation
- Other healthcare providers involved in your care (with appropriate consent or as required for treatment), including the practitioner who referred you, when the treating practitioner sends a reply letter
- Clinical systems and integration partners that the healthcare organisation chooses to connect to PreConsult
6.2 Service Providers (Sub-processors)
We use carefully selected service providers who process data on our behalf. These include:
| Service Category | Provider | Purpose | Processing Location |
|---|---|---|---|
| Cloud Infrastructure | Amazon Web Services | Hosting, database, file storage (including referral letters), receipt of forwarded emails, and content delivery | Your designated data region (see Data Residency below); currently Sydney, Australia |
| AI Language Models | Amazon Bedrock (Anthropic Claude and Amazon Nova models) | Conversational interviews, summaries, referral and email extraction, Decision Notes and letter drafting, billing code suggestions | Australian AWS regions for Australian organisations |
| AI Language Models | OpenAI | Only where an organisation's account is configured to use OpenAI models; and the chat assistant on our marketing website | USA (patients are asked for consent where patient-facing features use these models) |
| Speech-to-Text | Amazon Transcribe | Transcription of practitioner dictation (Decision Notes and Quick Add); audio is deleted once transcribed | Sydney, Australia for Australian organisations |
| SMS Delivery | Twilio | Interview invitation messages | USA (minimal data: phone number, patient first name, clinic name, and interview link) |
| Voice Processing | Twilio, with the speech recognition and voice synthesis providers configured through Twilio | Voice-based interview services (optional feature) | USA (with explicit consent) |
| Email Delivery | Mailgun or Amazon Simple Email Service (depending on configuration) | Transactional emails and notifications | USA (Mailgun) or Sydney, Australia (Amazon SES) |
| Form Protection | Google reCAPTCHA | Protecting public interview, walk-in and signup forms from automated abuse | USA |
| Website Tools | Google (Google Ads and Google Analytics), Calendly, Slack | Advertising measurement after cookie consent; demo booking when a visitor opens the booking tool; routing website chat conversations to our support team | USA (website visitor data only) |
Service-provider contracts and settings must be checked against the actual processing chain, including downstream speech services, logging, support and retention. A detailed provider list and the current verification status are available to healthcare organisations on request. Contract wording alone does not establish equivalent protection or compliance.
6.3 Legal and Regulatory Disclosure
We may disclose information when required by law, including:
- Court orders or legal process
- Regulatory investigations or audits
- Mandatory reporting obligations (e.g., notifiable diseases)
- To protect the rights, safety, or property of PreConsult, our users, or the public
7. International Data Transfers and Data Residency
7.1 Regional Data Residency
PreConsult is designed as a multi-region architecture so that your data can be stored and processed in the appropriate jurisdiction. Your healthcare organisation's data region determines where your primary data is hosted. At present the service is offered only to Australian organisations, with primary hosting in Sydney. Expansion to New Zealand and the other regions below remains planned and requires assessment before service is offered.
| Data Region | Countries Served | Primary Hosting Location | Status |
|---|---|---|---|
| Australia | Australia | Sydney, Australia | Operating |
| United States | United States, Canada | Virginia, USA | Planned |
| United Kingdom | United Kingdom | London, UK | Planned |
| European Union | Ireland, EU member states | Dublin, Ireland | Planned |
Within each region, the following data is stored locally:
- Patient health information and clinical records
- AI-powered interview transcripts
- Referral letters, forwarded emails and the details extracted from them
- Clinical summaries, Decision Notes and letters
- Audit logs and compliance records
7.2 Centralised Services
Some services are managed centrally for operational efficiency:
- User authentication: Account credentials and login sessions are managed from our primary region (Australia) but shared securely across regions via encrypted cookies
- Organisation settings: Administrative configuration is stored centrally
This centralised authentication allows practitioners to access multiple organisations across regions with a single login, while patient health data remains in the designated regional jurisdiction.
7.3 Cross-Border Processing
Some services may involve processing outside your designated data region:
- AI Language Models: Where regional AI services are not available, or where an organisation's account is configured to use US-hosted models, processing may occur in the United States with appropriate safeguards. You will be informed and asked for consent where required.
- Voice interviews: Audio processing may occur in the United States. You will be informed and asked for explicit consent before using this feature.
- SMS notifications: Delivery services may involve US-based processing. SMS messages contain minimal data: patient first name, clinic name, and interview link.
- Email delivery: Where our US-based email provider is in use, notification emails (which may include names and links) are processed in the United States.
- Form protection and website tools: Google reCAPTCHA on public forms, and the website tools listed in Section 6.2, process data in the United States.
7.4 Transfer Safeguards
For any data transfers outside your designated region, we ensure appropriate safeguards including:
- Standard Contractual Clauses (SCCs) approved by relevant authorities
- UK International Data Transfer Agreement (IDTA) for UK data
- Data Processing Agreements with all service providers
- Adequacy decisions where available (e.g., UK adequacy for EU transfers)
- Supplementary technical and organisational measures
7.5 Data Processing Agreements
Healthcare organisations using PreConsult enter into region-specific Data Processing Agreements that document our data handling obligations. Templates are available for review:
- UK Data Processing Agreement (UK GDPR with IDTA provisions)
- EU Data Processing Agreement (GDPR with Standard Contractual Clauses)
- Australia Data Processing Agreement (Australian privacy obligations)
- US Business Associate Agreement (draft for a future US offering)
To request a customised agreement, contact legal@preconsult.ai.
8. Data Security
The service uses the following access, encryption, development and incident measures. These descriptions are not an independent security certification:
8.1 Technical Safeguards
- Encryption: HTTPS for browser connections, encrypted database and object storage, and application encryption for designated sensitive fields
- Access controls: Organisation-scoped access and role permissions, with multi-factor authentication required for super administrators and clinical reviewers
- Network access: Restricted database access through configured AWS security groups
- Secure development: Automated tests, code linting and security scanning are used when preparing releases; these do not replace independent security review
8.2 Organisational Safeguards
- Operational access: Administrative functions are restricted to authorised roles
- Audit logging: Recorded security and access events support investigation; this is not a claim that every data access is logged
- Incident response: Documented breach response procedures
- Provider arrangements: Processing locations, retention, access and contractual safeguards require verification for each enabled service; no blanket provider security certification is claimed
8.3 Data Breach Response
In the event of a data breach that poses a risk to your rights and freedoms, we will:
- Assess suspected eligible Australian data breaches promptly, taking reasonable steps to complete the assessment within 30 days; notify the OAIC and affected individuals as soon as practicable once the eligible-breach threshold is met, subject to legal exceptions
- Notify affected individuals where required
- Take immediate steps to contain and remediate the breach
- Document the breach and our response
9. Data Retention
9.1 Working Copies and Collection Window
PreConsult is intended to hold a short-term working copy; the clinic is the medical-record custodian and must retain the necessary source material and approved records in its clinical system. Scheduled working copies remain available for at least seven days after the later of the appointment or interview completion, preserving any longer configured period. Without an appointment, expiry is based on the last recorded interaction, completion or update; the default is 30 days with a seven-day minimum. The interview shows its scheduled expiry.
Scheduled expiry clears the clinical working-copy sources and queues removal of original referral and paper-form attachments. Minimal operational and audit records can remain, including dates and service identifiers; these are not represented as anonymous. Manual identifier redaction is separate and may leave potentially identifiable clinical content until scheduled expiry. A preservation hold suspends scheduled expiry and discarded-record purge; an expired record cannot be restored by placing a hold.
Scheduled deletion is paused until the retention arrangement and rollout are approved. During that pause, information remains held beyond its proposed expiry window, and the interview shows that deletion is paused.
9.2 Legal Retention and Remaining Copies
Configured expiry and deletion requests do not override mandatory retention duties or legal holds. Applicable duties depend on the entity, jurisdiction and record type; PreConsult's own health-record retention status remains under legal review. An anonymous analytics dataset does not replace a required identifiable medical record. The workflow does not require a clinic filing confirmation.
Eligible working copies should be removed on the agreed schedule, subject to applicable law. Backup, object-storage and provider retention and deletion must be separately verified; expiry in the application does not prove removal of every copy. Retained clinical narratives remain protected personal information unless effective de-identification has been established, and are not used for model training.
9.3 Account Information
Practitioner and organisation account information is retained:
- While the account is active
- For a reasonable period after account closure for audit and legal purposes
- As required to comply with legal obligations
9.4 Technical Logs
Security and access logs are retained for security monitoring and incident investigation, subject to applicable law and the retention configuration for each log class. There is no verified single retention period for all technical logs.
10. Your Rights
Depending on your jurisdiction, you may have the following rights regarding your personal information:
10.1 Access and Portability
- Request a copy of the personal information we hold about you
- Receive your data in a structured, commonly used format (data portability)
10.2 Correction and Erasure
- Request correction of inaccurate or incomplete information
- Request deletion of your information (subject to legal retention requirements)
10.3 Restriction and Objection
- Request restriction of processing in certain circumstances
- Object to processing based on legitimate interests
- Withdraw consent at any time (where processing is based on consent)
10.4 Exercising Your Rights
For patients: Contact your healthcare provider about your medical record. You can also contact PreConsult about information we hold, access or correction requests, and complaints; we will coordinate with the clinic where appropriate and remain responsible for our own obligations.
For practitioners: Contact us at privacy@preconsult.ai.
We will respond to requests within the timeframes required by applicable law (generally 30 days, or 45 days for complex requests).
12. Children's Privacy
PreConsult may be used to collect health information about minors when arranged by their healthcare provider or parent/guardian. In such cases:
- Where a patient cannot give valid consent, representative authority and confidentiality must be assessed before information is collected
- The person answering must identify their relationship and authority, and the clinical record must distinguish their account from the patientโs own report
- The clinic applies the retention and confidentiality requirements relevant to the patient; any duty applying independently to PreConsult also remains applicable
12.1 Age Thresholds by Region
The minimum age for independent consent to data processing varies by jurisdiction:
| Jurisdiction | Minimum Age | Notes |
|---|---|---|
| Australia | No statutory minimum | Capacity-based assessment; no universal age of independent privacy consent |
| New Zealand | 16 years | Under Privacy Act 2020 |
| United Kingdom | 13 years | Under UK GDPR and Data Protection Act 2018 |
| Ireland / EU | 16 years (Ireland) 13-16 years (varies by EU member state) |
Ireland has set 16; other EU states may differ |
| United States | 13 years | Under COPPA; state laws may vary |
| Canada | No federal minimum | Meaningful consent required; provincial laws may apply |
Australian privacy consent depends on understanding and capacity, not a universal age threshold. Healthcare providers must assess capacity, representative authority and confidentiality before using PreConsult for a child or a person unable to consent. The interview records the respondentโs stated role and authority; it does not independently verify family relationships, court orders or capacity. Where authority or confidentiality is uncertain, the clinic resolves it before proceeding. There is no blanket adults-only restriction.
Our marketing website is not directed at children, and we do not knowingly collect information from children for marketing purposes.
13. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors.
- Minor changes: Posted on this page with an updated "Last updated" date
- Material changes: We will notify healthcare organisations and provide prominent notice on our platform
We encourage you to review this policy periodically to stay informed about how we protect your information.
14. Contact Information
Privacy Officer
Slay Pty Ltd (trading as PreConsult)
ABN 59 686 642 366
Email: privacy@preconsult.ai
Address: Melbourne, Australia
Complaints
If you believe your privacy has been breached or you are dissatisfied with how we have handled your information, you may:
- Contact us at privacy@preconsult.ai and we will investigate and respond
- Lodge a complaint with the relevant supervisory authority (see Jurisdiction-Specific Information below)
15. Jurisdiction-Specific Information
PreConsult is currently offered only to Australian organisations. Information about other jurisdictions below concerns planned expansion and remains subject to legal assessment before any service is offered there.
Our handling of Australian personal and health information must be assessed against the Privacy Act 1988 (Cth), the Australian Privacy Principles (APPs) and applicable state or territory health-information laws. This draft policy is not an independent compliance certification.
Supervisory Authority: Office of the Australian Information Commissioner (OAIC)
Website: www.oaic.gov.au
Phone: 1300 363 992
Health Records: State and territory health records legislation may also apply (e.g., Health Records Act 2001 (Vic)).
Before offering services in the UK, we must assess applicable duties under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
Supervisory Authority: Information Commissioner's Office (ICO)
Website: ico.org.uk
Phone: 0303 123 1113
International Transfer Mechanism: UK International Data Transfer Agreement (IDTA) and/or UK Addendum to EU SCCs.
See our UK GDPR Compliance Policy for detailed information.
Before offering services in the EU (including Ireland), we must assess applicable duties under the General Data Protection Regulation (GDPR).
Ireland Supervisory Authority: Data Protection Commission
Website: www.dataprotection.ie
International Transfer Mechanism: Standard Contractual Clauses (SCCs) as approved by the European Commission.
For US users, we comply with applicable federal and state privacy laws.
HIPAA: When PreConsult is used by HIPAA-covered entities, we act as a Business Associate and will enter into a Business Associate Agreement (BAA). US clinical service is not currently offered; any future offering requires assessment of HIPAA applicability, contracts and actual safeguards.
State Laws: We comply with applicable state privacy laws, including the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA) where applicable.
California Residents: You have the right to know what personal information we collect, request deletion, opt-out of sales (we do not sell personal information), and non-discrimination for exercising your rights.
For Canadian users, we comply with the Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable provincial health privacy legislation.
Supervisory Authority: Office of the Privacy Commissioner of Canada
Website: www.priv.gc.ca
Phone: 1-800-282-1376
Provincial Laws: Provincial health information legislation may also apply (e.g., PHIPA in Ontario, HIA in Alberta).
New Zealand service is not currently offered. Before offering it, we must assess applicable duties under the Privacy Act 2020 and the Health Information Privacy Code 2020.
Supervisory Authority: Office of the Privacy Commissioner
Website: www.privacy.org.nz
Phone: 0800 803 909
This Privacy Policy is governed by the laws of Victoria, Australia. By using PreConsult, you acknowledge that you have read and understood this Privacy Policy.