Does MediCoord AI store my GPS location?

No. Your device location is used in-memory during an active request to calculate travel times and is discarded immediately after. It is never stored in our database.

Can MediCoord AI see my symptom descriptions?

Your symptom descriptions are transmitted securely to an AI language model to generate the triage assessment. They are stored in your conversation history in our database but are never used to train any AI model.

Who can see my MediCoord AI data?

Only you and our service backend can access your records. Data is shared only with the service providers that make the app work: Supabase for storage, Sentry for error tracking, OneSignal for push notifications, and the AI provider for symptom triage.

Is my emergency contact shared with anyone?

No. Emergency contact metadata is never shared with any third party. It is processed only by you in your browser session when you choose to generate a message link.

Does MediCoord AI sell my data?

No. MediCoord AI does not sell any data and does not use it for commercial advertisement.

← Back to home

Data Disclosure

Last updated: October 7, 2026

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 & Sources

Real 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.

Guest demo: random browser IDNo account

Purpose:The public demo needs no sign-in. A random ID created in your browser keeps your conversations together and counts messages for the usage limit.

Storage Target:In your browser (local storage) and in our demo database. It is not linked to your name, email or IP address. Clearing your browser data starts a new, empty guest.

Sharing Limit:Never shared.

Guest demo: chat textDeleted after 30 days

Purpose:Shown back to you when you return in the same browser, and reviewed by the team to improve recommendations.

Storage Target:Demo database (Railway, PostgreSQL). Each conversation and its messages are deleted 30 days after the conversation started.

Sharing Limit:Sent to the language-model provider (Groq) to generate replies. Not sold or shared otherwise.

Guest demo: feedback and usage eventsKept

Purpose:Your thumbs up/down and optional comment, and three counters (conversation started, recommendation shown, route drawn), tell us whether the demo works.

Storage Target:Demo database, linked only to the random browser ID. No IP address is stored; it is used for ten minutes, in hashed form, to limit abuse.

Sharing Limit:Never shared.

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 by our server to the Geoapify routing service to calculate travel times and routes.

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.