Settings and exports

Connect your own Strava account, keep tokens server-side, and export summarized activity data manually.

Private Strava data loaded

Displaying activities for the authenticated token owner only.

Manual export tools

Exports are scoped to summarized personal activity data for your own review.

Strava connection

OAuth is used only to connect the single owner of this private dashboard.

OAuth configReady

ConnectionOAuth connected

Granted scopes

activity:read_all profile:read_all read

Access token expires

10/8/2026, 10:16:49 AM

Token storage

netlify-blobs encrypted

Add STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET, and STRAVA_REDIRECT_URI to .env.development.local, then restart the dev server.

OAuth tokens are stored locally at .data/strava-oauth.json, or encrypted in Netlify Blobs in production. Refresh happens automatically on the server.

Reconnect Strava

Compliance guardrails

Built for a single private athlete view.

OAuth is scoped to one authenticated Strava user only.
No social feeds, leaderboards, clubs, segments, competitions, or races.
No other athletes or public comparison data is requested or displayed.
No Strava API data is sent to an AI model automatically.

Server-side only

Strava calls stay inside server components and utilities.

Client components receive summarized activity objects for display and manual export. The access token is never passed to the browser.