Privacy policy

1. Who we are and current availability

SyncMap is operated by qianyu, an independent developer in Beijing, China, not a registered company. Contact: qianyu.life@gmail.com. This policy applies to SyncMap and its product/privacy pages at qianyu.fit, not to unrelated services.

SyncMap is in development. This website currently provides information only: Garmin sign-in, route planning and course synchronization are not publicly enabled. We do not currently collect Garmin account, activity or health data through this website. Sections about the integration describe its intended, limited scope. Before enabling it, we will verify that the implementation, vendors, consent flow and retention controls match this policy and publish any necessary update.

2. Data and purposes

The planned Garmin integration requests the Courses API only. It is intended to send routes selected by a user to that user's Garmin Connect account. It is not intended to import Garmin-recorded activities, heart rate, sleep, HRV, women's health information or other Garmin health records.

• User-created routes: route names, cycling/walking type, geometry, start/end points and waypoints are processed to preview/export a route and, only when requested, publish it to Garmin Connect. Routes can reveal precise locations. They are not made public by SyncMap.
• Connection information: after the integration is enabled, OAuth authorization state, tokens, the minimum account-link identifier, and course submission responses may be processed to connect the correct account, publish a course and report its status. This information is associated with the relevant SyncMap user; it is not anonymous data.
• Operational information: minimal task identifiers and result/error codes may be needed to prevent duplicate submissions, recover failed tasks and protect the service. Passwords and authorization secrets must not be included in ordinary application logs.
• Current website: loading a page necessarily transmits network/request information, including an IP address, request path and time, to our hosting infrastructure. These static pages have access logging disabled. Infrastructure error/security logs may still be generated. The pages set no cookies and load no external fonts, analytics, advertising scripts or tracking pixels.
• Support requests: if you email us, we receive your email address, request contents and any information you choose to include to resolve your request. Do not send Garmin passwords, API keys, tokens or health records by email.

Not retaining Garmin activity/health records does not mean that a route transfer can occur without processing route content or authorization information. We request only the permissions needed for the published integration and do not collect additional data merely because an API might offer it.

3. Every identified recipient and service provider

The following recipients are identified for the current information website and the planned Courses-only integration:

No third-party analytics, advertising, machine-learning, AI or other Garmin-data integration service is enabled. No CDN, external font or remote image service is used on these pages. The planned WeChat Mini Program and map/route-planning integrations are not enabled by this website. Their exact providers and data flows will be identified before deployment; no undisclosed provider is authorized to receive Garmin data.

If we add or replace a provider that receives Garmin data, we will name it and describe its purpose and data categories here before that processing begins, obtain any required approval or consent, and give users a way to decline or disconnect.

4. No sale, advertising or unrelated sharing

We do not sell, rent, trade or license Garmin user data or its derivatives. We do not share it for advertising, third-party statistics, profiling, data brokerage or unrelated commercial purposes. The only planned routine transfer is the user-requested route submission to Garmin, with the minimum technical processing by the disclosed hosting infrastructure.

Necessary disclosures may occur if required by applicable law or to investigate an actual security incident. Such disclosures must be limited to what is necessary and legally permitted. We will inform affected users when permitted and required. These exceptions do not authorize resale or AI use.

5. AI transparency and API-key restrictions

No AI system processes Garmin data in SyncMap. Garmin data and anything derived from it will not be used to train, evaluate, fine-tune or improve AI or machine-learning models. We do not send it to chatbots, foundation-model providers or external AI services. There is no AI consent setting because no AI processing is offered.

If any future AI processing is proposed and permitted by Garmin, it will remain disabled until a separate, prominent AI Transparency Statement identifies the provider, data, purpose and retention; the user gives explicit, separate opt-in consent; and a simple way to withdraw that consent is available. Withdrawing it must stop future AI processing. This would not override Garmin's prohibition on using Garmin data or derivatives for model training, evaluation or improvement.

