Location-Based Service Notice for TripPing

This notice explains how TripPing handles location-related processing as part of trip safety features. It should be read together with the TripPing Privacy Policy and Terms of Service.

TripPing may process location-related information in order to:

• Use current location when a user explicitly requests it.
• Record check-ins and update member safety status.
• Attach location context to SOS events and related safety alerts.
• Support missed check-in handling and watcher notifications.
• Investigate service abuse, security issues, or safety incidents where reasonably necessary.

TripPing may use location when users explicitly trigger relevant safety features, including:

• Use current location.
• Check in.
• SOS or scheduled SOS functions.
• Trip or map screens that request location-dependent safety context.

TripPing is not intended to provide continuous always-on background location tracking as a general app mode. It is designed around explicit actions and feature-specific event handling.

Device behavior, system permission rules, connectivity, or future product versions may affect how location-related features are presented, but this notice is intended to reflect the product's current explicit-action model unless stated otherwise in the app.

• Latitude and longitude.
• Location accuracy and related technical context.
• Event timestamps associated with check-ins, SOS events, and member status updates.
• Trip and member identifiers needed to associate a location event with the relevant trip.
• Limited device or network context needed to secure, validate, or deliver the related event.

Location-related information may be shared or made available to:

• Authorized trip members according to their role and the trip state.
• Watchers or other authorized recipients of safety alerts.
• GlobalHashtag service infrastructure and supporting providers needed to operate TripPing.
• Other recipients where required by law, valid legal process, or emergency-related obligations.
• Other recipients where we reasonably believe disclosure is necessary to address an imminent threat to life, safety, or serious harm, as permitted by applicable law.

Depending on your location and applicable law, location-related processing may rely on one or more of the following: performance of a contract or requested service, legitimate interests in operating and securing the service, consent, and legal obligations.

Location-related use may also depend on device-level permission settings. You can manage location permissions through your operating system settings. If permission is denied or withdrawn, some TripPing features may not function correctly.

Location-related data is retained only as long as reasonably necessary for service operations, support, security, anti-abuse review, and legal obligations.

• Check-in and SOS location records may be retained while the related trip or account data remains in the service.
• Member location status fields may remain associated with an active or retained trip record until the related trip or account data is deleted.
• Security, fraud-prevention, or backup records may remain for a limited time where reasonably necessary.
• Third-party providers may maintain their own retention schedules under their own policies and legal obligations.

We and our service providers may process location-related information in multiple countries. If you are located in a jurisdiction that regulates international transfers, we will rely on the transfer mechanism required or permitted by applicable law, such as adequacy decisions, contractual safeguards, or other approved measures where relevant.

Depending on your location and applicable law, you may have rights that can include access, correction, deletion, restriction, objection, withdrawal of consent, portability, and information about recipients or categories of recipients.

You can also manage device-level location permissions through your operating system settings and stop using location-dependent TripPing features at any time.

• Authentication-based access controls.
• Membership and role-based visibility for trip records.
• Encryption in transit through HTTPS and TLS where supported.
• Backend validation and security rules for service access.
• Operational monitoring and anti-abuse review where appropriate.

In some jurisdictions, location-related processing may be subject to additional notice, consent, labor, telecommunications, consumer, or safety laws. You are responsible for using TripPing only where you are legally permitted to do so and for obtaining any notices or permissions required from other participants under applicable law.

TripPing location and SOS features are supplementary safety tools. In a real emergency, contact public emergency services immediately. TripPing does not guarantee successful dispatch, response time, rescue, medical support, or delivery of every location event.

Questions about location-related processing may be sent to support@globalhashtag.com.