LureGo · YUJI
LureGo Privacy Policy
We value your privacy. This policy explains how LureGo processes, stores and protects personal information when providing fishing records and the Apple Watch experience.
Effective date
8 October 2026
Policy version
2.4
WeChat sign-in and linking amendment · 17 October 2026
01
Scope
This policy applies to the LureGo/YUJI iPhone app, companion Apple Watch app and directly related services provided by 六号网络科技（漳州市龙文）有限公司 (‘we’).
LureGo helps lure anglers record fishing trips, organize catches, review routes and view activity. We process information only as needed for these features. Health, activity and location data are not used for advertising, marketing or unrelated analytics.
02
Accounts and nickname content review
When you sign in with Apple, we process your Apple account identifier and credentials and store the email Apple provides (possibly a relay address), internal user identifier, nickname and nine-digit LureGo ID for authentication, account management and record association. The app still requests Apple’s name permission and may send name fields with a sign-in request; the server does not store that field when opening the account or use it as a nickname. Avatars are stored only on the device. The default nickname is ‘钓友’ followed by the last four ID digits.
When you choose WeChat sign-in and agree to the terms, the app uses the WeChat Open Platform SDK to open WeChat authorization. We process a one-time authorization code and the necessary account identifiers returned by WeChat (openid and unionid when provided) to authenticate you, associate WeChat with your LureGo account and issue a sign-in session. A linked WeChat identity signs in to the original account; an unlinked identity creates a new account. Data from different accounts is not merged automatically. Sign-in authorization does not include cloud backup of photos.
Nickname moderation is enabled. A change is first checked against local rules and word lists, then the text and a random request ID are sent to Tencent Cloud’s text-content safety service. Account IDs and LureGo IDs are not sent. Rejected changes or changes when review is unavailable are not saved; violating names may be reset to the default. Our server does not retain the raw moderation request. Tencent’s processing and retention follow its terms.
LureGo IDs are randomly assigned nine-digit numbers, remain unchanged for the account’s life and are not recycled after deletion. 000000001–099999999 are reserved for official accounts and are not assigned to ordinary users.
03
Information we process
Trips and catches
When you create a trip, we process the time, duration, casts, catch counts, species, dimensions, gear, notes and other information you enter or the app generates during fishing. This saves records, shows statistics, supports personal review and synchronizes to the server when a network is available.
Location and routes
With location permission, LureGo may record places and routes during fishing, including while the screen is locked; location recording for that purpose stops when fishing ends. Precise location is sensitive information and is processed only when the related feature is enabled. Ordinary trip sync includes place names, but current requests do not include start/end coordinates; continuous routes remain on the device. Atlas numbering derives city/province from photo location or authorized location and submits region codes to the atlas service. Photo uploads and associated information are described under ‘Atlas numbering and photo verification for upgrades’. Separately enabled Safety may process foreground and authorized background location as described below; ending a trip does not mean Safety is disabled.
Camera, photos and photo library
The app accesses the camera or photo library when you take or choose a catch photo. Catch photo files are stored locally for your catch archive. Cloud identification, identification feedback and atlas photo eligibility verification upload relevant photos as explained below. Ordinary catch sync may include an identifier linking the local photo and catch, but the identifier does not contain the photo itself.
Fish-identification data
Cloud identification uploads your photo to LureGo’s identification service. EXIF, including capture location, is removed and the photo compressed in server memory before being sent to the Doubao model on Volcengine Ark (北京火山引擎科技有限公司). The real-time identification service does not retain that request’s photo or write it to a database or log. Subsequent confirmed or corrected feedback is stored through a separate process described below.
The app also uses local models for image analysis and fish segmentation; local processing itself does not require uploading. Removing EXIF does not remove people or locations visible in the image. Submit photos focused on the fish where possible.
Atlas numbering and photo verification for upgrades
After installing this update, the first app launch attempts a one-time safe sign-out of the current local account, preserving local catches, photos, atlas data and existing numbers. If the network or another issue prevents completion, the old login is not restored and the app asks you to retry. Before signing in again with Apple, read and actively tick acceptance of the terms and this privacy policy; new registrations use the same process. Local features remain available without signing in. New atlas verification photos are not submitted before the updated policy is accepted and sign-in completed. After sign-in, the app submits photo evidence for the current account’s synchronized atlas catches to verify upgrade eligibility, allocate regional numbers and prevent duplicate-image credit. Opening the atlas, saving/syncing catches or returning to the foreground may trigger pending verification; existing catches may also be verified. Unlock and upgrade counting follows the app’s ‘Identification and atlas rules’.
Before upload, the app converts the photo to JPEG with a longest edge of at most 2048 pixels. GPS, author and device serial metadata are removed, but limited camera make/model, lens parameters and original capture-time fields are retained to assess genuine capture. People or places may remain visible. After reading necessary camera information, the server saves a private JPEG stripped of embedded metadata with a longest edge of at most 768 pixels. It does not publish photos or persist the larger upload. Verification results and photo digests are associated with your account and catch. Screenshots, images without verifiable camera information and duplicates do not count toward upgrades.
Deleting the corresponding server catch or account deletes associated verification records; cleanup removes the private photo copy. To prevent a qualifying photo being credited again after deletion, the server retains a pixel digest without account or catch identifiers and an internal test-pool flag. The digest is not a photo file but can match later submissions of the same image. Contact us under ‘Your rights and account deletion’ for requests.
Identification feedback and improvement
Adding a cloud result to your keepnet or explicitly confirming a corrected fish name submits identification feedback. It includes an account-linked fish photo, original result, confirmed/corrected name, action time and necessary identification status, model version or error details. Photos are stored without EXIF in a restricted private directory. Merely viewing a result is not confirmed feedback.
Feedback is used to review results, investigate issues and improve accuracy. Receipt does not mean a label is automatically adopted or training automatically starts. Request deletion by contacting us; account deletion also cleans up associated feedback and photos.
Health and activity data
With explicit permission, HealthKit may supply fishing-related workouts, workout routes, heart rate, active energy and walking/running distance to show activity during fishing. Apple Watch writes fishing workouts and GPS workout routes to Apple Health, preserving session times, routes and activity summaries. Individual heart-rate readings and raw HealthKit samples are not uploaded to our server. Trip sync may include summary energy and distance.
Motion & Fitness
With permission, device motion/fitness capabilities identify fishing movements and count casts, primarily on-device. Supported Apple Watch models also process motion anomalies, depth and submersion to generate water-risk notices. These notices are not medical diagnoses.
Apple Watch synchronization
Paired iPhone and Apple Watch exchange necessary fishing status, timing, casts, catch counts and activity information for viewing and recording. With permission, Apple Watch creates fishing workouts and GPS routes in Apple Health. This processing does not create advertising profiles.
Server synchronization
Sync may process record IDs, titles, start/end times, place names, weather summaries, cast/catch counts, active energy, distance and catch species, dimensions, weight, lures and notes. Ordinary trip sync excludes latitude/longitude; Safety location uploads are separate. Server sync saves/restores fishing information, supports service operations and handles support requests.
05
Weather and support tickets
From version 1.0.6, weather uses only Apple WeatherKit. Coordinates are rounded to two decimal places before the request; precision varies with latitude and other conditions and does not mean the data is anonymous. If Apple Weather is unavailable, the app shows weather as unavailable without querying another provider. You can disable location permission in system settings without affecting unrelated core features. The following existing fallback disclosure applies to version 1.0.5 and earlier: Weather uses Apple WeatherKit first. If it fails, the app sends latitude/longitude rounded to two decimal places to Open-Meteo outside mainland China; precision varies with latitude and other conditions. The request includes your network IP but no account information, and Open-Meteo processes it outside mainland China. Reduced coordinate precision and omission of account data do not make the information anonymous. Overseas weather processing requires legally applicable specific notice and separate consent; system location permission or a general sign-in checkbox does not replace that consent. You may disable the relevant location permission and email us to restrict or stop this overseas processing without affecting unrelated basic features.
For support feedback, we process category, text, screenshots you select, ticket/message IDs, account association and processing status. Text and screenshots are stored in the server database for authorized support staff. Alibaba Cloud Direct Mail (阿里云计算有限公司) sends ticket alerts only to LureGo support mailboxes, containing ticket number, LureGo ID and feedback content. Replies may arrive in-app or through APNs. Do not submit unrelated sensitive information.
06
LureGo Safety
Recipients authorized for an active event may view its precise location before tapping to participate. After you participate, your relative direction, distance and status are shown to authorized viewers. Location disclosure may expose where you are active. Enable the feature only as needed.
Enabling Safety/nearby alerts or requesting water-incident help may upload coordinates, accuracy, capture time, source, event time, trip-session IDs and response status to Safety for matching, notifications, maps and event handling. Location may update in the foreground and authorized background execution. A full fishing route is distinct from Safety updates. Participant locations are uploaded to show relative direction, distance and update time to authorized viewers.
The first round immediately matches eligible users whose location within the past 12 hours was within 3 km. After 30 seconds, if no more than one responder is going or has arrived, round two expands to eligible locations within the past 24 hours and 5 km. Matching requires accuracy of 100 m or better. Network, system and location conditions may affect alerts. Authorized recipients may view precise active-event locations before confirming participation.
With permission, we upload APNs device tokens, device identifiers and notification settings for Safety and reply alerts. Disabling features or signing out deactivates/unlinks them; network failures may delay completion. Emergency calls open only the system calling interface for your confirmation; the current Chinese policy references 119/120. The app does not automatically call on your behalf. The emergency-contact settings entry was removed; historical names, numbers and relationships remain locally and may appear during help. The whole address book is not read.
Read the LureGo Safety Privacy Notice and Safety Service Agreement.
07
System permissions and sensitive information
Precise location, movement routes and health information are sensitive: location supports routes, weather and Safety; health data supports activity review. Disclosure may expose places and health conditions. Declining processing affects only related features. Authorization is explained below.
Location, camera, photos, HealthKit, Motion & Fitness and notifications are optional choices. Photos support catches, avatars, identification or support screenshots. Original library photos may include time/GPS used for local organization. Declining optional permissions does not affect unrelated features. Withdraw permission in iPhone Settings, Health or the relevant app feature.
Sign-in requires actively ticking acceptance of the terms and privacy policy. Signed-in users may read and accept updates requiring renewed confirmation. An unticked box is not consent. System dialogs separately authorize location, notifications and health, with withdrawal in settings. Nearby Safety requires separate acceptance of its agreement and privacy notice. A system permission does not replace feature-specific consent or authorize undisclosed network processing.
08
Third-party services and entrusted processing
We do not sell or rent personal information or provide health, location or photos to advertising platforms. Entrusted processing must limit purpose, scope and safeguards. Independent recipients require notice and separate consent where legally required. The following distinguishes system capabilities, remote services and user-initiated links; these are not all embedded third-party SDKs.
The WeChat Open Platform SDK (Tencent) is registered only when you initiate WeChat authorization. It opens WeChat, receives the authorization callback and supports sign-in or linking. The app sends the necessary one-time authorization information to LureGo’s identity service, which authenticates it with WeChat Open Platform. The app does not read your WeChat password, chats or contacts. If you decline WeChat authorization, you can sign in with Apple or continue using local features.
• Apple: Sign in with Apple handles identifiers and authorization; HealthKit/WatchConnectivity handle local and paired-device health/activity; maps, location and WeatherKit handle location requests; APNs handles device tokens and necessary notifications. See Apple’s privacy policy.
• Tencent Cloud (腾讯云计算（北京）有限责任公司): servers/storage in Shanghai, mainland China, retain account, trip, Safety and support data. Text safety receives nickname text and a random request ID, not account or LureGo IDs. Tencent’s processing/retention follow its terms. See its privacy statement.
• Volcengine Ark/Doubao (北京火山引擎科技有限公司): receives photos stripped of EXIF, including location, and compressed in server memory for real-time identification. LureGo’s real-time service does not retain that request photo; LureGo separately retains confirmed/corrected feedback under the feedback rules above.
From version 1.0.6, the app no longer queries Open-Meteo. The following provider disclosure is retained for users of version 1.0.5 and earlier. • Open-Meteo: outside mainland China, receives coordinates rounded to two decimals and network IP for weather, without account information. See its terms and privacy information.
• Alibaba Cloud Direct Mail (阿里云计算有限公司): sends ticket alerts only to LureGo support, including ticket number, LureGo ID and feedback.
• External maps: Apple Maps, Amap or Baidu Maps receive necessary navigation coordinates/parameters only after you choose navigation. The selected provider’s privacy policy applies. See Amap’s agreement/privacy page, Baidu’s privacy policy and Apple’s policy linked above.
09
Storage and protection
From version 1.0.6, weather queries use only Apple WeatherKit. The fallback-weather information below applies to version 1.0.5 and earlier. Servers/storage use Tencent Cloud (腾讯云计算（北京）有限责任公司) in Shanghai, mainland China. Open-Meteo processes fallback weather requests outside mainland China as described above.
Photos, avatars, catches and historical contacts are stored on the device; cloud photo verification and identification feedback also retain private copies as described. Device backups and Health data may remain after deletion/uninstallation and require separate Apple settings. Cloud information is retained only as long as necessary. Local deletion, sign-out and account deletion are distinct; local deletion should not be assumed to remove all cloud copies.
Account information, trips, catches, support feedback and identification corrections remain until you delete the content or account. Atlas verification copies/records and retained deduplication digests follow the atlas-verification rules above. Server-accepted deletion immediately disables the account and starts cloud cleanup; some files are removed shortly afterwards. Backups retain only the last 14 days; deleted account data is removed within 15 days. Safety keeps only the latest location, replacing the previous one. Help events and related push/response records remain for 90 days after the event ends and are then automatically deleted; account deletion removes them immediately. Our server does not retain raw nickname-review requests.
Information with an unexpired statutory retention duty, or temporarily technically difficult to delete/anonymize, is kept solely for necessary storage and security, not nearby matching, location display or unrelated purposes. It is cleared when the basis ends. Necessary cybersecurity logs are legally retained for at least six months; personal-information impact assessments and required processing records for at least three years. This does not mean all precise locations, photos or health samples must be kept for those periods.
We use access controls, transport protection and minimal access. Personal-information incidents trigger remedial measures and legally required notices.
10
Your rights and account deletion
You may access, copy, obtain a copy, correct, supplement or delete information, withdraw consent, restrict unnecessary processing, delete your account and request explanations. View/edit local records, manage permissions or contact support@luretrack.com, including for server-record deletion. We verify identity proportionately and handle requests lawfully, explaining refusals and remedies. You may request transfers meeting statutory conditions. Complaints, withdrawal and deletion requests use this email; we promptly accept them and reply within 15 working days with the result or progress/reasons, without unrelated conditions.
Confirm deletion in Profile → Account → Delete account. Server acceptance immediately disables the account and invalidates all device sessions, starts cloud business-data cleanup and revokes Sign in with Apple. Retention rules explain deadlines and legal exceptions. Local LureGo data is cleared; system Photos and Apple Watch data are unaffected, and offline copies on other devices do not automatically disappear. Signing in later with the same Apple ID creates a new account. A failed network or unconfirmed status requires checking the app or contacting us; tapping alone is not proof all processing finished. You may also request deletion by emailing support@luretrack.com; we handle it within 15 working days.
LureGo IDs are random nine-digit identifiers, unchanged for the account’s life and never recycled after deletion. 000000001–099999999 are reserved for official accounts. Withdrawal does not affect lawful processing before withdrawal.
11
Minors and special rules for children’s information
Information about children under 14 is sensitive. They must not independently enable location sharing or the real Safety network. Guardians must first contact support@luretrack.com to request use or exercise rights, read these special rules and notices, and provide lawful consent. An ordinary account checkbox or system permission is not guardian consent. Without verified valid guardian consent, related processing must not be enabled. We stop and take necessary measures, including deletion, if children’s information was processed without valid consent. Users aged 14–17 should use the app with guardian guidance.
Children’s information is used only for explained, necessary features, within the categories, recipients and periods in this policy and Safety notices; never advertising, marketing or unrelated profiling. Guardians may decline unnecessary processing or request access/copy/correction/deletion/withdrawal by email. We verify identity/guardianship proportionately without unrelated documents. Refusal/withdrawal does not remove emergency-number access or other features not needing the information. Material purpose/method/category changes require fresh guardian consent where legally required.
The operator named in this policy receives children’s rights requests and assigns dedicated staff. Children’s sensitive information and online location sharing must not be processed/enabled without valid guardian consent.
12
Policy updates
This update explains atlas photo verification and retained deduplication digests after deletion. Visiting a webpage or installing an update is not consent. Registration/sign-in requires reading and actively accepting the current terms and policy; signed-in accounts must reconfirm before new photo processing begins. New processing must not be enabled before the necessary valid consent.
We may update this policy as features, processing or applicable rules change. Material effects on your rights are explained through in-app notices, the website or other appropriate means, with renewed consent where required.
13
Contact us
For questions about this policy, personal-information processing or rights requests, contact us below.
Personal-information processor
六号网络科技（漳州市龙文）有限公司
Official website
www.yujiapp.cn
support@luretrack.com
© 2026 LureGo · YUJI