Skip to main content

Privacy Policy

Last updated April 15, 2026.

We respect your privacy. This policy explains what we collect, why we use it, and how you can exercise your choices—including GDPR-focused detail and subprocessors further down the page.

0. Introduction

TrainingLogger (“we,” “us,” or “our”) explains how we handle your information when you use this training log app. This policy covers global privacy notices where applicable, including GDPR (EU/EEA), UK GDPR, California (CCPA/CPRA and CalOPPA), Brazil's LGPD, Canada's PIPEDA, Australia's Privacy Act, Singapore's PDPA, and Japan's APPI.

1. Information we collect

Account and authentication. We use Clerk to handle sign-in, sign-up, sessions, and account security. Your account is required to use TrainingLogger.

Training records you enter. Workouts, exercises, sets, reps, weight, notes, and similar fields you save are stored in our Postgres database (hosted by Railway) and tied to your account so you can view history, track progress, and continue logging seamlessly.

Technical data. Like most web apps, we collect basic technical information needed to operate the service: browser type, OS, referring URL, pages visited, time on page, and IP address. This helps us diagnose issues, improve performance, and prevent abuse.

2. How we use information

We use the data above to:

  • Operate the app, show your training history, and track progress
  • Authenticate you and protect accounts from abuse
  • Diagnose issues, improve performance, and keep the service secure

We do not sell, rent, or trade your information for marketing. We do not use your data for profiling or behavioral advertising. We share data only with essential service providers who help us run the product (authentication, hosting, and database), or when required by law.

3. Third-party services

We use only essential third parties to deliver the app. Your data is processed only as needed for their stated role:

Subprocessors, purposes, and privacy links
ProviderPurposePrivacy
ClerkAuthentication, sign-in, sessions, and account securityclerk.com/legal/privacy (opens in new tab)
RailwayHosting the application and managed Postgres database for training recordsrailway.com/legal/privacy (opens in new tab)
CloudflareDNS and related network services for our domain namescloudflare.com/privacypolicy (opens in new tab)
Bunny FontsWeb font deliverybunny.net/privacy (opens in new tab)

4. How data is stored

Clerk manages sign-in, sessions, and authentication account data. Training records and other application data you save in TrainingLogger are stored in Postgres on infrastructure operated by Railway, following their security and privacy practices for managed databases and hosting. We keep your data while your account is active and as needed to operate the service. If you delete your account or request removal of data we control (for example, training history in our database), we will comply where we can reasonably do so, subject to legal or security requirements. Some authentication data may be processed or retained by Clerk according to their policies.

Your browser may cache training data locally for offline access via service worker. You can clear this data anytime in your browser's site settings.

5. Your privacy choices

You can request to export, correct, or delete your training records and account data. Depending on where you live, you may have additional rights (see section 6 below). Contact us using the information in section 9, and we will respond as promptly as we can.

6. Regional privacy rights and notices

We process your data based on legitimate interests to operate and secure the app, including technical processing by our application and database host (Railway) and DNS provider (Cloudflare). We do not use data for marketing or profiling, and we do not sell or share personal information for cross-context behavioral advertising.

The following rights and protections may apply depending on where you live:

  • Access, correction, and deletion: You may request copies of your data, ask us to correct inaccurate information, or request deletion in certain circumstances
  • Portability and withdrawal: You may request your data in a portable format or withdraw consent where processing is based on consent
  • Objection and restriction: You may object to certain processing or request that we restrict how we use your data
  • Complaint: You may lodge a complaint with your local data protection authority

Data controller: Not specified — contact support

Rights and verification requirements vary by jurisdiction. Contact us using section 9 and we will handle your request under the law that applies to your region.

7. Children's privacy

We do not knowingly collect personal data from children under 13. The app is designed for fitness logging by teens and adults. If we learn we have collected data from a child under 13, we will delete it promptly.

8. Updates to this policy

We may update this policy when our practices or the app changes. When we do, we will adjust the date at the top. If a change is material, we will take reasonable steps to make it visible.

9. Contact

Questions or requests about this policy or your privacy rights: reach out through the contact path we provide in the app or on this site. We aim to respond within a reasonable time and in line with applicable legal timelines for your jurisdiction.

Effective date: April 14, 2026 · Last updated: April 17, 2026