Back to Home返回首页

Security

Last updated: May 13, 2026

We take the security of your data seriously. This page describes how we protect your information at every stage of the pipeline.

1. Password Handling

Your Garmin password is never stored. It is used exactly once during the initial authorization to perform a token exchange with Garmin Connect. The password exists only in memory for the duration of this exchange and is immediately discarded afterward. It is never written to disk, never logged, and never transmitted to any system other than Garmin's authentication servers.

2. Token Encryption

After the one-time authorization, the resulting Garmin session token is encrypted at rest using Fernet symmetric encryption (part of the Python cryptography library). Fernet provides:

The encryption key is stored separately from the encrypted tokens.

3. Data in Transit

4. Infrastructure

5. Email Security

Reports are delivered via Resend using TLS-encrypted connections. We use SPF, DKIM, and DMARC records to help prevent email spoofing and ensure report emails are authenticated.

6. AI Processing

When health metrics are sent to the LLM API for analysis, they are transmitted as anonymized numerical data only. No personal identifiers (name, email, Garmin username, or account ID) are included in AI requests. The LLM provider does not receive any information that could identify you as an individual.

7. What We DO Protect

8. What We Do NOT Store

9. Responsible Disclosure

If you discover a security vulnerability in our Service, we ask that you disclose it responsibly. Please email us with details of the vulnerability, steps to reproduce, and any relevant supporting information. We will acknowledge receipt promptly and work to address the issue.

Report a Security Issue

Email: dailyreport@garminhub.com

Please include "SECURITY" in the subject line for prioritized handling.

Garmin Daily Report is not affiliated with Garmin Ltd. or its subsidiaries. Garmin and Garmin Connect are trademarks of Garmin Ltd.