Privacy policy.
How we collect, use, and protect personal information across the OriComply platform.
Last updated 13 November 2026
- 01 /
About this policy
OriComply is operated by Matthew25 AI (ABN 19 692 319 476). We are committed to protecting the privacy of personal information, including health information, in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).
This policy applies to all personal information collected through our platform, including the Comply, Food Safety, and Learning modules.
- 02 /
Information we collect
We collect the following categories of personal information:
- Identity information: Name, email address, role, job title
- Account information: Login credentials (passwords are hashed, never stored in plain text)
- Usage information: Training completion records, policy acknowledgments, compliance activity logs
- Health-related information: Where applicable, health information that appears within care-related and compliance documentation (for example, care notes, incident records and policy documents)
- Uploaded content: Profile photos, certificates, training documents, policy documents
- Staff kiosk questions: Where your organisation enables the passcode-protected staff policy kiosk, the questions staff type into it, used to generate answers from your facility's policies. Staff are asked not to enter residents' names or other personal details.
- Technical information: A one-way hashed version of each kiosk visitor's IP address, used only to rate-limit the kiosk and prevent abuse. Raw IP addresses are never stored.
- Staff mobile numbers (app login): For staff using the OriComply mobile app, we collect the mobile phone number, which serves as the login credential. Face ID / fingerprint unlock happens entirely on the staff member's own device — that biometric data is never transmitted to or stored by OriComply.
We collect personal information directly from you or your organisation's administrator when they invite you to the platform. We do not collect information from third parties without your knowledge.
Public-website analytics. Our public pages (the home page and the security, terms, privacy and contact pages) use Vercel Web Analytics to count visits, see which pages are read, and count clicks on our “Book a demo” and email links. It is cookieless, sets nothing on your device, and does not build a profile of you or follow you across other websites. It records the page visited, the referring site, and coarse device and country information — never your IP address and never a persistent identifier. It does not run on any signed-in page, so no resident, client or staff record is ever seen by it.
We use Microsoft Clarity to see how visitors use our public website pages. It records clicks, scrolling and page views, with text masked, and is not used on the signed-in app. These are session recordings that we can replay.
Except as set out under Advertising and Demo bookings below, our public pages embed no third-party content, advertising or tracking; links to LinkedIn contact LinkedIn only when you click them; the booking script is described under “Demo bookings” below. The pages do load two services listed under “Data sharing & disclosure” below: Clerk, our sign-in provider, and Sentry, which receives error reports and a sample of page-load timings so we can fix problems. A few small items are stored on your device: Clerk's sign-in cookies, your language preference, an error-monitoring session marker, and an offline cache so the app loads quickly. Except as set out under Advertising below, none is used for advertising or to follow you across other websites. Microsoft Clarity, described above, is a further exception to the statements above: it is third-party tracking on public pages only. It sets the cookies _clck and _clsk on our site, and Microsoft sets its own cookies on clarity.ms, including CLID and MUID, which Microsoft also uses for advertising. See the Microsoft privacy statement.
Advertising and conversion tracking. Our home page, articles and contact page also use the Google Ads conversion tag. Google uses the tag to tell us whether a visit that began with one of our Google ads ended in a click on “Book a demo” or a contact form message. It sets cookies on your device and sends Google the page you visited, the code Google added to the link when you clicked our ad, what you did on the page, and technical details such as your IP address and browser. We do not send Google anything you type into the contact form. The tag is not loaded on any signed-in app page, so nothing there is shared with Google.
We also keep that code, and any campaign details in the link, in your browser until you close the tab. If you send the contact form, we add them to the message we receive so we can see which ad it came from.
To opt out, turn off ad personalisation in Google Ads Settings, or block or clear cookies in your browser settings. The site works the same either way.
Demo bookings. Pages with a “Book a demo” button load a script from Cal.com, a booking service based in the United States, which receives your IP address and browser details when the page loads. If you book, Cal.com stores what you enter in the form and which of our buttons you used, on our behalf, in the United States.
- 03 /
How we use your information
We use personal information for the following purposes:
- Providing and operating the OriComply platform and its modules
- Authenticating your identity and managing your account
- Tracking training completion and compliance status for your organisation
- Generating AI-assisted summaries and search results from your organisation's policy documents
- Answering staff questions at the policy kiosk by generating AI-assisted responses from your organisation's own policy documents (processed by AWS Bedrock in Australia; never used to train any model)
- Authenticating staff in the OriComply mobile app — sending a one-time SMS verification code at enrolment, and using the mobile number as the sign-in identifier thereafter
- Reading residents' progress notes, imported from your organisation's care system, to flag residents who may need clinical attention (the Morning Brief), on your organisation's instructions
- Sending service notifications (training reminders, system updates)
- Improving the platform based on aggregated, de-identified usage patterns
We will not use your personal information for purposes other than those described above without your consent, except where required or authorised by law.
- 04 /
Health information
Where our platform processes health information (as defined under the Privacy Act), we apply additional protections in accordance with APP 3 (collection of sensitive information). For resident and care-related health information, the provider organisation is the data controller and is responsible for obtaining any consent required to collect it; OriComply acts as the data processor and handles that information solely on the organisation's instruction, for the purpose for which the organisation provided it — typically clinical documentation, care planning, or regulatory compliance. Where you provide health information about yourself directly to us, we collect it only with your consent and use it solely for that purpose.
- 05 /
Data storage & security
Your data is protected by the following measures:
- Data residency: Resident and operational data is stored in Australia (AWS ap-southeast-2) via our database provider Supabase. Some account and service data is handled by overseas sub-processors — see “Data sharing & disclosure” below
- Encryption at rest: AES-256 encryption for all stored data
- Encryption in transit: TLS encryption for all data transmission
- Access control: Row-Level Security (RLS) ensures users can only access data belonging to their organisation
- Authentication: Multi-factor authentication (MFA) available for all accounts
- Infrastructure certification: Our infrastructure provider (Supabase) maintains SOC 2 Type II certification
- Backups: Daily automated backups with point-in-time recovery capability
- 06 /
Data sharing & disclosure
We do not sell, rent, or trade personal information. We may share information with:
- Your organisation's administrators: Who have access to manage users, view compliance reports, and configure the platform for their organisation
- Sub-processors in Australia: Supabase and Amazon Web Services (database hosting and file storage), Vercel (application hosting, and anonymous visitor analytics on our public pages only), and AWS Bedrock and Amazon Transcribe (the AI used for the policy agent, regulatory-standards search, summarisation and voice transcription, and the Morning Brief — all in Australia)
- Sub-processors overseas (United States): Clerk (authentication and identity), Twilio (SMS verification codes for staff mobile-app sign-in), Resend (email delivery), Microsoft (Clarity, visitor recordings on our public pages only), Sentry (error monitoring), and Cal.com (demo bookings on our public website)
- Law enforcement or regulators: Where required by Australian law or court order
All sub-processors are bound by data processing agreements. In accordance with APP 8, where personal information is handled by the overseas sub-processors listed above, we take reasonable steps to ensure they protect it consistently with the Australian Privacy Principles. Resident and operational data — including health information — remains stored exclusively in Australia.
- 07 /
Data retention & deletion
For resident, care and operational data entered into OriComply (“Customer Data”), the provider organisation is the data controller and ori is the data processor. Provider organisations carry record-keeping obligations under the Aged Care Act 1997 (Cth), the Records Principles 2014 and related health-records legislation — commonly seven years or longer. We will not unilaterally destroy a provider organisation's Customer Data on a subscription lapse or any other event short of a written deletion instruction.
While your subscription is active:
- Customer Data is retained continuously so the service can be used normally
- Data is encrypted in transit and at rest; tenant isolation is enforced at the database level
If your subscription lapses or is cancelled:
- You have a 30-day export window during which authorised users can sign in to download Customer Data in a structured, machine-readable format. Contact privacy@oricomply.ai if you need help with export
- After the 30-day window, platform access is revoked, but Customer Data is preserved on our systems — we do not run any automatic deletion triggered by subscription status. This is deliberate so that a commercial event does not destroy records you may be legally required to retain
- You can resume normal access at any time by reactivating the subscription
If you instruct us in writing to delete Customer Data (offboarding):
- We make Customer Data available for export for 30 days from the date of the deletion instruction
- At the end of that window, we delete Customer Data from the live platform within 30 further days
- Deleted records cycle out of routine backups within the backup retention window (currently 7–28 days, depending on plan)
- Sub-processors are instructed to delete associated personal information per their data processing agreements; some retain limited records to meet their own financial or legal obligations
- The deletion event is recorded in an internal deletion log and we confirm completion to you on request
If you delete your own account (staff app):
- In the OriComply staff app, go to Settings, then Account, then Delete my account. You can cancel the request at any time before it is carried out
- Your employer’s head office is told. They can approve it straight away. If nobody acts, your account is deleted automatically 30 days after you ask
- When it is deleted, you can no longer sign in, and we remove your email address, phone numbers, home address, date of birth and emergency contact details from your profile
- Your name stays on records your employer must keep, such as training completions, policy sign-offs and audit history. We keep these so your employer can show who was trained and who signed what; they hold no contact details
Audit logs of AI model invocations are retained for seven years to support clinical-records traceability. Billing records held by our payment processor are retained for the period required by Australian financial record-keeping obligations (commonly seven years). Application and error logs are retained for shorter periods (90 days for system logs, 12 months for access logs).
- 08 /
Your rights
Under the Australian Privacy Principles, you have the right to:
- Access the personal information we hold about you (APP 12)
- Correct inaccurate or out-of-date information (APP 13)
- Request deletion of your personal information, including by deleting your own account in the staff app
- Withdraw consent for processing where consent was the basis for collection
- Export your data in a machine-readable format
To exercise any of these rights, contact us at privacy@oricomply.ai.
- 09 /
Data breach notification
In accordance with the Notifiable Data Breaches (NDB) scheme under the Privacy Act, if we suspect an eligible data breach (one likely to result in serious harm), we will assess it within 30 days. If we decide it is an eligible data breach, we will:
- Notify the Office of the Australian Information Commissioner (OAIC) as soon as practicable after deciding it is an eligible data breach, as required by the NDB scheme
- Notify affected individuals as soon as practicable after deciding it is an eligible data breach
- Provide recommendations for steps individuals can take to protect themselves
- 10 /
AI & automated processing
Our platform uses AI to provide features such as policy search, document summarisation, regulatory-standards analysis, and assistance with care-related documentation. When using AI features:
- AI processes only your organisation's data — never data from other organisations
- AI-generated outputs are clearly labelled and should be reviewed by qualified staff before clinical or regulatory use
- Morning Brief: our AI reads the progress notes your organisation imports from its care system and flags residents who may need clinical attention. It is used only to help your staff decide who to check first; it does not make care decisions, and its flags should be reviewed by qualified staff. We run it on your organisation's instructions, as its service provider, and the notes are processed only in Australia
- Your data is not used to train AI models
- All AI processing — including chat, summarisation, transcription, and embeddings — runs on AWS Bedrock and Amazon Transcribe in Australia. Data is transmitted securely and is not retained by the provider beyond the request lifecycle
- 11 /
Changes to this policy
We may update this privacy policy from time to time. We will notify you of material changes via email or an in-app notification. The “last updated” date at the top of this page indicates when the policy was last revised.
- 12 /
Contact
For privacy inquiries, data access requests, or complaints:
- Email: privacy@oricomply.ai
- Privacy Officer: Jordy Fung
If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC).