Location & App Permissions

1. Permission Principle

DrLoop's approach to device permissions is:

Ask only when needed.

A device capability should not be requested merely because the operating system makes it available.

The permission requested should be reasonably connected to an actual DrLoop Driver feature.

Where a less intrusive permission can reasonably support the feature, DrLoop seeks to use the less intrusive option.

2. Your Device Controls Permissions

Your device operating system controls whether DrLoop Driver receives access to permissions such as:

• location;
• notifications;
• camera;
• photos;
• other device capabilities.

You may be able to:

• allow;
• deny;
• limit;
• later change

a permission through your device settings.

Some DrLoop Driver functionality may not operate properly if a permission required for that functionality is disabled.

3. Permission Requests Are Separate From These Terms

Reading or accepting this page does not itself grant DrLoop access to your device.

Where an operating-system permission is required, your device will provide the applicable permission control.

Where additional notice is appropriate, DrLoop may first provide an in-app explanation before the operating-system request appears.

4. Location

Location is an important operational capability in DrLoop Driver.

Depending on the functionality enabled for your Transportation Provider and role, DrLoop Driver may use location to support:

• dispatch;
• Trip assignment;
• Vehicle availability;
• navigation;
• Pickup coordination;
• estimated arrival times;
• Vehicle progress;
• active Trip tracking;
• Provider operational visibility;
• Rider Trip visibility;
• Hospital or Facility Trip visibility;
• safety or operational support;
• investigation of significant Trip discrepancies.

Location is treated as sensitive information.

5. Precise Location

Certain Driver functions may require precise location rather than an approximate location.

For example, accurate location may be reasonably necessary to support:

• navigation;
• Vehicle progress;
• Pickup arrival;
• active Trip tracking;
• ETA;
• operational dispatch.

DrLoop seeks to use precise location only where the level of accuracy is reasonably necessary for the applicable feature.

6. Approximate Location

Where approximate location is sufficient for an enabled feature, DrLoop may use or accept a less precise location.

Not every feature requires the same level of location accuracy.

Certain operational Driver functions may not work properly with approximate location alone.

7. Foreground Location

Foreground location generally means location accessed while DrLoop Driver is open and actively being used.

Foreground location may support functions such as:

• showing your Vehicle on a map;
• navigation;
• locating a Pickup;
• updating operational position;
• calculating an ETA.

DrLoop may request foreground location before a feature that reasonably requires it is used.

8. Background Location

Certain DrLoop Driver functions may require location to continue while:

• DrLoop Driver is minimized;
• another application is visible;
• the phone screen is locked;
• DrLoop Driver is otherwise not visible on screen.

This is referred to in this page as background location.

Where enabled and necessary, background location may support functions such as:

• active Trip tracking;
• Vehicle progress;
• ETA;
• applicable dispatch functionality;
• Trip coordination.

9. Why Background Location May Be Needed

A Driver should not need to keep DrLoop Driver continuously open on screen merely so an active Trip can remain visible to authorized participants.

Where properly enabled, background location may allow applicable Trip functionality to continue while the Driver:

• uses navigation;
• locks the device;
• uses another permitted device function;
• keeps the phone safely mounted or stored.

This can reduce unnecessary manual interaction with the App while driving.

10. Background Location Is Not Unlimited Tracking

Permission to process location in the background does not mean DrLoop has unlimited permission to track a Driver for unrelated purposes.

Background location should remain connected to legitimate and disclosed DrLoop Driver functionality.

DrLoop does not intend background location permission to authorize continuous unrelated personal surveillance.

11. Operational States

Location processing may depend on the Driver's operational state and the functionality enabled for the Transportation Provider.

Depending on the implemented workflow, location-dependent states may include:

• available for applicable dispatch;
• assigned to a Trip;
• On your way;
• Arrived;
• Picking up;
• Going to destination;
• another active Trip state.

DrLoop should not continue collecting precise location solely because a previous Trip once required it.

12. Active Trip Tracking

During an active Trip, location may be used to support:

