Data & Privacy

Step-by-Step Data Flow

How workout information moves securely between Strava, your browser, and Fuel.

Step 1

Strava OAuth

Sign in securely with Strava. Tokens are stored server-side, while your browser receives only a signed httpOnly session cookie.

Step 2

Live API Fetch

Recent activities are fetched live from Strava to display in your browser. Activity history is not stored in Fuel unless you explicitly publish a share.

Step 3

Nutrition Calculation

Selecting foods calculates total carbs, fluids, and sodium in real-time. The reusable fuel catalog and your favorites are stored in Fuel; activity selections remain part of the save flow.

Step 4

Strava Sync

The nutrition summary is sent back to your Strava activity, according to your privacy choice.

Private Note Sync

Keeps all data entirely between you and Strava.

The fuel summary is written to your activity's private_note on Strava.

⚡️ 120g carbs · 750ml fluid · 600mg sodium

No activity snapshot is saved in Fuel's database. Only you see this note on Strava.

Public Description Sync

Publishes a clean, read-only fueling breakdown.

Writes the summary line + short URL to your Strava activity description:

⚡️ 120g carbs · 750ml fluid · getfuel.cc/aB3xD9z1

Saves a read-only snapshot accessible only via an unguessable 8-character link.