Fitport Privacy Policy

Effective Date: April 2026 Last Updated: April 2026

Overview

Fitport is a Chrome Extension that exports fitness data from Peloton and MyFitnessPal. All data processing happens entirely within your browser. No fitness data is ever transmitted to external servers.

Data Collection

What Fitport Accesses

What Fitport Does NOT Collect

Data Processing

All data processing occurs 100% client-side within the Chrome extension:

  1. Data is read from the platform (Peloton API or MFP page DOM)
  2. Data is normalized into a unified format within the extension
  3. Data is formatted (Markdown-KV, JSON, YAML, or CSV) in-browser
  4. The formatted output is provided to you via clipboard copy or file download

At no point does your fitness data leave your browser.

Data Storage

Fitport uses minimal Chrome extension storage:

No fitness data is persisted in any storage. Exported data exists only in memory during the export process.

Third-Party Services

Fitport itself runs no servers. The only third-party service the extension contacts beyond the source platforms is Lemon Squeezy, which handles payments and license-key validation for the optional Pro tier:

For details on how Lemon Squeezy handles checkout and customer data, see https://www.lemonsqueezy.com/privacy.

Chrome Extension Permissions

Fitport requests the following permissions, each for a specific purpose:

Permission Purpose
sidePanel Renders the Fitport UI as a Chrome side panel
activeTab Detects which platform (Peloton/MFP) is open in the active tab
storage Stores the Pro license activation record (license key, instance ID, status, expiration)
cookies Checks Peloton login status via session cookie
alarms Keeps the service worker alive during long exports
scripting Injects content scripts to extract MFP nutrition data from page DOM

Host Permissions

GDPR and Data Portability

Fitport is a data portability tool aligned with GDPR Article 20 (Right to Data Portability). It enables users to export their own fitness data in structured, commonly used, and machine-readable formats. Since all processing is client-side, no data controller obligations apply to the extension itself.

Changes to This Policy

We will update this privacy policy if our data practices change. The "Last Updated" date at the top reflects the most recent revision.

Contact

For questions about this privacy policy or Fitport's data practices, please contact:

Email: support@quiicks1lver.dev GitHub: https://github.com/QuiickS1lver/fitport