• Vehicle progress;
• ETA;
• Pickup coordination;
• Destination progress;
• authorized Trip visibility;
• Provider operations.

Location-dependent tracking should end when the purpose for that tracking ends, unless another legitimate and disclosed operational state requires location.

13. Before Pickup

Where applicable, location may be used after a Driver is assigned or begins travelling to a Pickup.

This may help:

• the Provider understand Vehicle progress;
• the Rider see applicable Vehicle progress;
• an authorized Hospital user understand ETA;
• DrLoop calculate or update arrival information.

14. During Transportation

During transportation, location may support:

• route progress;
• ETA;
• Provider visibility;
• Trip coordination;
• authorized Rider visibility;
• authorized Hospital or Facility visibility.

Location information does not replace safe Driver judgment or actual transportation procedures.

15. After Trip Completion

Location collection required solely for a particular Trip should end after the applicable Trip-related purpose has ended.

If another legitimate operational function remains active, such as another assigned Trip or properly enabled dispatch availability, location may continue for that separate purpose.

A completed Trip does not by itself justify unnecessary ongoing tracking.

16. Off-Duty Location

DrLoop does not intend to use precise Driver location for unnecessary continuous off-duty surveillance.

Where there is no legitimate operational reason requiring location, location processing should be stopped or appropriately limited.

The actual behaviour may depend on:

• operational state;
• Provider configuration;
• device permissions;
• App configuration;
• enabled Driver functionality.

17. Shift End and Sign Out

Where supported by the applicable workflow, ending a Driver's operational activity or signing out may affect ongoing location collection.

Location that is no longer needed for an active or legitimate operational function should not continue merely because DrLoop Driver remains installed on the device.

18. Transportation Provider Visibility

The applicable Transportation Provider may receive Driver or Vehicle location where reasonably necessary for legitimate transportation operations.

This may include:

• Vehicle position;
• active Trip location;
• Trip progress;
• ETA;
• dispatch-related position;
• applicable operational history.

Provider access should remain connected to legitimate operational or workplace purposes and the Provider's own legal responsibilities.

19. Rider Visibility

During an applicable Trip, the Rider or authorized person using DrLoop Go may receive limited location-related information about the assigned Vehicle.

This may include:

• Vehicle position;
• ETA;
• Driver status;
• progress toward Pickup;
• Trip progress.

A Rider should not receive unrestricted access to a Driver's:

• off-duty location;
• unrelated location history;
• unrelated Trips.

20. Hospital and Facility Visibility

An authorized Hospital or Facility participant may receive limited Trip-related information where necessary for transportation coordination.

Depending on the enabled workflow, this may include:

• Vehicle progress;
• ETA;
• Trip status.

A Hospital or Facility should not receive unrestricted access to a Driver's location outside the applicable authorized Trip.

21. DrLoop Access to Location

Authorized DrLoop personnel may access location information where reasonably necessary for legitimate functions such as:

• support;
• operations;
• safety;
• privacy investigations;
• fraud prevention;
• security;
• technical troubleshooting;
• dispute review;
• legal compliance.

Access should be limited according to role and legitimate need.

22. No Location-Based Advertising

DrLoop does not use precise Driver location to create behavioural advertising profiles.

DrLoop does not use Driver precise location for unrelated targeted advertising.

DrLoop Driver background location should not be requested solely for:

• advertising;
• unrelated marketing;
• general analytics.

23. Location and Analytics

Location information should not be provided to analytics tools merely because those tools are integrated into DrLoop Driver.

Where location is genuinely required by an approved operational feature, access should remain limited to what is reasonably necessary for that feature.

Third-party software does not receive unrestricted access to Driver location merely by being included in the App.

24. Location Disclosure

Before requesting sensitive location access where an additional explanation is appropriate, DrLoop may display an in-app disclosure describing:

• what location is being requested;
• whether location may continue in the background;
• why the information is needed;
• which relevant features use it;
• how it may be shared.

This disclosure is separate from the operating-system permission prompt.

25. Background Location Disclosure

Where DrLoop Driver requests background location, the disclosure should clearly explain that location may continue to be collected when DrLoop Driver is not visible or is not actively being used on screen.

