Privacy Policy

1. Summary

This Privacy Policy explains how ClinicalPro OSCE handles information across the website, mobile apps, support channels and related services. ClinicalPro OSCE is designed as an independent education and preparation product for AMC Part 2 candidates. It is not a patient-care system, official assessment system, clinical record system, emergency service or Australian Medical Council service.

2. Scope and product boundaries

This policy covers the website, mobile apps, accounts, practice and replay features, AI requests, analytics, leaderboard and support. Information is collected directly when you create an account, practise, submit notes or contact support; automatically through app, diagnostic and hosting systems; and from sign-in and purchase providers when those features are used. Do not submit real patient records or identifiable patient information. The service is designed for fictional educational practice, not for handling clinical records.

3. Information we may collect

Account information includes the details you provide, such as email, profile name or image, and authentication identifiers. Practice information includes station selections, activity and attempts, transcript text, Session Notes, simulated-patient responses, Session Results, replay information, ratings and feedback. Purchase information includes plan and entitlement status, store product and transaction references, and validation or renewal information. Support information includes your messages, reports and relevant account or request details. Device and operational information can include app version, platform, device or app identifiers, request IDs, event metadata, crash diagnostics and hosting logs. Some categories are collected only when you use the relevant feature.

4. Voice, speech-to-text and replay

Spoken responses are transcribed through your device's speech-recognition service. Depending on the operating system, language, device capability and settings, that service may process audio on the device or send it to its speech-service provider. ClinicalPro OSCE does not enforce on-device-only transcription. Recognised transcript text is sent to our service for AI-supported practice and saved session features. Candidate replay can use text-to-speech generated from transcript text; simulated-patient audio can be generated and stored for replay. Microphone and speech-recognition access can be revoked in device settings; this stops those spoken features but does not delete previously saved transcripts. The operating-system provider's speech privacy terms also apply.

5. AI processing

AI-supported practice sends relevant station context, conversation history, transcript text and requests to our backend and AI processing provider, Amazon Web Services through Amazon Bedrock, to generate simulated-patient replies, guidance and Session Results. Session Notes are saved for later review and are not used to generate AI examiner scoring or Session Results. Do not include patient or other unnecessary personal information in an AI request. To stop further AI processing, stop submitting requests and contact support with consent or data-deletion questions. Stopping future requests does not automatically delete earlier saved data. This policy explains processing; it does not replace a separate permission required before sharing personal data with an AI provider. AI responses can be inaccurate and are educational practice support, not medical advice or official AMC results.

6. AI training and human review

The processing described here supports requested practice features, service security and investigation of reported problems. The limited licence in the Terms does not give us a general-purpose model-training licence over your personal practice content. Authorised support or safety staff may review information relevant to a report or investigation, subject to access controls and the purposes in this policy. Any additional use of personal practice content for model training, fine-tuning or research requires a separate explanation of the data, purpose and recipient, and any consent required by law or platform rules before that use begins.

7. Content, cases and copyrighted material

Use fictional practice material and submit third-party content only if you have the rights and lawful authority to do so. Material available online is not automatically free to reuse, and AI rewriting does not remove copyright restrictions. Do not submit protected AMC cases, confidential examination material, paid course text or real patient records. Content rights, misuse and rights-holder reports are addressed in sections 13 to 17 of the Terms. If a submission contains someone else's personal information, contact support so we can assess restriction or deletion; a user's breach of these rules does not remove our privacy obligations.

8. How information is used

Information is used to create and secure accounts, authenticate users, deliver requested practice and AI features, save session history and notes, calculate progress, manage access and purchase entitlements, respond to support requests, investigate reported replies or bugs, prevent misuse and meet legal obligations. Operational event and diagnostic metadata is used to assess reliability and product performance. Private practice content is not made public merely because you submit it; leaderboard display and any sharing you choose are separate features.

9. Analytics, crash reporting and diagnostics

Clinical payload text is not used for analytics or crash custom keys. Where enabled, Firebase Analytics receives app event and identifier metadata, and Firebase Crashlytics receives crash and diagnostic metadata. These reports support reliability, safety and product performance; they are separate from storage of your practice transcripts and notes. Contact support about privacy choices and applicable access or deletion rights.

10. Payments, subscriptions and app stores

App Store and Google Play purchases are processed by the relevant store. Our subscription infrastructure, including RevenueCat, handles purchase-validation information and entitlement updates so the app can provide the correct access. Information can include an app user identifier, store product and transaction references, subscription status, renewal or expiry details, and limited support attributes needed to investigate access problems. We do not request full payment-card details for app-store purchases. Store payment records remain subject to the store's own privacy and retention rules. For cancellation, restoration and refund routes, see section 19 of the Terms.

11. Leaderboard, analytics and progress features

Leaderboard and analytics features may use practice counts, streaks, scores, Session Results, pass/fail-style practice outcomes, cohort eligibility, display names, avatars or other progress metadata. These features are intended for preparation context only and are not official AMC performance records. Users should avoid using identifying patient information or sensitive personal details in display names, profile images or public-facing fields.

12. Third-party processors and cross-border processing

