MediCoord AI is built on real Canadian public health data — no simulated locations, no synthetic wait times. This page shows exactly what we collect, where it lives, and who can see it. For your legal rights, see our Privacy Policy.
Canadian Clinical Data Integrations & SourcesReal Regional Telemetry Sourcing
MediCoord AI relies entirely on authentic geographical and medical coordinates. All hospital locations, clinical resources, wait time estimations, and routing nodes are fetched directly from public Canadian sources, including:
- Health Ontario Directory (hospital capabilities, specialized care classifications)
- City of Toronto Open Data Portal (emergency facilities, public medical centers)
- Metropolitan Toronto Transit Telemetry (transit times, street routes, and traffic datasets)
No coordinates, patient distributions, or facility parameters are simulated; they match real-world Canadian public healthcare configurations.
Data Collection Directory
Below is the exhaustive directory of data elements processed by our application.
Email addressAccount
Purpose:Used for account creation, secure authentication, and profile identification.
Storage Target:Supabase secure cloud database.
Sharing Limit:Shared only with Supabase authentication servers.
Symptom descriptions & Triage historySensitive
Purpose:Used to run symptom analysis, map patient speech to clinical protocols, and save consultation logs.
Storage Target:Supabase secure cloud database.
Sharing Limit:Transmitted securely to the clinical AI language model provider; never used for model training.
Device coordinates & GPS positionIn-session only
Purpose:Used solely to find nearest emergency rooms and calculate live transit times.
Storage Target:Not stored. Used in-memory during active requests and discarded.
Sharing Limit:Sent to the OSRM/Geoapify routing services to calculate travel time ETAs.
Emergency contact metadataOptional
Purpose:Used only if you manually request the app to generate a shared message link for family contacts.
Storage Target:Supabase secure cloud database.
Sharing Limit:Never shared with any third party; processed only by you in your browser session.
Application diagnostic logsOperational
Purpose:Used to capture front-end rendering exceptions, software crashes, and connection failures.
Storage Target:Sentry diagnostics registry.
Sharing Limit:Shared only with Sentry monitoring servers. Content inputs are masked.
Notification device tokenOptional
Purpose:Used to route real-time travel alerts and queue updates to your device.
Storage Target:Supabase database & OneSignal registry.
Sharing Limit:Registered only with OneSignal push dispatch servers.
Medical profile (allergies, conditions, blood type)Optional / Opt-in
Purpose:Optionally provided during onboarding or in Profile. Sent to the AI triage engine only when the "Let the AI assistant use this" toggle is enabled.
Storage Target:Supabase secure cloud database.
Sharing Limit:Transmitted to the clinical AI language model only when opt-in is active. Never used for model training.
We do not sell any of the above metadata or telemetry, and we do not use it for commercial advertisement.