The exact wording presented in the App should reflect the actual functionality implemented at that time.

26. Android Location Permissions

On Android devices, the specific permission options available may depend on:

• Android version;
• device;
• DrLoop Driver version;
• enabled functionality.

DrLoop seeks to request the minimum location access reasonably necessary for the applicable feature.

Where foreground location can reasonably provide the required functionality, DrLoop should not request background location merely for convenience.

27. Android Background Location

Where an enabled core DrLoop Driver function genuinely requires background location, DrLoop may request the applicable Android permission.

Before requesting that permission, DrLoop may provide a prominent in-app explanation of the background location functionality.

Background location should remain connected to functionality actually used and disclosed in DrLoop Driver.

28. Android Foreground Services

DrLoop Driver may use operating-system mechanisms that allow certain active operational functions to continue when the App is minimized.

Where applicable, the device may display an ongoing system notification or other indicator while the functionality is active.

The implementation may vary by Android version and enabled functionality.

29. iPhone Location Permissions

On iPhone, available location choices may include different levels of authorization depending on:

• iOS version;
• enabled DrLoop Driver functionality;
• when location is required.

DrLoop seeks to request the least extensive authorization reasonably capable of supporting the enabled feature.

30. "While Using" Location

Where location is only required while DrLoop Driver is actively being used, DrLoop may request the applicable permission allowing location while using the App.

This level of authorization may not be sufficient for every active Trip workflow where location legitimately needs to continue while DrLoop Driver is no longer visible.

31. Extended iOS Location Access

DrLoop should not request broader or continuing iOS location authorization unless enabled Driver functionality reasonably requires it.

Where broader location access is necessary, the App should explain the relevant purpose in context.

The operating system retains control over the permission ultimately granted.

32. Changing Location Permission

You can generally review or change DrLoop Driver location permissions through your device settings.

Depending on your device, you may be able to:

• disable location;
• allow location while using the App;
• change precise-location settings;
• change background-location authorization.

The exact options vary by platform and operating-system version.

33. What Happens if Location Is Denied

You may decline a location permission.

However, Driver functionality that reasonably depends on location may become unavailable or limited.

Depending on the enabled workflow, this may affect:

• navigation;
• Trip assignment;
• dispatch;
• ETA;
• active Trip tracking;
• Vehicle progress;
• Provider visibility.

DrLoop should explain the relevant consequence rather than repeatedly pressuring a Driver to grant an unrelated permission.

34. Open Settings

If a required permission was previously denied, DrLoop Driver may explain why the permission is needed and provide an option to open the applicable device settings.

DrLoop should not attempt to bypass an operating-system permission decision.

35. Location Accuracy

GPS and other location technologies are not perfectly accurate.

Location may be affected by:

• buildings;
• tunnels;
• weather;
• GPS availability;
• device hardware;
• network connectivity;
• operating-system limitations;
• device settings.

A temporary location error does not automatically establish misconduct by a Driver.

36. GPS Spoofing and Manipulation

Drivers must not intentionally falsify location used for DrLoop operations.

Prohibited conduct includes:

• GPS spoofing;
• manipulating device location to create a false Trip record;
• making a Vehicle appear to have arrived when it has not;
• deliberately falsifying Trip progress.

Technical location errors that occur without intentional manipulation are different from deliberate spoofing.

37. Safety

Location is an operational tool.

It is not a substitute for:

• emergency services;
• Driver judgment;
• safe driving;
• Provider procedures;
• emergency response.

DrLoop does not guarantee that location will always be:

• available;
• accurate;
• uninterrupted;
• monitored in real time.

38. Location Is Not Automatic Emergency Detection

Unless DrLoop expressly introduces and describes a specific feature, location access does not mean DrLoop automatically detects:

• collisions;
• medical emergencies;
• Driver distress;
• unsafe driving;
• Vehicle breakdowns.

In an emergency, use the appropriate emergency procedures directly.

39. Notifications

DrLoop Driver may request permission to send notifications.

