Skip to content

Commit 0d423e0

Browse files
ckdakeckdake
committed
Updates site
1 parent 803bc81 commit 0d423e0

1 file changed

Lines changed: 112 additions & 11 deletions

File tree

‎site/src/faq.html‎

Lines changed: 112 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -314,6 +314,14 @@ <h1>Frequently Asked Questions</h1>
314314
that provider remain in your TraceKit account —
315315
unlinking does not delete historical data.
316316
</p>
317+
<p>
318+
<strong>Strava is an exception:</strong> when
319+
you unlink Strava, all Strava activity data is
320+
immediately and permanently deleted from
321+
TraceKit. This is required by Strava's API
322+
terms. Export anything you need before
323+
unlinking.
324+
</p>
317325
<p>
318326
To fully revoke TraceKit's access, also remove
319327
it from the provider's own connected-apps
@@ -329,17 +337,110 @@ <h1>Frequently Asked Questions</h1>
329337
</summary>
330338
<div class="faq-a">
331339
<div class="provider-note warning">
332-
<strong>Strava</strong>
333-
Strava's API does not allow downloading the
334-
original source files (GPX, FIT, or TCX) for
335-
activities. Activity metadata — name, type,
336-
distance, duration, and so on — syncs normally,
337-
but the raw files are not available through the
338-
API. If Strava is your only provider and you
339-
want source files in TraceKit, export your full
340-
Strava data archive from Strava's settings page
341-
and contact us to have it imported via the Files
342-
provider.
340+
<strong>Strava — important restrictions</strong>
341+
<p>
342+
Strava's API terms place specific
343+
requirements on how TraceKit may use your
344+
Strava data. Please read these carefully:
345+
</p>
346+
<ul>
347+
<li>
348+
<strong
349+
>Strava is always a write target,
350+
never a source.</strong
351+
>
352+
TraceKit treats Strava as a destination
353+
only. For example, if you set an
354+
activity name in Garmin, TraceKit can
355+
push that name to Strava — but it will
356+
never go the other direction and push a
357+
Strava name to Garmin or another
358+
provider. Your other providers are
359+
always authoritative.
360+
</li>
361+
<li>
362+
<strong
363+
>Out-of-sync detection and
364+
updates.</strong
365+
>
366+
When TraceKit notices that Strava is out
367+
of sync with your authoritative data
368+
(e.g. a name or gear assignment
369+
differs), it will surface the
370+
discrepancy and offer to update Strava
371+
for you. Nothing is written until you
372+
explicitly approve.
373+
</li>
374+
<li>
375+
<strong
376+
>Creating activities in
377+
Strava.</strong
378+
>
379+
If you record an activity somewhere else
380+
(Garmin, RideWithGPS, etc.), TraceKit
381+
can create a matching activity in Strava
382+
on your behalf. Activities you
383+
originally created in Strava are never
384+
pushed outward to other providers.
385+
</li>
386+
<li>
387+
<strong
388+
>No source files from
389+
Strava.</strong
390+
>
391+
Strava's API does not permit downloading
392+
original source files (GPX, FIT, TCX)
393+
for activities. Raw files are not
394+
available through the API regardless of
395+
how the activity was recorded.
396+
</li>
397+
<li>
398+
<strong
399+
>Initial backfill via
400+
export.</strong
401+
>
402+
You can export your data archive from
403+
Strava's settings page and import the
404+
individual activity files (FIT, GPX,
405+
etc.) into TraceKit via the Files
406+
provider. Those files are treated
407+
identically to files uploaded from any
408+
other source — no Strava restrictions
409+
apply to them. Note that this only
410+
covers the files themselves; any sync
411+
suggestions or updates back to Strava
412+
still require a live Strava connection,
413+
and all of the restrictions above apply.
414+
</li>
415+
<li>
416+
<strong
417+
>Data freshness — 7-day
418+
window.</strong
419+
>
420+
Strava data must have been retrieved
421+
within the last 7 days to be used for
422+
activity matching. If you update an
423+
activity's name or gear after the 7-day
424+
window has passed, TraceKit will still
425+
offer to push the change to Strava, but
426+
it will not be able to confirm whether
427+
Strava already has that value until you
428+
press the "Accept" button and the update
429+
is applied.
430+
</li>
431+
<li>
432+
<strong
433+
>Unlinking deletes all Strava
434+
data.</strong
435+
>
436+
When you unlink Strava, every piece of
437+
Strava activity data stored in TraceKit
438+
is immediately and permanently deleted.
439+
This is a hard requirement of Strava's
440+
API terms. Export anything you need
441+
before unlinking.
442+
</li>
443+
</ul>
343444
</div>
344445
<div class="provider-note warning">
345446
<strong>Garmin</strong>

0 commit comments

Comments
 (0)