Garmin-issued API keys are solely for the authorized developer/operator. They must not be shared with, transferred to, obtained by or used by third parties. Infrastructure hosting is not a transfer of API-key rights. We will not put keys in client code, public repositories, logs, this website or AI prompts. Third-party requests for Garmin API keys should be reported to connect-support@developer.garmin.com.

6. Choice, authorization and withdrawal

Before Garmin connection or route transfer is enabled, SyncMap will explain the requested permissions and destination and obtain the user's express authorization. Connecting an account alone will not authorize publishing arbitrary routes. The user must select the course and request its transfer. Users must not upload data they are restricted from uploading to Garmin.

You may withdraw the connection through Garmin Connect's connected-app controls or email qianyu.life@gmail.com with “SyncMap disconnect”. After withdrawal is confirmed, we will stop future API processing and remove stored connection credentials, if any. You may also request deletion of SyncMap-held data through the same address. Routes already delivered to Garmin are not automatically deleted by unlinking SyncMap; manage those routes and device copies in Garmin Connect and on your device.

The planned GPX export feature does not require connecting a Garmin account. At present, this website has no Garmin connection or consent to withdraw.

7. Storage and retention

We do not plan to retrieve or persist Garmin-recorded activity or health datasets. While the integration is unavailable, this website stores no Garmin routes, account links or tokens.

Before the integration is activated, these limits must be implemented: route content is processed only to carry out the user's request; any temporary route draft must expire within 24 hours; reusable authorization tokens, if needed, are encrypted and kept only while the account connection remains active; disconnecting or completing an applicable deletion request removes the active connection and its credentials. Any additional operational record or backup retention must be disclosed in an updated policy before it is introduced. The service will not launch with indefinite, undisclosed retention.

Current infrastructure error logs, if generated, use size-based rotation rather than a guaranteed number of days (the web-service log configuration is capped at three 10 MB files). The static SyncMap pages do not generate access logs. Support emails are retained only as needed to resolve a request and document its handling or meet an applicable legal duty; you may request their deletion. We will explain any specific legal exception and restrict the retained information.

8. Access, correction, deletion and export

Email qianyu.life@gmail.com with the subject “SyncMap privacy request” to:

• ask whether we hold your data and receive a copy;
• correct inaccurate account-link or route information held by SyncMap;
• delete your routes, connection credentials or support correspondence held by SyncMap;
• export available data in a usable format, such as GPX for a retained route or JSON/CSV for connection/task records;
• withdraw consent, disconnect Garmin or object to/restrict a particular use.

Provide the contact/account identifier used with SyncMap and the request type. We will use proportionate verification and will not ask for your Garmin password or token. We aim to acknowledge requests within 7 days and complete them within 30 days, or explain an applicable exception or delay. If a request concerns data already deleted or never collected, we will say so. Do not send a government ID unless a specific, necessary verification process has first been agreed.

For information held independently by Garmin, use Garmin Connect's privacy controls or contact Garmin. SyncMap cannot correct, export or delete data on a device or another service merely by changing its own records.

9. Security, location and children

The website uses HTTPS. The intended backend will keep authorization secrets server-side with restricted access and encrypted storage; these controls must be verified before users connect accounts. Hosting is in Alibaba Cloud's Beijing region. An expressly requested transfer to Garmin may be processed in the locations described in Garmin's privacy notice; we do not represent that every Garmin copy remains in China.

SyncMap is not directed at children under 18. We do not knowingly collect their Garmin data. If you believe a child has provided data, contact us so we can investigate and remove it. No internet service can promise absolute security; contact us if you suspect unauthorized processing.

10. Updates and contact

We will update the date and version when this policy changes. Before changing purposes, adding recipients or enabling new processing, we will provide notice and seek additional consent where required. A policy update alone does not authorize a new use of Garmin data.

English and Chinese versions describe the same intended practices. If a translation discrepancy affects your request, contact us for clarification. SyncMap is an independent product, not a Garmin product or an endorsement by Garmin.