Notifications may be used for operational purposes such as:

• Trip assignments;
• Trip updates;
• Provider messages;
• shift or availability information;
• reminders;
• operational alerts;
• safety-related information;
• security information.

40. Notification Privacy

Notifications may appear on a lock screen depending on device settings.

DrLoop seeks to avoid displaying unnecessary sensitive Patient or health-related information in notifications.

Users can generally manage notification visibility through their device settings.

41. Camera Permission

DrLoop Driver may request camera access only where an enabled feature reasonably requires it.

Possible legitimate features may include:

• authorized Driver profile functionality;
• credential submission;
• Vehicle documentation;
• authorized incident documentation;
• another approved feature.

DrLoop should not activate or access the camera for unrelated continuous monitoring.

42. Photos and Media

Where a feature allows submission of an existing image or document, DrLoop should seek to use a limited file or photo selection mechanism where reasonably available rather than requesting unrestricted access to an entire personal photo library.

Only files intentionally selected for the legitimate feature should be processed where technically appropriate.

43. Incident Photos

Where DrLoop Driver allows incident documentation, collect only information reasonably necessary for the legitimate incident purpose.

Avoid unnecessary photographs of:

• Patients;
• medical records;
• identification documents;
• unrelated people;
• unrelated private information.

Do not use incident photography for personal purposes or social media.

44. Microphone

DrLoop Driver should not request microphone access unless an actual enabled feature reasonably requires it.

If microphone functionality is introduced, DrLoop should explain the feature and request appropriate device permission.

DrLoop Driver should not secretly activate a device microphone for unrelated monitoring.

45. Contacts

DrLoop Driver should not request broad access to a Driver's personal contact list merely to operate ordinary Trip functionality.

Where a future feature genuinely requires contact-related functionality, DrLoop should seek the least intrusive mechanism reasonably available and provide appropriate disclosure.

46. Bluetooth and Nearby Devices

DrLoop Driver should request Bluetooth or nearby-device permissions only if an actual enabled function reasonably requires them.

Possible future legitimate functionality may include connection with authorized:

• Vehicle hardware;
• operational accessories;
• approved devices.

A permission should not be requested before an actual feature requires it.

47. Motion, Activity and Sensors

DrLoop Driver should not request access to motion, activity or other device-sensor information unless an enabled feature has a legitimate need for it.

If such functionality is introduced, DrLoop should provide appropriate disclosure before collecting information that may not reasonably be expected.

48. Files and Storage

DrLoop Driver should use device storage access only where reasonably necessary for an actual function.

Examples may include authorized:

• document upload;
• credential submission;
• incident attachment.

Where a limited file-picker mechanism is available, DrLoop should prefer that approach over unnecessary broad access.

49. Biometrics

Where DrLoop Driver supports biometric authentication, authentication may be handled through device or operating-system security features such as fingerprint or facial authentication.

DrLoop does not need to receive a copy of the underlying biometric template merely because the device uses biometrics to authorize access.

The exact process depends on the authentication feature implemented.

50. Advertising Tracking Permissions

DrLoop Driver is an operational application.

DrLoop does not intend to request advertising-tracking permission merely to support core:

• dispatch;
• Trip;
• navigation;
• location;
• Provider

functionality.

Sensitive Driver or Rider information should not be used for behavioural advertising.

51. Device Information Without Special Permission

Some technical information may be processed by the App without appearing as a separate operating-system permission.

Depending on implementation, this may include:

• App version;
• operating system;
• device type;
• crash information;
• security information;
• network information.

These practices are further described in the DrLoop Driver Privacy Notice.

52. Permission Status Information

DrLoop Driver may determine whether a required permission is:

• granted;
• denied;
• restricted;
• unavailable.

This can allow the App to explain why an operational feature is not working.

Permission status should not be used to circumvent the choice made through the operating system.

53. Permission Changes

You may change permissions after originally granting them.

If you disable a permission needed for an active function, DrLoop Driver may:

• explain which feature is affected;
• pause or limit that function;
• ask you to restore access where operationally necessary.

