Privacy policy

Who this policy covers

Garmin TXT Reader provides a web service and a Connect IQ watch application for moving selected TXT chapters to compatible Garmin watches. In this policy, “we,” “us,” and “the service” refer to Garmin TXT Reader.

Garmin TXT Reader is an independent application and is not affiliated with or endorsed by Garmin Ltd. Garmin and related product names are trademarks of their respective owners.

Information we process

Google account and authentication data

Google sign-in provides your Google account identifier, verified email address, display name, and profile image URL. We use these fields to create and identify your Garmin TXT Reader account. We do not request Google Drive or Gmail data, and we do not retain Google access or refresh tokens.

We also process hashed session tokens, OAuth state and nonce hashes, login and session timestamps, and an essential first-party session cookie. The cookie is HttpOnly, SameSite=Lax, and limited to the Garmin TXT Reader domain.

TXT library and transfer data

When you save a book, we store the uploaded TXT source, generated chapter and watch sections, immutable transfer blocks, title, optional author, source file name, size-related metadata, integrity hashes, selected chapters, target watch, queue state, delivery receipts, and transfer errors. Your browser detects the source encoding and sends normalized text to the service. TXT content is stored in private Cloudflare R2 objects; related metadata is stored in Cloudflare D1.

Watch and pairing data

We process a device identifier, Garmin part number, resolved model name, optional custom device name, reported firmware, pairing status, last-seen timestamps, and watch credentials. Our database stores digests of pairing codes and watch bearer tokens rather than reusable plaintext credentials. The watch keeps the active token in its local application storage. A Garmin part number identifies a model family, not a unique person.

Billing data

Stripe hosts Checkout and subscription management. We send Stripe the email and display name associated with your account, an internal user reference, and the plan you choose. We store Stripe customer, Checkout Session, price, and subscription identifiers together with Checkout attempt and link metadata, plan interval, status, trial and renewal dates, and entitlement state. We do not receive or store complete payment-card numbers.

AI chapter-analysis data

After you confirm the detected encoding, AI chapter detection runs by default. Your browser first analyzes the complete file locally. It then sends a bounded structural summary to our server and DeepSeek: document counts, cluster statistics, a source digest, and up to a few short candidate heading examples per cluster. A disclosure guard rejects requests whose heading samples would exceed 20% of the source. We do not intentionally send the complete book or ordinary chapter body text to DeepSeek.

Security and operational data

We process timestamps, request outcomes, error codes, and hashed rate-limit subjects. An IP address is converted to a keyed hash for pairing-abuse controls; the raw address is not stored in the application rate-limit table. Cloudflare may process network and request-log information while hosting and protecting the service.

Support communications

If you contact support, we process the email address, message, troubleshooting details, and attachments you choose to send. Support email is handled through Google email services. Please do not send passwords, payment-card data, credentials, pairing codes, watch tokens, or complete copyrighted books.

Website analytics

With your permission, the international site loads Google Analytics (measurement ID G-Y1VHJNQL4M) to measure visits, Store-link clicks and successful setup steps observed by the browser, such as sign-in, pairing, book import and completed sync. URLs sent by our integration omit query strings and fragments; private routes use generic labels. We do not send email addresses, book text, pairing codes or device credentials. Optional browser storage keeps the analytics preference and short-lived event-deduplication markers. You can refuse or withdraw permission in Analytics choices without losing access to the reader. Browser privacy signals are respected, and advertising personalization is disabled. The domestic site does not load this integration.

How we use information

• Authenticate you and keep your account secure.
• Store, split, display, and deliver the TXT content you choose.
• Pair and manage compatible Garmin watches.
• Maintain a device-specific transfer queue and recover interrupted downloads.
• Provide AI-assisted chapter detection and enforce fair-use limits.
• Provide Checkout, subscription management, and paid-access decisions.
• Prevent abuse, investigate failures, and operate and improve the service.
• Comply with legal obligations and enforce our terms.

We do not sell personal information or serve behavioral advertising. Optional usage analytics helps us improve the product and content; it is not required to use the service.

Service providers and disclosures

We disclose information only as needed to operate the service:

• Cloudflare hosts the Worker, D1 database, private R2 storage, static assets, and operational logs.
• Google provides OpenID Connect sign-in and the profile fields you authorize. On the international site, Google Analytics processes optional usage and setup events only after analytics permission, as described above.
• Stripe processes payments, subscriptions, billing-portal activity, and related fraud and compliance data.
• DeepSeek processes the bounded structural prompt when AI chapter detection runs.
• Garmin infrastructure may carry network requests made by the Connect IQ application, including through Garmin Connect’s system network bridge on supported devices.

These providers may process data in countries other than your own under their own terms and privacy notices. We may also disclose information when required by law, to protect users or the service, or as part of a business reorganization subject to appropriate safeguards.

Authorized operators may access the account, book-title and author, device, transfer, billing, and support metadata needed to troubleshoot the service, respond to requests, protect accounts, and perform manual deletion. They are not provided a general-purpose interface for reading or downloading TXT book contents.

Retention and deletion

Cloud books and their transfer metadata remain available until you delete a book or submit a verified account-deletion request. The proposed 30-day cleanup policy for inactive non-subscribers is not currently enabled. If we enable an automatic cleanup policy later, we will update this policy and provide the promised warning before deletion.

• Web sessions are issued for up to 30 days and can be ended by signing out.
• Four-digit pairing sessions expire after 10 minutes.
• AI advice cache entries are no longer eligible for reuse after 30 days; expired database rows may remain until later maintenance. Keyed abuse and cost counters use bounded rolling windows.
• Downloaded copies remain on your watch until you remove them or reset the watch application.

Expired security records, backups, infrastructure logs, Stripe records, and records required for fraud prevention, accounting, dispute handling, or legal compliance may remain for a limited period according to operational needs, provider policies, and applicable law. We do not use retained data for unrelated marketing.

Security

Transfers use HTTPS. Our server-side database stores digests of session tokens, pairing codes, watch bearer tokens, OAuth state, and rate-limit subjects rather than reusable plaintext credentials. Your browser cookie and watch application necessarily retain the active credentials they use. TXT objects use private, user-scoped storage keys. No system is completely secure, so please contact us if you believe your account or watch token has been compromised.

Connect IQ Fit permission

The watch application uses the Connect IQ Fit permission only to create a temporary, generic activity-recording session that helps keep a long transfer alive. The session is stopped and discarded when the transfer ends. Garmin TXT Reader does not read, retain, or upload health, workout, location, sensor, or fitness metrics from it.

Your choices and rights

• Delete individual cloud books from your signed-in library.
• Rename a watch or revoke its access and remove it from the active Devices list.
• Manage or cancel a subscription from the Stripe customer portal on the Billing page.
• Review AI chapter suggestions, switch to a local chapter rule, or manually correct chapter boundaries before saving or syncing.
• Sign out to revoke the current browser session.

Request deletion of your account and associated cloud data.

Depending on where you live, you may also have rights to access, correct, export, restrict, object to, or delete personal information, and to complain to a privacy authority. We may need to verify your identity before fulfilling a request.

Children

The service is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. If you believe a child has provided information to us, contact us so we can investigate and remove it where required.

Changes to this policy

We may update this policy as the service, providers, or legal requirements change. The effective date at the top identifies the current version. Material changes will be communicated through the service or another appropriate channel when required.

Contact

Questions and privacy requests are handled manually by Garmin TXT Reader support.