Privacy Policy

This Privacy Policy explains how littlefrogprojects handles personal data when you use the public website and Coach, our workout-building product.

It is written to reflect the product as it operates today, including Clerk authentication, Garmin OAuth, OpenAI-powered workout parsing, saved workout storage, and analytics.

Account and authentication data: When you sign in, authentication is handled by Clerk. We receive the Clerk user ID and the account information needed to provide login-protected product features.

Workout and product data: If you use Coach, we store the workout text you submit, generated workout structures, saved workouts, pace profiles, schedule dates, and workout history needed to operate the product.

Garmin connection data: If you connect Garmin, we store the Garmin user ID plus Garmin access and refresh tokens and token expiry metadata. Garmin tokens are encrypted at rest before they are stored in our database.

Usage and diagnostics data: We use Vercel Analytics on the website and Coach. We also generate operational logs that can include request path, host, request IDs, IP-derived request metadata, and Clerk user ID where available. Sensitive token-like fields are redacted from application logs.

To authenticate users and provide account-based features.

To generate structured workouts from your prompt. Coach sends workout text and, when available, your saved pace profile to the OpenAI API so it can return a structured workout draft.

To save, load, and manage workouts, pace profiles, and workout history inside Coach.

To connect to Garmin, refresh Garmin tokens when needed, and create or schedule workouts in your Garmin account when you request it.

To measure usage, improve reliability, enforce rate limits, and investigate product issues or abuse.

Clerk provides authentication and account session management.

OpenAI processes workout prompts and related pace-profile context for workout generation.

Garmin receives data when you connect your Garmin account or create or schedule workouts through the Garmin integration.

Vercel Analytics is used for basic product and website analytics.

Our application infrastructure and database providers may process data on our behalf to host and operate the service.

Garmin connection is optional. If you do not connect Garmin, Coach can still parse workouts and save drafts, but it cannot create or schedule workouts in Garmin.

If you disconnect Garmin from within Coach, we delete the Garmin tokens we store for your account.

Garmin may separately process data under Garmin’s own terms and privacy policies once you authorize the integration or send data to Garmin.

We keep account-linked product data for as long as it is needed to operate your account and the features you use, unless you delete it earlier or ask us to remove it.

Saved workouts and workout history remain in the product until deleted or until the account data is removed.

Garmin tokens remain stored until disconnected, replaced, expired, or removed as part of account/data deletion workflows.

Operational logs and analytics data may be retained for security, reliability, and product operations for a limited period determined by our providers and operational needs.

You can choose not to sign in, but some Coach features will not be available.

You can connect or disconnect Garmin from Coach.

You can delete saved workouts from the product UI.

You can contact us to request account or data deletion.

We use reasonable technical and organizational measures to protect the product, including encryption for stored Garmin tokens and redaction rules in server logs for sensitive fields.

No system can be guaranteed to be perfectly secure, so you should also protect your own account credentials and connected third-party accounts.

We may update this policy as the product changes. When we do, we will update the effective date on this page.