Service providers handle information for the functions described in this policy. AWS supports authentication, hosting, storage, APIs, Amazon Bedrock AI processing, speech generation and operational logs. RevenueCat supports store purchase validation and subscription entitlements. Google Firebase Analytics and Crashlytics support app event reporting and crash diagnostics where enabled. Apple and Google provide distribution, sign-in and operating-system services when used. Information is stored or processed in Australia and may also be handled overseas through provider infrastructure, AI routing or support. Contact support for information about the providers and processing locations relevant to a request. Providers must handle personal information under applicable privacy requirements and the protections required for the service; using a provider does not remove our own privacy obligations.

• Amazon Bedrock data protection
• RevenueCat data processing terms
• Firebase privacy and security

13. Retention

Account and saved practice information is kept to provide your account and history until it is deleted or no longer needed for that purpose. Account deletion removes or de-identifies the profile and associated personal practice information, including session history, transcripts, notes, results and leaderboard information, subject to lawful exceptions. Limited purchase, subscription-ownership or support records may need to remain for transaction reconciliation, fraud prevention, an unresolved complaint or a legal requirement. Diagnostic and backup records follow their applicable retention and rotation schedules; they are not a reason to keep an active account indefinitely. Retained information must be limited to its identified purpose, access restricted, and deleted or de-identified when that purpose ends. Contact support for the categories, reason and expected timing relevant to your deletion request. Store and other independent provider records follow their own applicable obligations.

14. Access, correction, deletion, export and complaints

To delete an account, open Profile, then Edit profile, then Delete my account. You can also email support@amcclinicalpro.com.au about access, correction, deletion, an available export or a privacy complaint, including if you cannot sign in. We may verify identity using information proportionate to the request. We aim to respond to privacy requests and complaints within 30 days; if more time is needed, we will explain why and provide an update, subject to any shorter legal deadline. Complaints are assessed, investigated as appropriate and answered with the outcome and any available further steps. If you remain dissatisfied, you may contact the Office of the Australian Information Commissioner where it has jurisdiction, or the privacy regulator relevant to your location. Deleting an account does not cancel a store subscription. Permissions and privacy choices depend on the feature. Use device settings to manage microphone, speech-recognition and notification permissions. Contact support to ask about your personal information, object to processing or withdraw consent where processing relies on consent. We will explain any feature that cannot continue without the information necessary to provide it. Withdrawing consent applies to future processing and does not make earlier lawful processing unlawful. Account and saved-data deletion is explained in this section and section 13. Optional marketing preferences are separate from service messages.

• Privacy complaints to the OAIC

15. Security measures

ClinicalPro OSCE uses reasonable technical and organisational measures to protect information, such as HTTPS transport, cloud provider access controls, authentication, private storage where appropriate, least-privilege operational access, logging, monitoring, backup practices, security review and separation between clinical payload text and analytics/crash custom keys. No internet, cloud, mobile or AI system is risk free, and ClinicalPro OSCE cannot guarantee that unauthorised access, loss, misuse, outage or error will never occur.

16. Data breach handling

Suspected privacy or security incidents will be assessed according to applicable legal requirements. Where a notifiable or eligible data breach occurs, ClinicalPro OSCE will take reasonable steps to contain and investigate the issue, reduce harm, notify affected users or regulators where required, and improve controls where appropriate.

17. Children and adult users

ClinicalPro OSCE is intended for adults aged 18 or over preparing for professional examinations. Children must not create accounts or submit personal information; parental permission does not change this adult-use restriction. If we become aware of an ineligible account or information collected from a child, we will assess it, restrict access where appropriate and delete the associated personal information, except for limited records that must lawfully be retained.

18. Communications, cookies and website analytics

We use contact information to answer enquiries and send account, security, privacy or service notices. Promotional email requires an appropriate lawful basis and includes a way to unsubscribe; opting out of promotional messages does not stop essential account or security messages. The website is served through hosting and security infrastructure that can process request metadata such as IP address, browser details, requested pages and timestamps. Browser settings can manage cookies or local storage. App event reporting is described in section 9; it is separate from your saved practice history.

19. Regional privacy rights

Depending on location, users may have privacy rights under Australian privacy law or other regional laws, such as rights to request access, correction, deletion, portability, objection, restriction, complaint handling or regulator review. ClinicalPro OSCE will respond to valid requests as required by applicable law, while preserving mandatory records and legal defences where permitted.

20. Privacy rights and responsibilities

This policy explains how personal information is handled; it does not waive privacy rights or transfer our privacy or security obligations to users or service providers. Users should minimise personal information in practice and support submissions. Our educational-use boundaries and any lawful limits on liability are set out in the Terms. Those provisions do not exclude non-excludable privacy rights, consumer guarantees or remedies.

21. Changes to this policy

We will publish the date of changes to this policy. For a material change to how personal information is collected, used or disclosed, we will provide appropriate notice through the app, email or another reasonable channel and obtain any fresh consent required before the new processing begins. Continued use alone does not replace consent where consent is required.

22. Contact

Privacy questions, access requests, deletion requests, correction requests, complaints and support enquiries can be sent to support@amcclinicalpro.com.au. Users should not include real patient records, emergency information or unnecessary sensitive clinical information in email or contact forms.