1. Scope
This Privacy Notice applies to personal information DrLoop processes about authorized users of DrLoop Driver.
Depending on your role and enabled functionality, this may include information processed through:
- your Driver account;
- Trip assignments;
- Trip activity;
- Driver location;
- Vehicle information;
- communications;
- shifts or availability;
- safety and incident reporting;
- technical and security systems;
- Driver support.
Separate privacy notices apply to other DrLoop services, including:
- DrLoop Go;
- Hospital Portal;
- Provider Portal;
- drloop.ca.
2. DrLoop and Your Transportation Provider
Your DrLoop Driver account may be connected to a Transportation Provider.
DrLoop and the Transportation Provider may have different responsibilities for personal information.
For example, your Transportation Provider may independently process information relating to:
- employment or engagement;
- payroll;
- compensation;
- scheduling;
- human resources;
- training;
- credentials;
- discipline;
- workplace administration.
This Privacy Notice primarily describes personal information processed by DrLoop through DrLoop Driver and related DrLoop systems.
It does not replace a Transportation Provider's own privacy, employment or workplace policies.
3. Information We Collect
The information DrLoop processes depends on:
- your role;
- your Transportation Provider;
- enabled DrLoop features;
- your assigned Trips;
- your device permissions;
- your interactions with DrLoop Driver.
The categories below describe information that may be processed where relevant.
4. Driver Identity and Account Information
DrLoop may process information used to create, identify, authenticate or administer your Driver account.
This may include:
- name;
- email address;
- phone number;
- Driver account identifier;
- authentication information;
- account status;
- profile information;
- profile image where enabled;
- preferred language;
- security information;
- Provider association;
- assigned branch or operational unit;
- role.
5. Information From Your Transportation Provider
A Transportation Provider may provide DrLoop with information reasonably necessary to authorize or manage your use of DrLoop Driver.
This may include:
- Driver identity;
- Provider;
- branch;
- operational role;
- account authorization;
- Vehicle assignment;
- work or availability status;
- credential status where applicable;
- other information reasonably necessary for authorized platform access.
6. Credential and Qualification Information
Where credential-management functionality is enabled, DrLoop may process information relating to qualifications required for your authorized role.
This may include information about:
- Driver's licence;
- credential type;
- issuing authority;
- issue date;
- expiry date;
- status;
- Provider verification;
- other applicable qualification records.
DrLoop does not intend to collect unrelated identification or credential information merely because it is available.
7. Vehicle Information
DrLoop Driver may process information relating to the Vehicle associated with your work.
This may include:
- Vehicle identifier;
- Vehicle type;
- Provider Vehicle number;
- licence plate where applicable;
- transportation capabilities;
- equipment configuration;
- Vehicle assignment;
- operational status.
Vehicle information may become associated with you where you are assigned to operate or work in that Vehicle.
8. Trip Assignment Information
When you are assigned or authorized to participate in a Trip, DrLoop may process information such as:
- Trip identifier;
- Pickup;
- Destination;
- scheduled time;
- Rider;
- Transportation Provider;
- assigned Vehicle;
- transportation requirements;
- relevant Trip instructions;
- Trip type;
- Trip status;
- applicable operational notes.
9. Limited Rider Information
DrLoop Driver may display limited Rider or Patient information where reasonably necessary to perform an assigned Trip.
Depending on the Trip, this may include:
- Rider name;
- Pickup;
- Destination;
- relevant contact information;
- transportation requirements;
- mobility or accessibility requirements;
- relevant precautions;
- Trip instructions;
- Relevant diagnosis or condition for transportation where reasonably necessary.
Access to Rider information is tied to an authorized operational purpose.
Technical access does not authorize personal or unrelated use of Rider information.
10. Relevant Diagnosis or Condition for Transportation
For certain Trips, DrLoop Driver may display information described as:
Relevant diagnosis or condition for transportation
This means diagnosis or condition information only where it may reasonably affect:
- transportation requirements;
- assistance;
- safety;
- care requirements during transportation.
It is not intended to provide Drivers with a Rider's complete medical history.
Drivers and crew must use this information only for authorized transportation purposes.
11. Trip Activity
DrLoop may process information generated as you perform or manage assigned Trips.
This may include:
- assignment;
- acceptance or acknowledgement;
- status changes;
- departure;
- arrival;
- Pickup;
- Destination arrival;
- completion;
- waiting;
- delay;
- cancellation;
- no-show;
- timestamps;
- Trip-related operational events.
These records support transportation coordination and accountability.
12. Trip Status History
DrLoop may maintain a history of Trip status changes.
This may include statuses such as:
- On your way;
- Arrived;
- Picking up;
- Going to destination;
- Completed;
- Cancelled;
- No-show;
- Delayed.
Status records may be visible to authorized participants where relevant to the applicable Trip.
13. Precise Location Information
DrLoop Driver may process precise device or Vehicle location where necessary for enabled operational functions.
Location information may support functions such as:
- dispatch;
- Trip assignment;
- Vehicle availability;
- navigation;
- Pickup coordination;
- ETA;
- Vehicle progress;
- Trip tracking;
- Provider operations;
- applicable safety or support functions;
- investigation of significant operational issues.
Precise location is treated as sensitive information.
14. Foreground Location
DrLoop Driver may use location while the App is open and being actively used.
Examples may include:
- displaying your location on a map;
- navigation;
- identifying Vehicle position;
- supporting Trip operations;
- updating ETA.
DrLoop will request applicable device permission where required.
15. Background Location
Certain Driver functions may require location to continue while DrLoop Driver is not visible on the screen or while the device is being used for another purpose.
Where background location is enabled, it may support legitimate operational functions such as:
- active Trip tracking;
- Vehicle progress;
- ETA;
- dispatch or assignment functionality;
- Trip coordination.
Background location is not intended to authorize unlimited tracking for unrelated purposes.
16. Location While Driving
DrLoop Driver may continue processing location while you are performing an active transportation function without requiring you to manually interact with the App.
This allows location-dependent functionality to operate without requiring unsafe or unnecessary App interaction while driving.
Driver safety remains more important than manually updating the App.
17. When Location Is Collected
DrLoop seeks to limit location collection to circumstances in which location is reasonably necessary for enabled operational functions.
Depending on the implemented Driver workflow, relevant operational states may include:
- available for applicable dispatch;
- assigned to a Trip;
- On your way;
- Pickup;
- Going to destination;
- another active operational state requiring location.
The exact behaviour of location collection depends on the functionality actually enabled in DrLoop Driver and the device permission granted.
18. Off-Duty Location
DrLoop does not intend to use Driver precise location for unnecessary continuous off-duty surveillance.
Location collection should end or be appropriately limited when it is no longer reasonably necessary for an enabled operational purpose.
Turning off an operational state, ending applicable work activity, completing applicable Trips, signing out or changing device permissions may affect location processing depending on the implemented configuration.
19. Location After Trip Completion
Completion of a Trip should end location processing that is required solely for that Trip once the operational purpose has ended.
Location may continue where another legitimate and disclosed operational state independently requires it, such as another assigned Trip or enabled dispatch availability.
Location should not continue merely because a completed Trip previously required tracking.
20. Location Accuracy
Location data may not always be perfectly accurate.
Accuracy can be affected by factors such as:
- GPS availability;
- device hardware;
- network conditions;
- buildings;
- environmental conditions;
- device settings;
- operating-system behaviour.
DrLoop may use other legitimate operational information when reviewing a location-related discrepancy.
21. Location Is Not Continuous Human Surveillance
Processing location through DrLoop Driver does not necessarily mean that a person at DrLoop is continuously watching a Driver's location.
Location may be processed automatically to support operational functionality.
Access by DrLoop personnel should remain connected to legitimate authorized purposes.
22. Transportation Provider Location Visibility
Your Transportation Provider may receive location information where reasonably necessary for legitimate transportation operations.
Depending on enabled functionality, this may include:
- current Vehicle position;
- active Trip location;
- ETA;
- Trip progress;
- dispatch-related location;
- assignment information;
- relevant operational history.
Provider access should remain connected to legitimate operational purposes and applicable Provider responsibilities.
23. Rider Location Visibility
For an applicable Trip, the Rider or authorized DrLoop Go participant may receive limited information showing the progress of the assigned Vehicle.
Depending on functionality, this may include:
- Vehicle position;
- ETA;
- Driver status;
- Trip progress.
Riders should not receive unrestricted access to a Driver's unrelated historical or off-duty location through DrLoop.
24. Hospital and Facility Location Visibility
Where a Hospital or Facility is authorized to view a Trip, DrLoop may provide limited Trip-related location or ETA information reasonably necessary for coordination.
This may include:
- Vehicle progress;
- ETA;
- Trip status.
Hospital or Facility access should remain connected to the applicable authorized Trip.
DrLoop does not intend to provide Hospitals with unrestricted Driver location history unrelated to their authorized Trips.
25. Location Is Not Used for Behavioural Advertising
DrLoop does not use Driver precise location to create behavioural advertising profiles.
DrLoop also does not use precise Driver location for unrelated targeted advertising.
Location should remain connected to legitimate operational, safety, security, support or other appropriately disclosed purposes.
26. Shift and Availability Information
Where enabled, DrLoop Driver may process information relating to:
- shift status;
- availability;
- start or end of operational activity;
- Provider schedule;
- assignment readiness;
- Vehicle availability.
This information may be visible to the applicable Transportation Provider.
27. Electronic Operational Records
Using DrLoop Driver may generate electronic operational information about your activities.
Depending on functionality, this may include:
- Trip statuses;
- timestamps;
- location;
- assignments;
- availability;
- communications;
- login activity;
- Vehicle association.
These records may allow DrLoop or the Provider to understand aspects of transportation activity.
28. Transportation Provider Monitoring
A Transportation Provider may use information available through DrLoop for its own legitimate operational, supervisory or workplace purposes, subject to the Provider's own legal responsibilities and policies.
This Privacy Notice does not replace any separate electronic-monitoring or workplace notice that a Transportation Provider may be required to provide.
Questions about a Provider's independent use of Driver information should also be directed to that Provider where appropriate.
29. Communications
DrLoop may process communications connected with DrLoop Driver.
These may include:
- Trip Chat;
- Driver-to-Provider messages;
- Driver-to-Rider Trip communications where enabled;
- DrLoop support communications;
- safety reports;
- incident reports;
- email;
- SMS;
- push notifications.
Communications may be associated with the applicable Trip or account where reasonably necessary.
30. Device and Technical Information
DrLoop may process technical information needed to operate and secure DrLoop Driver.
Depending on the implementation, this may include:
- device type;
- operating system;
- App version;
- IP address;
- device or App identifiers;
- language;
- network information;
- authentication events;
- crash information;
- diagnostic information;
- security logs;
- permission status;
- technical interaction information.
31. Login and Security Information
DrLoop may maintain information relating to account access and security.
This may include:
- login events;
- failed login attempts;
- authenticated sessions;
- security events;
- device information;
- access records;
- account restriction events.
This information may be used to protect:
- Driver accounts;
- Rider information;
- Provider information;
- DrLoop systems.
32. Rider Information Access Logs
DrLoop may maintain records showing access to sensitive Rider or Trip information.
Access records may be used to:
- support security;
- investigate unauthorized access;
- investigate privacy complaints;
- detect misuse;
- protect Patients and Riders.
The existence of technical access does not create authorization to view information.
33. Safety and Incident Information
Where you report or are involved in a safety or operational incident, DrLoop may process information such as:
- affected Trip;
- date and time;
- location;
- Provider;
- Vehicle;
- Driver or crew;
- description of events;
- relevant communications;
- supporting documentation;
- relevant system records.
DrLoop seeks to limit collection to information reasonably relevant to the legitimate incident purpose.
34. Photos and Incident Documentation
Where an authorized Driver feature allows submission of incident photographs or documents, DrLoop may process the information submitted.
Do not upload unnecessary:
- Patient photographs;
- medical records;
- identification documents;
- unrelated personal information.
Documentation should be limited to what is reasonably necessary for the authorized purpose.
35. Fraud and Misuse Information
DrLoop may process information to identify, prevent or investigate suspected:
- account compromise;
- Driver impersonation;
- fraudulent Trip activity;
- false status information;
- GPS spoofing;
- unauthorized access;
- payment manipulation;
- platform abuse;
- security threats.
An automated flag does not necessarily establish that misconduct occurred.
36. How We Use Driver Information
DrLoop may use Driver personal information where reasonably necessary to:
- create and administer Driver access;
- authenticate users;
- associate Drivers with Providers;
- associate Drivers with Vehicles;
- assign or display Trips;
- support dispatch;
- coordinate transportation;
- provide navigation;
- calculate or display ETA;
- provide active Trip tracking;
- communicate Trip status;
- support Rider and Hospital visibility;
- maintain operational records;
- support Provider workflows;
- provide Driver support;
- investigate safety issues;
- detect or prevent fraud;
- protect accounts and systems;
- investigate unauthorized access;
- troubleshoot technical problems;
- improve reliability and functionality;
- enforce applicable DrLoop Terms;
- comply with applicable legal requirements.
37. We Do Not Collect Information Merely Because It Might Be Useful
Personal information should remain connected to identified legitimate purposes.
DrLoop does not intend to collect sensitive Driver information simply because the technology makes collection possible.
Collection should be reasonably proportionate to the function or purpose being provided.
38. Information Shared With Your Transportation Provider
DrLoop may provide your Transportation Provider with information reasonably necessary for Provider operations.
Depending on functionality, this may include:
- Driver identity;
- account status;
- assigned Vehicle;
- assigned Trips;
- Trip status;
- timestamps;
- operational location;
- shift or availability status;
- communications;
- relevant incident information;
- other authorized operational information.
39. Information Shared With Riders
For an assigned Trip, DrLoop may provide the Rider or authorized booking participant with limited information reasonably useful for transportation coordination.
Depending on functionality, this may include:
- Driver first name or other appropriate Driver identifier;
- Driver profile information where enabled;
- Transportation Provider;
- Vehicle information;
- ETA;
- Trip status;
- applicable Vehicle location.
DrLoop does not intend to provide Riders with unrelated Driver personal information.
40. Information Shared With Hospitals and Facilities
Where a Hospital or Facility is an authorized participant in the applicable Trip, DrLoop may share information reasonably necessary for transportation coordination.
Depending on the workflow, this may include:
- assigned Provider;
- Vehicle;
- Driver information where appropriate;
- ETA;
- Trip status;
- Vehicle progress;
- relevant coordination information.
Access should remain limited to legitimate authorized Trip purposes.
41. DrLoop Personnel
Authorized DrLoop personnel may access Driver information where reasonably necessary for their role.
Examples may include:
- support;
- operations;
- safety;
- privacy;
- security;
- fraud prevention;
- technical troubleshooting;
- legal compliance.
Access to sensitive information should be limited according to legitimate need.
42. Service Providers
DrLoop may use service providers for functions such as:
- cloud infrastructure;
- authentication;
- mapping and routing;
- communications;
- notifications;
- security;
- diagnostics;
- support.
Service providers may process Driver information where reasonably necessary to perform services for DrLoop.
DrLoop seeks to use appropriate contractual, technical and organizational protections based on the nature and sensitivity of the information.
43. Legal, Safety and Security Disclosures
DrLoop may preserve, use or disclose information where required or permitted by applicable law.
This may include circumstances involving:
- lawful legal process;
- regulators;
- court orders;
- safety incidents;
- emergencies;
- fraud;
- security incidents;
- protection of legal rights;
- protection of individuals or DrLoop systems.
Sensitive information should be limited to what is appropriate for the applicable purpose.
44. Business Transactions
If DrLoop is involved in a proposed or completed:
- merger;
- acquisition;
- financing;
- restructuring;
- sale of business or assets,
Driver personal information may be handled as permitted by applicable law and subject to appropriate safeguards.
A business transaction does not authorize unrelated use of sensitive Driver or Rider information.
45. Processing Outside Ontario or Canada
Some DrLoop service providers may process or store information outside Ontario or outside Canada.
Where information is processed in another jurisdiction, it may be subject to applicable laws of that jurisdiction.
DrLoop considers the sensitivity of information and applicable safeguards when managing service providers.
46. No Sale of Sensitive Driver Information
DrLoop does not sell Driver precise location or sensitive Trip-related information for behavioural advertising purposes.
DrLoop also does not use Rider health-related information accessed through Driver workflows for advertising to Drivers.
47. Analytics and Diagnostics
DrLoop may use limited analytics and diagnostic information to:
- maintain DrLoop Driver;
- troubleshoot;
- identify crashes;
- understand technical performance;
- improve reliability;
- understand feature operation.
Analytics should not receive sensitive Rider or precise Driver location information unless that information is genuinely necessary for an approved function and appropriately protected.
48. Third-Party SDKs
DrLoop Driver may include third-party software supporting approved functionality.
DrLoop considers the information practices of SDKs and similar components used within the App.
A third-party component should not receive unrestricted access to:
- precise Driver location;
- Rider health information;
- Trip information
merely because it is included in the App.
49. Automated Processing
DrLoop may use automated systems to support functions such as:
- ETA;
- routing;
- dispatch workflows;
- alerts;
- security detection;
- fraud detection;
- operational analysis.
An automated signal or flag may be incomplete or incorrect.
Where reasonably appropriate, relevant information may be reviewed before significant platform action is finalized.
50. Accuracy
Operational information may affect:
- Trips;
- Riders;
- Provider operations;
- safety;
- billing;
- Driver access.
Drivers and Providers should take reasonable steps to ensure information they provide is accurate and current.
You may request correction of personal information where appropriate.
An accurate historical record may remain as a historical record even where circumstances later change.
51. Retention
DrLoop retains Driver personal information only for as long as reasonably necessary for the purposes for which it was collected and applicable:
- operational;
- safety;
- security;
- fraud-prevention;
- contractual;
- legal;
- financial;
- dispute-resolution
requirements.
Different categories of information may have different retention periods.
52. Location Retention
Precise Driver location should not be retained indefinitely merely because location data can be stored.
Retention should remain connected to legitimate purposes such as:
- applicable Trip records;
- Provider operations;
- safety;
- investigation;
- disputes;
- security;
- fraud prevention;
- legal requirements.
Where identifiable precise location is no longer reasonably required, DrLoop will take appropriate steps to delete, de-identify or otherwise securely handle it.
53. Trip Record Retention
Some information associated with completed Trips may need to remain after transportation ends.
This may include information required for purposes such as:
- operational records;
- billing;
- Rider support;
- safety;
- disputes;
- fraud prevention;
- legal requirements.
Retention of a Trip does not automatically justify retaining every category of associated Driver or Rider information for the same period.
54. Safety and Incident Retention
Records connected with significant:
- collisions;
- injuries;
- safety investigations;
- privacy incidents;
- security incidents;
- harassment complaints;
- discrimination reports;
- fraud investigations;
- legal disputes
may need to be retained longer than ordinary operational information where there is a legitimate basis.
55. Credentials and Provider Records
Credential or Provider-association information may be retained for periods appropriate to:
- authorization;
- compliance;
- safety;
- Provider records;
- dispute resolution;
- applicable legal obligations.
Information no longer needed for those purposes should not be retained merely because the Driver once had platform access.
56. De-Identified and Aggregated Information
DrLoop may retain information that has been appropriately de-identified or aggregated so that it is no longer reasonably associated with an identifiable Driver.
Such information may be used for legitimate purposes such as:
- operational analysis;
- service planning;
- reliability;
- product improvement;
- aggregate reporting.
DrLoop should not intentionally re-identify properly de-identified information without an appropriate basis.
57. Security
DrLoop uses administrative, technical and organizational safeguards designed to protect personal information according to its sensitivity.
Safeguards may include measures involving:
- authentication;
- authorization;
- role-based access;
- encryption;
- logging;
- infrastructure security;
- secure development;
- security monitoring;
- incident response.
No digital system can guarantee absolute security.
58. Role-Based Access
Access to Driver and Rider information should be based on authorized roles and legitimate need.
For example:
- Drivers should receive information necessary for their authorized Trips;
- Provider users should receive information necessary for legitimate Provider operations;
- Riders should receive limited information relevant to their Trip;
- Hospitals should receive information relevant to authorized Trips;
- DrLoop personnel should access information only where their role requires it.
59. Access Logging
DrLoop may maintain access or security logs to help:
- detect unauthorized access;
- investigate misuse;
- investigate privacy incidents;
- maintain accountability;
- protect sensitive information.
Access logs themselves may contain personal information and should also be appropriately protected.
60. Lost or Compromised Devices
If a device used for DrLoop Driver is:
- lost;
- stolen;
- compromised;
- accessed by an unauthorized person,
notify the applicable Provider or DrLoop process as soon as reasonably possible.
DrLoop may take measures such as:
- ending active sessions;
- restricting account access;
- requiring reauthentication;
- investigating relevant security activity.
61. Location Permissions
You can control applicable location permissions through device settings.
Depending on the operational function, denying or disabling location may prevent or limit features such as:
- dispatch;
- navigation;
- ETA;
- active Trip tracking;
- Vehicle progress.
DrLoop should explain the purpose of relevant permissions before or when they are requested.
62. Background Location Permission
Where DrLoop Driver requires background location for an enabled core operational feature, DrLoop will provide contextual information describing:
- that location is being requested;
- that location may continue when the App is not visible;
- why background location is needed;
- how the information may be used or shared.
The operating system will also provide the applicable permission control.
See the DrLoop Driver Location & App Permissions page for additional information.
63. Notifications
DrLoop Driver may request permission to send notifications for functions such as:
- Trip assignments;
- Trip updates;
- Provider messages;
- reminders;
- safety or operational alerts.
Notification permissions can generally be managed through device settings.
Sensitive Rider information should not be unnecessarily displayed in lock-screen notifications.
64. Camera and Photos
Where an actual DrLoop Driver feature requires a camera or photo, the App may request appropriate access.
Possible legitimate purposes may include authorized:
- profile functionality;
- document submission;
- incident documentation
where enabled.
DrLoop should not request unrestricted photo access where a more limited method reasonably supports the feature.
65. Microphone and Contacts
DrLoop Driver should not request access to:
- microphone;
- personal contacts
unless an actual enabled feature reasonably requires that access.
If such functionality is introduced, appropriate disclosure and permission will be provided.
66. Provider Departure
If your relationship with a Transportation Provider ends, access to Provider-associated Driver functionality may also end.
Ending Provider authorization does not necessarily require immediate deletion of all historical information associated with your previous authorized activity.
DrLoop may retain limited information where legitimately required for:
- completed Trips;
- safety;
- security;
- disputes;
- fraud prevention;
- legal requirements.
67. Driver Account Closure and Personal Information
A Driver account may be provisioned or authorized through a Transportation Provider.
Closing, disabling or removing Driver platform access is therefore not necessarily the same as deleting every item of personal information associated with previous activity.
You may contact DrLoop regarding applicable privacy rights concerning Driver personal information.
68. Deleting the App
Removing DrLoop Driver from your device does not by itself delete:
- your Driver account;
- Provider records;
- historical Trip records;
- information legitimately retained by DrLoop.
If you have a privacy request, use the contact process described below.
69. Access to Your Personal Information
You may request access to personal information DrLoop holds about you, subject to applicable law and permitted exceptions.
DrLoop may need to verify your identity before providing sensitive information.
Depending on the request, DrLoop may provide information regarding:
- the personal information held;
- how it has been used;
- applicable disclosures.
70. Correction
You may request correction of personal information that is inaccurate or incomplete.
Where the information is an accurate historical operational record, DrLoop may preserve the original record while recording an appropriate correction, clarification or dispute where required.
71. Provider-Controlled Information
Some information about your:
- employment;
- compensation;
- payroll;
- discipline;
- scheduling;
- human resources
may be controlled independently by your Transportation Provider rather than DrLoop.
A request involving those records may need to be directed to the Provider.
DrLoop will not represent that it can alter or delete records it does not control.
72. Privacy Concerns About Location
You may contact DrLoop if you believe Driver location is being:
- collected unexpectedly;
- collected outside a disclosed operational purpose;
- retained unnecessarily;
- accessed inappropriately;
- disclosed improperly.
DrLoop may review relevant technical and operational information to investigate the concern.
73. Privacy Complaints
You may contact DrLoop with concerns about how Driver personal information is:
- collected;
- used;
- disclosed;
- accessed;
- retained;
- protected.
DrLoop may request information reasonably necessary to:
- verify your identity;
- identify the relevant account or Trip;
- investigate the concern.
74. No Retaliation for Good-Faith Privacy Concerns
DrLoop does not prohibit a Driver from raising a good-faith privacy concern, requesting access to personal information or questioning how DrLoop processes location information.
Nothing in this Privacy Notice is intended to waive legally protected privacy, employment or other rights.
75. Changes to Information Practices
If DrLoop introduces a materially different use of Driver personal information, DrLoop will assess whether additional:
- notice;
- disclosure;
- consent;
- permission
is appropriate or required before the new use begins.
A materially different use should not be hidden inside a general App update.
76. Changes to This Privacy Notice
DrLoop may update this Privacy Notice as:
- DrLoop Driver changes;
- location practices change;
- Provider workflows change;
- service providers change;
- applicable requirements change.
The current version will display its:
Effective Date
and:
Last Updated
Where a change is material, DrLoop may provide additional notice where appropriate.
77. Relationship to Other Policies
This Privacy Notice should be read together with:
- DrLoop Driver Terms of Use;
- DrLoop Driver Location & App Permissions;
- DrLoop Driver Safety & Conduct Standards;
- DrLoop Community Guidelines.
The Transportation Provider may maintain additional privacy, electronic monitoring, employment or workplace policies.
78. Contact
For questions, requests or complaints concerning Driver personal information handled by DrLoop:
DrLoop Inc.
Privacy Inquiry
info@drloop.ca
Please do not send unnecessary Rider or Patient medical information through ordinary email.
Where your request concerns a specific account, Trip or privacy event, DrLoop may request additional information through an appropriate process to verify identity and investigate the matter.
For matters involving employment, payroll, Provider scheduling or Provider-controlled personnel records, contact the applicable Transportation Provider where appropriate.
For an immediate emergency, contact the appropriate local emergency service.