The App should not represent an optional permission as mandatory where it is not actually required.

54. Permissions and Provider Requirements

A Transportation Provider may require certain DrLoop Driver functionality to perform assigned transportation.

Where that functionality legitimately requires a device permission, denying the permission may affect your ability to use the corresponding DrLoop feature.

Employment or Provider consequences arising from a Provider requirement are separate from DrLoop's operating-system permission request and remain subject to applicable Provider responsibilities and law.

55. Permissions Are Not Consent to Unrelated Monitoring

Granting a device permission for a specific DrLoop Driver function does not create unlimited consent for unrelated:

• surveillance;
• profiling;
• advertising;
• personal monitoring.

Information collected through a permission should remain connected to properly disclosed legitimate purposes.

56. Transportation Provider Monitoring

Information generated through DrLoop Driver may be visible to your Transportation Provider for legitimate operational or workplace purposes.

A Provider may have separate responsibilities relating to:

• employee privacy;
• electronic monitoring;
• workplace policies;
• notice;
• employment law.

This page does not replace policies the Provider may separately be required to provide.

57. Access to Permissions Information

Drivers should be able to understand the main permissions used by DrLoop Driver.

Where implemented, DrLoop may provide a location such as:

Menu → Privacy & Permissions

to explain:

• Location;
• Notifications;
• Camera;
• other applicable permissions.

The exact settings available depend on the DrLoop Driver version and device.

58. Third-Party SDKs

Third-party libraries or SDKs integrated into DrLoop Driver must not be treated as automatically entitled to sensitive device permissions.

DrLoop seeks to review third-party components and limit access to what is reasonably necessary for approved functionality.

A third-party SDK must not use DrLoop Driver precise location for unrelated advertising merely because the App has been granted location permission.

59. Security

Information obtained through device permissions is protected under DrLoop's applicable privacy and security practices.

Access to sensitive information should be limited according to:

• authorized role;
• legitimate purpose;
• operational need.

No mobile or digital system can guarantee absolute security.

60. Retention

Granting a device permission does not mean information obtained through that permission may be retained indefinitely.

Retention remains subject to the purposes and retention practices described in the DrLoop Driver Privacy Notice.

Sensitive information should not be retained longer than reasonably necessary for legitimate purposes.

61. Privacy Requests

You may contact DrLoop if you have concerns about how information obtained through a Driver permission is:

• collected;
• used;
• disclosed;
• retained;
• accessed;
• protected.

This includes concerns about unexpected Driver location collection.

62. Permission Troubleshooting

If a DrLoop Driver feature is not working because an applicable permission is disabled, the App or support process may provide instructions for reviewing the device permission.

DrLoop should not request unrelated sensitive information simply to troubleshoot a permission setting.

63. Changes to Permissions

DrLoop may introduce, remove or modify Driver functionality over time.

If a materially new feature requires a materially different sensitive device permission, DrLoop should provide appropriate notice or contextual explanation before requesting the permission.

A previously granted permission should not be treated as authorization for a materially unrelated future use.

64. Changes to This Notice

DrLoop may update this Location & App Permissions notice as:

• DrLoop Driver changes;
• location functionality changes;
• operating systems change;
• device permissions change;
• applicable requirements change.

The current version will display its:

Effective Date

and:

Last Updated

Where a material change affects sensitive data practices, DrLoop may provide additional notice where appropriate.

65. Relationship to the Driver Privacy Notice

This page provides additional information about device permissions.

The DrLoop Driver Privacy Notice more broadly explains how DrLoop collects, uses, discloses, retains and protects Driver personal information.

If you have questions about Driver information beyond device permissions, refer to the Driver Privacy Notice.

66. Contact

For questions or privacy concerns about DrLoop Driver permissions:

DrLoop Inc.

Privacy Inquiry

info@drloop.ca

Please do not send unnecessary Rider or Patient medical information through ordinary email.

For concerns involving your Transportation Provider's independent monitoring or workplace practices, you may also need to contact the applicable Provider.

For an immediate emergency, contact the appropriate local emergency service.