Everything you need for a season that sticks.

Most apps ask you to translate ambition into forms. Stryvn starts with a conversation: your race, your timeline, how many days you can commit, and what has broken plans before. The coach reflects that back so you are aligned before the first week is generated.

You can refine goals as the season evolves — from “finish healthy” to “PB attempt” — without rebuilding everything from scratch.

Static PDFs cannot react. Stryvn watches completion, subjective feel (when you share it), and external load signals where available, then proposes adjustments — an extra rest day, a shifted workout, or a trimmed long run — with a short explanation.

You stay in control: accept, tweak, or ask for a second opinion in plain language.

Connect Strava once; new activities can flow into Stryvn so your coach sees duration, distance, and relative effort without manual entry. We only request what we need to reconcile training.

When displaying interoperability, we follow Strava’s API branding rules — including the required “Compatible with Strava” / “Powered by Strava” wording for plain-text references.

No wearable parade required. If a session did not sync, you can log it manually so the week still reflects reality. The coach uses that entry the same way it uses an imported activity.

That matters for treadmill work, borrowed watches, or those days the Bluetooth gremlins win.

Your training story is personal. Stryvn supports data export so you can move or archive your history, and deletion flows when you want the account gone. OAuth tokens for connected services are stored encrypted at rest.

AI processing is described in our privacy policy — including which categories go to our model provider and how long they are retained for operational needs.

• Request a structured export of your account data.
• Request deletion; we queue hard-delete within documented windows.
• Strava and other tokens use Laravel encrypted casts.