Privacy Policy
Bridgie is a Collaborative Care Partner Hub and care coordination platform operated by DATAVERSED PTY LTD, ABN 20 637 174 675, ACN 637 174 675 ("we", "us" or "our"). This policy explains how we handle personal information when you visit our website, register your interest, use Bridgie, communicate with us or connect an optional integration.
Contact us about privacy at hello@bridgie.io. Please do not send medical records, passwords or payment-card details in an initial email. We can arrange an appropriate way to receive necessary information.
1. Bridgie and your care providers
Bridgie supports bookings, communications, care packages, Care Cases, clinical workflows and payments. Clinics, pharmacies and other Collaborative Care Partners remain responsible for their own services, clinical decisions, professional obligations and patient records. Their own privacy notices may also apply.
Depending on the activity, we handle information to operate our own service or on behalf of a participating organisation. Account access and patient consent controls govern what participating organisations can see. Joining Bridgie does not make all patient information available to every Partner.
2. Information we collect
The information involved depends on which features you use. It may include:
- Identity and contact information: name, email, phone number, address, account identifiers and authorised representative details.
- Organisation and staff information: business names, registration details, staff roles, provider profiles, locations and account settings.
- Care and health information: appointment details, intake forms and answers, consent records, care plans, consultation records, prescriptions, patient messages, uploaded documents and recordings or transcripts when those features are used.
- Transaction information: orders, subscriptions, invoices, payment status, refunds and payment-provider references. Payment providers handle payment credentials through their payment interfaces; do not send card details to us by email or patient message.
- Integration information: connected-account identifiers, selected calendars, permission grants and tokens needed to operate integrations you authorise.
- Technical information: IP address and connection information, browser/device information, request and security logs, session identifiers, access records and diagnostic information.
- Website enquiries: the name, work email, organisation, interest category and message you choose to provide.
We receive information directly from you, from your authorised organisation or care team, from people lawfully acting on your behalf, and from services you authorise. Sensitive information, including health information, is handled with consent where required or where otherwise permitted or required by law. If you do not provide information needed for a feature, that feature or care arrangement may not be available.
3. How we use information
- Establish accounts, authenticate users and manage organisation and staff permissions.
- Coordinate appointments, consent, care packages, Care Cases and authorised sharing between care providers.
- Deliver forms, documents, patient communications and requested notifications.
- Process and reconcile orders, payments, subscriptions, invoices, allocations and refunds.
- Operate optional services such as calendar sync and transcription when authorised.
- Provide support, maintain audit trails, investigate incidents, protect the platform and meet legal obligations.
- Respond to enquiries and provide requested launch or product updates. You can ask us to stop optional marketing communications.
We do not sell personal information. Google user data has additional use restrictions described below.
4. Sharing and service providers
We disclose information where needed for the purposes above, with appropriate authority or consent, or where the law permits or requires it. Recipients may include your authorised organisation, treating providers and care team, people you authorise, and suppliers supporting the service.
Depending on the features used, suppliers include Microsoft Azure for hosting, storage, identity, email and speech processing; configured payment providers for payment services; Mobile Message for SMS; and Google or Microsoft for calendar integrations. Their services and privacy notices apply to their own handling of information. We aim to disclose only the information necessary for the task.
Authorised personnel and professional advisers may access information when necessary to provide support, investigate security issues or meet legal obligations. Information may also need to be disclosed to regulators, courts or other authorities where legally required.
The public website loads fonts from Google Fonts, which involves a request from your browser to Google's infrastructure. You should not put patient or clinical information into the public register-interest form.
5. Google Calendar data
Connecting Google Calendar is optional and requires your authorisation through Google's consent screen. You must have authority to connect the selected calendar to the relevant Bridgie resource or organisation.
Access and purpose
calendar.readonlylets Bridgie list calendars so you can select one and read calendar events to identify busy times and avoid booking conflicts.calendar.eventslets Bridgie create, update and remove the external events linked to Bridgie appointments.- Offline access lets calendar sync run when you are not actively signed in. It does not mean unrestricted use for unrelated purposes.
What is stored and shown
We store connection and calendar identifiers, the calendar name and connected-account information available to the integration, an encrypted refresh token, sync/subscription metadata and links between Bridgie appointments and external events. The external busy-time mirror stores event identifiers and start/end times, rather than external event descriptions or attendee lists. Google API responses may contain additional event metadata that is not retained in that mirror.
External busy times are used to make availability decisions for the connected resource. Calendar management information is available to staff authorised to manage that connection. Appointment events sent to Google contain the service name, organisation name, time and a generic sync description; the integration does not add patient names or clinical notes to those events. People who can access that Google calendar may still see the service and organisation names under your Google sharing settings.
Use and sharing limits
Bridgie's use of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. We use and transfer Google user data only to provide or improve the user-facing calendar features you authorise, as permitted by that policy. We do not sell it, use it for advertising or credit decisions, or use it to train general-purpose AI or machine-learning models.
Google data is processed by the infrastructure needed to deliver those features. Human access is limited to the circumstances permitted by Google's policy, such as your affirmative permission to view specific data for support, necessary security investigations or compliance with applicable law. Google Calendar data is not sent to Bridgie's transcription service.
Disconnecting, revocation and deletion requests
You can disconnect a calendar using Bridgie's integration controls. This disables the active connection for further sync; it does not itself revoke Google's permission grant, erase all stored connection history or remove events already created in Google.
You can separately revoke Bridgie's access through your Google Account connections settings. To request deletion of stored Google connection or calendar data, email hello@bridgie.io and identify the relevant organisation and connection. We verify authority, explain any retention requirements and handle the request as described in sections 7 and 8. Disconnecting does not delete the underlying Bridgie appointment or clinical record.
6. Storage, security and overseas processing
Bridgie's core application infrastructure is hosted in Australia. We use controls including encrypted connections, role-based account access, database access controls, protected document storage and audit records. Calendar refresh tokens are encrypted before storage. No online service can guarantee absolute security.
Australian hosting does not mean every supplier processes all information exclusively in Australia. Calendar, identity, payment, messaging, support and other suppliers may operate infrastructure or personnel overseas. The locations involved depend on the supplier, account and service configuration. Contact us for information about the arrangements relevant to your use; applicable cross-border privacy obligations must be considered before sensitive information is shared.
We use browser storage and session technologies for authentication, security and preferences. Your identity provider and integration providers may use their own cookies. Clearing Bridgie browser data does not necessarily sign you out of those separate services. We assess suspected data incidents and make notifications where required by applicable law.
7. Retention and deletion
We retain information for as long as reasonably necessary for its purpose and applicable clinical-record, accounting, dispute, security and legal requirements. The relevant period depends on the record and the organisation responsible for it; this policy does not promise a single deletion deadline for all information.
Some clinical, transaction and audit records use soft deletion, historical versions or tamper-evident records. Closing an account or disconnecting an integration does not automatically erase those records. Backups and legally required records may also be retained. Where destruction is not available or lawful, we explain the position and consider available restrictions, correction or de-identification.
A care provider may independently need to retain its clinical records even if you stop using Bridgie. We do not delete records from Google, Microsoft or another provider's systems merely because you close a Bridgie account.
8. Access, correction and choices
You can ask for access to, or correction of, personal information we hold about you, and ask about deletion, restrictions or withdrawing consent where applicable. Email hello@bridgie.io. We may need to verify your identity or authority and work with the organisation responsible for a clinical record.
Rights are subject to applicable law, other people's privacy and record-retention obligations. If we cannot carry out a request, we explain why and any available review or complaint process. A correction may be recorded as an amendment rather than erasing a clinical or audit history. Withdrawing consent can affect future services but does not automatically undo earlier lawful processing or required records.
You may unsubscribe from optional marketing or ask us to stop those updates. Necessary account, transaction, security or care-related messages may still be sent where appropriate.
9. Questions and complaints
Contact DATAVERSED PTY LTD at hello@bridgie.io with a description of your concern and how we can respond. We will assess it and respond within a reasonable period, taking account of any legal time limits.
If you are dissatisfied, you may contact the Office of the Australian Information Commissioner or another relevant regulator. Complaints about a provider's own care or records may also need to be directed to that provider.
10. Changes to this policy
The current policy and its effective date are available on this page. We will explain material changes and seek fresh consent where required, including before using Google data for a new purpose requiring consent.