Training data should make fueling clearer, not less private.

Fueleur stores the data needed to connect training context, generate fueling guidance, confirm what happened after a session, and keep recommendations useful over time. This page explains the main data categories in the MVP and how they are used.

Nutrition guidance disclaimer

Fueleur provides training nutrition guidance for endurance athletes. It is not medical advice, diagnosis, treatment, or a replacement for care from a physician, registered dietitian, or other qualified professional.

Users with medical conditions, eating disorders, pregnancy, heat illness risk, sodium restrictions, diabetes, kidney disease, medication interactions, or other high-stakes health considerations should consult a qualified professional before changing fueling, hydration, sodium, caffeine, or supplement practices.

What Fueleur stores

Account and profile data

Fueleur stores your account email and athlete profile details such as display name, bodyweight, timezone, diet preference, goal context, caffeine preference, GI sensitivity, sweat rate, and sweat sodium values when you provide them.

Used for personalization, unit context, reminders, and fueling calculations.

Strava connection data

When you connect Strava, Fueleur stores provider account identifiers plus access and refresh tokens so the app can request activity data for your account.

Tokens are server-side connection credentials. They should never be exposed in browser UI, logs, support screenshots, or client-side code.

Workout and activity data

Fueleur stores planned manual workouts, reusable workout templates, imported completed activities, activity pairing state, sport type, start time, duration, distance, elevation, intensity, and provider payload details when available.

Used to build upcoming fuel plans, show Activities history, pair manual plans to completed activities, and calculate training demand.

Fueling entries and Fuel Score data

Fueleur stores confirmed intake values such as calories consumed, carbs, sodium, fluid, confirmation time, and whether fuel was intentionally skipped.

Used to compare actual fueling against Fueleur recommendations and calculate per-activity and 30-day Fuel Score results.

Product, cart, and notification data

Fueleur stores product catalog references, inventory assumptions, generated cart data, reminder settings, notifications, read state, and related action links.

Used for replenishment planning, reminder behavior, and clearing notifications after user actions.

Security practices for the MVP

Connection tokens are intended to be stored and used only on the server.
Production deployments should use HTTPS and secure, HTTP-only session cookies.
Environment variables should be used for provider secrets and database credentials.
Users should not share screenshots containing tokens, raw provider payloads, or private account details.
Access to production databases, logs, and provider dashboards should be limited to trusted operators.
Provider connections should be revoked through the provider account if a user no longer wants Fueleur to access that data.

Current MVP limitations

Fueleur is an MVP and does not yet include full self-serve export, retention, or account deletion controls.
Background sync behavior is intentionally conservative to respect provider API limits.
Some provider data may be incomplete or delayed depending on the connection and activity payload.
Fuel Score depends on confirmed user intake. If intake is not confirmed, the activity remains pending.

For support or data questions, include the page you were using and what action you took. Do not send access tokens, raw credentials, or private provider secrets.

hello@fueleur.com