A new running app promises an instant training overview when you connect your Strava account. Its button simply says sign in or connect with Strava. The next screen, however, lists data permissions. You are deciding not only how to identify yourself to the new service, but also what access it receives to your training history.
You do not need to be a programmer to make a sound decision. Distinguish reading from writing, basic data from full activity access, and requested permissions from those actually accepted. Our running-app situations show when a permission may be justified and what questions clarify its need. The aim is a useful, considered connection whose data path you still understand later.
A connection button involves an access decision
The OAuth 2.0 foundational specification describes a framework for granting a third party limited access. A service requests permission to data held in another system, and the user may authorise it. This differs from manually saving every item to a file and handing it over. A connection can operate through defined system requests while authorisation remains valid.
In our example, a fictional analysis app produces monthly summaries from earlier runs. Strava holds the recordings, the analyser is the external service requesting access, and you decide what to allow. Keep both applications’ names and roles clear. Approving a connection on a familiar platform’s authorisation screen does not stop the new app being a separate provider with a separate data path.
The everyday label “sign in” is therefore incomplete. A button may simplify login while also requesting data functions. The next screen matters more than the button’s brief marketing name. Check which app receives permission for which action. One-click convenience does not reduce the substance of the decision.
Reading, writing and broader access are separate permissions
The official Strava authentication documentation lists separate access scopes. activity:read permits reading activities visible to everyone or followers, excluding hidden-zone data. activity:read_all can access owner-only activities and zone data too. activity:write can permit creation and editing of activities visible to the app.
When we checked, official sources differed on hidden map sections: the developer list above and Privacy Controls FAQ describe exclusion under narrower reading, while the App Authorization Settings page dated 18 September 2026 mentions access to hidden map portions even under standard activity reading. We do not resolve that documentation discrepancy by assumption. Do not treat a permission labelled narrower as a guarantee that sensitive location data remain inaccessible: clarify the specific request and integration with the provider, using a personal trial containing no sensitive place if necessary. Technical scope and the actual product path matter together.
In a decision about a read-only graph app, ask why creating or editing activities would be needed. There may be a documented functional reason, such as a separate upload option, but the app should explain it clearly. A permission is appropriate when connected to the chosen function, rather than because it sounds small. An unknown purpose remains a question to clarify.
A private activity is not the same as data closed to apps
The social view and authorised API access are separate layers. A run visible only to you on Strava may still be accessible to an appropriately authorised external app within its documented scope. Consider that when interpreting broader activity-reading permission. A private label does not automatically prohibit every other system when you separately grant access.
In our example, a runner keeps workouts near work out of the social view. They nevertheless want a fictional annual analyser to examine all their runs, so reading private recordings may be justified. That is consistent when deliberate. Requesting the same broad access without explanation for one small feature concerning a public race result is a different situation.
The Strava map-visibility description also emphasises that masking rules do not automatically transfer to other services. A map or export made by an external app therefore needs its own check. Successful masking in the public view and detailed access granted to an app are separate decisions. Both can help, but neither replaces the other.
Enlarge imageRequested and accepted permission lists may differ
Strava’s developer description says users may omit requested scopes, so the returned list of accepted scopes can differ from the original request. The app must handle that actual outcome. A missing function may therefore result from withholding the data it needs. It is not necessarily a network or watch-synchronisation fault.
In our example, the analyser would summarise both public and private activities annually, but you approve only narrower access. Its display therefore does not contain your entire training year. First reconcile the permission with the desired function, rather than declaring the data faulty. If you do not want broader access, choose a view or workflow that remains meaningful with narrower data.
The app should clearly indicate when a refused permission prevents a function. As a user, do not authorise everything at random because a graph is empty. First establish which information is missing and why it is needed. Extending access may be appropriate, but should follow a specific understood function rather than a general troubleshooting reflex.
Define the necessary minimum around the task
The RFC 9700 OAuth security best current practice recommends restricting access to resources and operations necessary for the specific application purpose. For a runner, this becomes a straightforward question: which data and actions are needed for what I want to use now? The aim is the narrowest functioning scope. More permissions accompanying more features are not a default advantage.
Our three functions have different needs. A view summarising existing recordings may need reading. A feature uploading a newly entered workout may require creation rights. A profile-editing tool may request another operation. These are not recommendations for particular apps; they show how permission can be tied to the task actually wanted.
Separate functions used now from those you might try later. If an app requests a broad package for a rarely used extra, ask whether a narrower route exists. The product may not support that choice. Then decide whether to accept its package for the useful function or choose another solution. An explicit compromise is better than a hidden assumption.
Proper authorisation is not handing a password to an unknown form
One role of OAuth is letting an external app use user-approved access rather than receiving the whole account password. RFC 9700 treats the old grant based on directly handing over a user’s password as a flow that must not be used. For a user, the important point is that an access decision differs from a login secret. Permission for a running app does not justify providing your account password on an unknown interface.
In our example, an app promises a connection, then sends you to an arbitrary page requesting a password in Strava’s name. First clarify the origin of the official login and authorisation route. A familiar logo or orange button alone does not authenticate a page. Decide from the actual service opened and request made, rather than the graphics’ familiarity.
A safer protocol does not automatically make every app trustworthy. A genuine authorisation request can be too broad for your purpose, and an approved provider’s data practices still matter. Check both whether you are authorising the right system and whether the permission’s contents are appropriate. A good answer to one does not automatically resolve the other.
After reading permission, the subsequent data path matters
Permission to read does not explain everything about retention, how summaries are produced or how a copy can later be removed. Look for those details in the service’s own documentation. A scope describes a technical capability; data-handling practice is another question. Even a simple graph can involve server-side storage, so the visible screen does not establish a complete retention policy.
In our example, one tool processes a file locally while another is a continuously connected online log. Convenience and data paths may differ. Neither is necessarily better in every situation; purpose and implementation matter. Know where data go, who can access them and how you will use the result later.
The official Strava Privacy Controls FAQ specifically discusses permissions granted to external apps. After learning the provider’s name and requested scope, review your own sharing needs too. An automatic connection can save time, but a long-running data path also needs periodic review. Initial consent should not become a forgotten default.
Enlarge imageThree short decision examples
The first fictional app graphs monthly kilometres from already public runs. Reading is the necessary action; if it requests writing too, you seek a separate reason. The second private training log analyses all your runs. Private-activity reading may fit that chosen function, but location data and retention remain part of the decision. Understanding the function helps assess proportionality.
The third app posts a new workout to your account. Writing permission is then readily understandable, but you should also know the created data’s source and which activities the programme can change. A specific trial after successful upload can check the result. Alongside convenient automation, content and data-source transparency remain important.
For all three, the same sentences help: this is my function; these data and actions are needed; this is the access I accepted. If any sentence cannot be completed clearly, the basis for deciding is incomplete. No secret-token inspection or developer requests are required. The user-facing authorisation request and understandable service documentation should provide the necessary information.
After connection, keep track of what you authorised
Note which app you connected and why, and occasionally check whether you still use it. A changed function and new permission request mean a new decision. A good past experience does not automatically justify a new data scope. Nor need every update be suspicious: understand the actual change and compare it with your use.
If you disconnect, stopping new access differs from handling copies already created. Authorisation does not describe the physical lifetime of every data copy. Check the service’s own deletion and retention information separately. Asking this before connecting also helps show how deliberately the whole path can be managed.
Sign in with Strava can therefore begin a convenient, useful connection. The important decision concerns the next screen’s permissions: reading, writing, private data and access actually accepted. Relating them to the wanted function makes the connection understandable and manageable later. The aim is to follow your running data’s path, rather than reject every connection.
Sources
- Strava OAuth: access scopes and the accepted scope list.
- RFC 6749: foundations of the OAuth 2.0 authorisation framework.
- RFC 9700: minimum privilege and avoiding direct password transfer.
- Strava Map Visibility: differences between the social map and other services.
- Strava Privacy Controls FAQ: third-party app permissions.
- Strava App Authorization Settings, 18 September 2026: differing map-access description.
How Futószív articles are prepared: our editorial guidelines.


