When reviewing old logs, change the settings you need to change and record what you verified. One change to a privacy setting doesn’t complete the review of every old record. Drawing on YAMAP and Strava’s official guidance about what each setting applies to, the editorial team suggests keeping a review table. We haven’t tested the process on live accounts.
List older logs and decide what to check
Start with a row for each log’s date, title and a link or number that lets you identify it. Include the date to distinguish multiple hikes on the same mountain. You can keep the table private and keep your account details to yourself.
Give each row fields for current audience, restricted-audience list, photos and text, track, copies you posted elsewhere, next action, date checked and open questions. Leave rows for logs you haven’t started reviewing. You can fill in the details as you go. This is an editorial suggestion, not an official feature or a method proven to catch every issue.
Flag logs you want to review first, such as those with a start or finish near home or work or photos that show someone’s name or where they spend time. Write down how many you intend to review, such as the ten most recent logs. If you stop, note which row to open next. Mark the whole list complete only after reviewing everything in scope.
Review logs, photos and shared lists separately
YAMAP explains how to make an activity log public or private in the editor. Public logs are available on the internet and appear in followers’ feeds. In the table, record the old audience, the new one you chose and the setting shown on your screen after saving.
Restricted-audience lists limit viewing to selected YAMAP users. Changing who’s on a list affects all logs that use it. Before adding someone, check which old logs are assigned to that list. Use separate fields for changes to a single log and changes to a list used by several logs.
For example, if you add someone to a list for hiking companions, check earlier logs assigned to that list as well as today’s. This is a way to apply the documented behavior. It doesn’t establish that the person actually viewed anything.
YAMAP’s help explains how to make a photo private or hide where it was taken. Review the log’s audience, the photo itself and its location separately. Hiding a photo’s location doesn’t establish that you removed a sign from the image, an address from the text or location data from the image file.
YAMAP also says the total number of summits reached and earned badges stay public when you make a log private. Record the actual scope of what you changed, including whether you checked the profile.
Find out what a bulk change actually covers
Check what a bulk option affects, even if you have many logs to review. YAMAP’s average pace help shows how to change the visibility of average pace for each log and apply that change to all activity logs in account settings. The guide applies to average pace.
A bulk change to average pace doesn’t tell you whether the log, track or photos changed audience. The sources reviewed for this article don’t establish whether there’s a bulk control for whole logs. Check the latest official guidance as needed and keep individual logs on your list while that’s unclear.
Strava says its default setting to hide the map near a specified address applies to past and future activities, except those whose map visibility you edited individually. The default options to hide all starts and ends or the whole map apply to future uploads. Individual map settings override defaults.
For old Strava logs, record the date and whether you changed a default or edited the activity itself. Strava also explains that map visibility is separate from the activity audience and doesn’t carry over to other services. These settings belong to Strava.
Record what you changed and what you haven’t confirmed
Record the actual step you completed, such as “not started,” “saved the setting,” “verified on my own screen” or “open question.” A label like “checked” leaves it unclear what you confirmed and for whom. If you haven’t seen what a recipient can see, leave that part unverified.
You can check settings without making a private log public temporarily, sending a private photo or link as a test, or using a family member’s sign-in details. If you’re unsure content is safe to share, hold off and check the settings guide or ask official support.
If you remember posting photos, text or screenshots on a social network or blog, add the destination and any changes in a separate field. Editing the original log doesn’t change those posts. Japan’s Personal Information Protection Commission says online images are extremely difficult to remove completely.
If you update or delete one of your own posts, note where and when you made the change. Copies saved by others or search results can persist. Mark outside copies as unverified if you don’t know whether they remain, and track any follow-up separately.
Count the logs you reviewed and record what remains
After one pass, count how many logs you meant to review, how many settings you saved and how many logs have open questions. Keep separate notes on each log’s audience, where lists apply, photos and tracks, and other places you shared them. That makes it easier to resume.
Describe what you finished precisely, such as “Checked the saved settings for ten logs on my own screen.” Keep that scope clear if you haven’t checked every viewer’s experience or outside copies. When you next change a list or repost a log, review which older records might be affected.
References and sources
- YAMAP · Making activity logs public or private and what stays visible
- YAMAP · Restricted-audience lists and which logs they affect
- YAMAP · Photo visibility and hiding where a photo was taken
- Strava · Map visibility defaults, individual settings and past activities
- Japan Personal Information Protection Commission · The difficulty of removing images online
- YAMAP · What the bulk average pace visibility setting applies to