LureGo SAFETY NETWORK

LureGo Safety Privacy Notice

This supplements the LureGo Privacy Policy and explains Safety location, notifications and data rights.

Effective date

30 September 2026

Notice version

2.2

Scope

This notice covers the Safety Network pages, mutual help, water-incident requests, nearby alerts and location sharing provided by 六号网络科技（漳州市龙文）有限公司.

This covers specialized Safety scenarios only. Read the main privacy policy for ordinary trips, catches, routes, HealthKit, Motion & Fitness and Apple Watch processing.

Processing scope

After help is requested, recipients with valid event authorization may view the active event’s precise location before tapping to participate. Participants’ relative direction, distance and status are also shown to authorized viewers. This may expose where you are active. Refusal or withdrawal does not affect unrelated basic features.

Once the feature is enabled and authorized, location is uploaded to Safety for nearby matching and request display; it is not kept solely on your device. Watch heart-rate snapshots may support local notices between paired devices; current help-creation requests do not contain heart-rate samples.

Information in the current version

Safety settings, consent status, event caches and historical emergency-contact names/numbers/relationships are local. The contact-settings entry was removed, but historical data may still appear on help pages. The whole address book is not read. Network processing includes event/user/device IDs, coordinates, accuracy, capture time, source, event time, response status and notification delivery information.

Online processing rules

Upload frequency depends on foreground/background state, permissions, movement and enabled features. Fishing/help may involve continuous location, including authorized background updates; no fixed interval is guaranteed. Coordinates, accuracy and time are uploaded. Nearby matching needs accuracy within 100 m; storing a coarse location does not make it eligible for matching.

Round one immediately matches eligible users located within 3 km in the past 12 hours. After 30 seconds, if no more than one responder is going/has arrived, round two expands to 5 km and the past 24 hours. Recipients need a valid location, normal account, enabled alerts and an available notification device.

For active events, initiators, valid participants and authorized recipients may read precise location; recipients need not participate first. Closure, expiry or revocation restricts other users’ access. Do not forward another person’s location without authorization. Participants’ locations are also uploaded so authorized viewers see relative direction, distance, status and update time. Server event records include notification and response status.

Only the latest Safety location is kept; each update replaces it. Events and related push/response records are retained for 90 days after the event ends, then automatically deleted; account deletion removes them immediately. Backups cover only 14 days; deleted account data is removed within 15 days. The 12/24-hour matching windows and default two-hour event validity are not deletion deadlines.

Event/processing records support delivery/response review, complaints and security, not advertising or unrelated profiles. Precise location is no longer shown to other users after closure, expiry or revocation. Information subject to unexpired legal retention or temporary technical deletion/anonymization limits is kept solely for necessary storage/security, not matching, location display or unrelated use, and cleared when the basis ends. Necessary security logs are retained at least six months; impact assessments and legally required processing records at least three years. These periods do not require all locations, photos or health samples to be kept that long.

Permissions and separate consent

Nearby Safety requires separate acceptance of the Safety agreement and this notice. Relevant features must explain the necessity of sensitive processing, viewers and risks. System permissions do not consent to all online sharing; webpage reading is not separate consent. Alerts require notification permission; foreground/background location requires corresponding authorization. Location, notifications and health are separately authorized in system dialogs and revocable in settings. Precise location/movement is sensitive and may be shown to participants and authorized recipients, exposing your whereabouts. Declining permissions or disabling Safety does not affect unrelated basics.

The 119/120 buttons described in the Chinese policy only open the system calling interface. You decide whether to call; the app does not call on your behalf.

Sharing, entrusted processing and disclosure

Safety uses Tencent Cloud (腾讯云计算（北京）有限责任公司) servers/storage in Shanghai, mainland China. APNs processes device tokens and necessary notifications. Navigation coordinates are passed to a chosen map only when you open navigation. Provider/privacy links are in the main policy. Safety location is not used for advertising or unrelated profiling.

APNs tokens and device IDs are uploaded for push. Disabling/sign-out deactivates/unlinks them, potentially delayed by offline state or failed requests. Historical contacts stay local; the app does not automatically text or call them.

Information security

We limit processing to what is necessary and use risk-appropriate access controls, transport protection and incident response. Networks/devices cannot be absolutely secure. We take remedies and give lawful notice for personal-information incidents affecting rights.

Your rights

Disable Safety/nearby alerts, revoke location/notification permission or email support@luretrack.com for access, copies, correction, deletion or account deletion. Disabling reception, leaving an event, ending your own request and revoking location are distinct actions; check each state. Ending ordinary fishing does not stop Safety location updates. Revoking permission does not automatically delete existing cloud data. Email explicit requests to withdraw Safety processing consent, stop sharing or delete records. Offline/failed requests may leave server state unchanged; do not assume withdrawal completed. Identity verification is proportionate, and withdrawal does not affect prior lawful processing.

Confirm deletion in Profile → Account → Delete account. Server acceptance immediately disables the account and all device sessions, cleans cloud business data and revokes Apple authorization. See retention rules for deadlines/exceptions. Local app data is cleared, not system Photos or Watch data; offline copies elsewhere do not automatically disappear. Later sign-in with the same Apple ID creates a new account. For network failure/unconfirmed status, check the app or contact us; tapping alone does not complete all processing. You may email support@luretrack.com; we handle requests within 15 working days. See the main privacy policy.

Protection of minors

Under-14 information is sensitive; children must not independently enable location sharing or the real Safety network. Guardians must contact support@luretrack.com first, read the special rules/notices and give lawful consent. Account checkboxes/system permissions are not guardian consent. Without verified valid consent, related processing must not be enabled. We stop processing and take necessary measures, including deletion, if children’s data was processed without valid consent.

Notice updates

This update clarifies precise-location viewers, withdrawal/deletion and statutory liability boundaries. Webpage visits are not consent, and a webpage version does not replace actual app confirmation. Changes to purpose, method or information categories require renewed consent before processing, as do other legally applicable cases. New processing must not start without necessary valid consent.

We update this notice when information types, purposes, location frequency, viewers, retention, providers or rights procedures change. Material changes are prominently announced in-app, on the website or otherwise, with renewed consent where required.

Contact us

Personal-information processor

六号网络科技（漳州市龙文）有限公司

support@luretrack.com

Related reference

Special service agreement

LureGo Safety Service Agreement

Safety Agreement