You decide to stop using a running-analysis app. You revoke its Strava connection, yet old workouts remain in a spreadsheet made earlier. At first, it can seem revocation failed. But stopping new access and handling copies already created are separate processes.
This distinction does not mean providers may freely keep everything indefinitely. Strava’s current API policy also requires deletion after access is revoked. Invalidating a technical permission is not a remote delete button that removes files from your laptop and every earlier attachment, however. Our examples cover disconnection, finding provider confirmation and separately reviewing your own copies.
Ending a connection closes a future data path
The RFC 7009 specification on OAuth token revocation describes invalidating previously issued access or refresh tokens. These technical credentials support authorised system requests. Revocation aims to make previously granted access unusable; it does not manage every user file system or recipient mailbox.
In our fictional example, a running app previously read your new activities. After disconnection, it can no longer use that authorised path. An earlier monthly report may still exist elsewhere. Technical access and a stored report are separate objects. Check each in its own place to complete closure.
State the goal at the outset. Do you want only to stop new automatic transfer, close the external account too, or also verify deletion of earlier imported data? These may be related but not controlled by the same button. A precise aim prevents treating one successful step as completion of everything.
What does Strava’s technical description say?
The Strava OAuth documentation says revoked credentials cannot be used for further authorised requests. It also describes a new recommended revoke procedure for developers from 1 June 2026, becoming the only supported route on 1 June 2027. Users need not copy tokens or run developer commands. Use official app-connection controls and the integration’s supported disconnection process.
An app asking for authorisation again when next opened may be consistent with the old connection ending. Do not automatically approve it merely because the window is familiar. If you deliberately disconnected, another request is a new decision. Your current purpose should replace the old automatic routine.
An old graph remaining on screen does not prove new API access by itself. It may be locally retained display, an earlier download or a provider copy still needing handling. Examine freshness, connection state and the provider’s documented process separately. Old content remaining and a new authorised request are different observations.
Provider deletion also has explicit requirements
The Strava API Policy effective from 1 June 2026 requires developers to delete data following user requests and revocation of app access. Section 7.4 addresses prompt deletion of applicable data with a general upper limit of thirty days and retention exceptions defined in the document. This is a provider requirement, rather than proof that every copy in every system disappears at the click.
The policy also addresses deletion information and confirmation for users. Ask what a provider confirms: disconnection, receipt of a deletion request or completed deletion? These are different states. “Request received” does not mean the requested action finished. Precise wording helps track the process.
This need not become a personalised legal conclusion. Data circumstances and service terms can be specific. For a user check, find the provider’s deletion process and appropriate confirmation alongside technical disconnection. Separating access revocation from fulfilment avoids both overpromising and falsely assuming unlimited retention.
Enlarge imageA file downloaded to your computer has a separate life
The Strava export information permits downloading activity files and a personal data archive. A downloaded copy exists on your storage, rather than as part of an API token. An earlier FIT, GPX or CSV remains readable independently of whether an app has an active connection. Physical file contents and system permission are separate things.
In our example, you exported a run in May and made a spreadsheet. In November, you disconnect the app. The May file on your laptop is not remotely deleted or automatically made unreadable. Remove your own copy separately if wanted. If retaining it as a personal archive, continue protecting it.
The same applies to an emailed attachment or an earlier screenshot. Revoking access does not automatically recall a sent file from every recipient. This reflects the different nature of file sharing rather than failed revocation. Copies therefore need consideration both when connecting and disconnecting.
Uninstalling an app may not close the whole connection
The icon disappears when an app is removed from a phone, but the external account and server-side data path may exist in another system. Closure on uninstall depends on the implementation. An absent icon does not reliably establish revoked permission. Check actual connection status in the relevant account.
In our example, the phone app only displays information while an online service performs regular synchronisation. Replacing a phone need not end the previous connection’s purpose. Another app offers a separate disconnect button. Product documentation explains each action. Leaving an interface and closing a data path are not interchangeable.
Logging out can serve another role too. It may hide an account view on one device without terminating every integration created earlier. You need not assume every app works badly, but complete the process through supported settings. Seek unambiguous confirmation of what you actually want to end.
First make a short inventory of the data path
Note where information went from each service. In our simple example, the watch manufacturer’s log sends to Strava, then an external analyser reads from Strava. Disconnecting the analyser does not necessarily stop the separate watch-to-Strava connection. The arrows have different permissions and roles. An inventory prevents leaving too many or too few paths active.
File-based transfers can join the inventory: your laptop, an export sent to a coach or another cloud folder. These cannot be revoked in the same way as API access. A simple list shows where to disconnect, verify deletion or handle a local copy. You need not map every technical internal process.
Only known paths should appear as established facts. If unsure whether the service stored information on a server, mark that as a question. The user interface cannot prove background retention. Documentation or a provider response may clarify. Marked uncertainty is more accurate than an invented inventory that merely looks complete.
What should you check after disconnection?
Check that you disconnected the right app in the right account. Similar service names or multiple accounts can be confused. Retain the closure date and confirmation if later needed. The aim is a record of which connection ended when, rather than collecting secret technical information.
Then find the service’s deletion instructions and check request status. If only receipt is confirmed, completion still needs separate follow-up. If retention is stated, ask through the appropriate channel about its stated basis and extent. A targeted question is more useful than assuming revocation certainly did nothing or everything.
Organise your own archive separately. Decide which original to retain, which working copy is unnecessary and which copies were previously shared. Do not randomly delete every matching filename when the only copy of important personal training history may be among them. Disconnection and organising backups can be coordinated but remain separate decisions.
Enlarge imageWhen authorising again, read today’s screen
If you return to an app later, read the permissions requested now. Functions, access scopes and data handling may have changed. A good previous experience matters but does not override the new request. A new connection is another decision, even with a familiar name and icon.
In our example, a tool previously summarised only public recordings but now requests private activities too. That may be justified for a new feature, but accept the change consciously. Ask whether you need the feature and which data scope supports it. Reauthorisation should not blindly restore an old habit.
Earlier data may also fail to appear immediately or in the same form. Reconnecting does not guarantee complete historical backfill in every service. Check the product’s specific synchronisation rules. Do not automatically grant the broadest scope for an empty view; first identify which data and period are missing.
Make the three closure outcomes clear
First is revoked access: the app no longer uses its earlier authorised path. Second is provider data handling, with applicable deletion and confirmation. Third is reviewing personal and previously shared files. These do not always happen together, and the same technical button cannot remotely control the third completely.
A short closure note can therefore show three states: access revoked; provider deletion confirmed or still in progress; own copies reviewed. Do not claim completion you have not checked. A pending item can be marked precisely. The next step then becomes concrete rather than general uncertainty.
Revoking a running app’s connection is an important, clearly defined action. Closing the full path also requires provider deletion fulfilment and separate copies to be handled in their own places. Current Strava rules do not permit unlimited retention, while token revocation does not promise instant physical deletion of every file. Understanding the distinctions makes disconnection traceable and checkable.
Sources
- Strava OAuth: revocation and the 2026–2027 technical transition.
- RFC 7009: the role of OAuth token revocation.
- Strava API Policy 2026: deletion requirements, sections 2.5 and 7.4.
- Strava: exporting personal activity files and data archives.
How Futószív articles are prepared: our editorial guidelines.


