What changing a default does — and doesn’t do
AllTrails settings are organized by content category, and changing a default normally affects new items rather than the ones you already posted. That is why an owner who switched a default can still find older activities, maps or lists visible to the previous audience.
AllTrails offers Public, Followers only and Only me settings by content category; changing defaults normally affects new items. Source
So the default change is the first half of the job. The second half is deciding whether the older items should match it, and if so, applying the change to them deliberately rather than assuming it already happened.
Decide the audience you want for each category
Before touching the retroactive option, write down the intended audience for each category you use. This is a checklist for you, not a record of any test we ran.
| Category you are reviewing | Question to answer first |
|---|---|
| Activities | Should older routes be Public, Followers only or Only me? |
| Maps | Is this map for anyone, your followers, or only you? |
| Lists | Does the list reveal places or plans you would rather keep restricted? |
The three audience settings mean different things:
- Public — the item can be seen beyond your followers.
- Followers only — visibility is limited to people who follow you.
- Only me — the item is restricted to you.
Treat these as content-visibility settings, not as a full identity switch. A restricted item does not make your whole presence on the platform invisible.
Keep profile details separate from content settings
Profile photo, name, location and high-level statistics are not the same as the content you post, and they may stay visible even when your content is set to Only me.
Profile photo, name, location and high-level statistics may remain visible even when content is Only me. Source
Practical implication: if your concern is what your profile reveals about you, changing activity or map audiences will not address it. Review the profile fields as a separate decision, and do not assume that restricting content also hides your name, photo, location or aggregate statistics.
Apply the change to existing content on the website
The retroactive control is described as part of the website’s Privacy settings, not as something established for the mobile apps. If you cannot find it in the app, use the website rather than guessing at a menu path.
AllTrails’ website Privacy settings includes Apply to past content; saving with it selected applies the chosen defaults retroactively to existing content. Source
A reasonable sequence, based on the reviewed claims:
- Open the Privacy settings on the AllTrails website.
- Set the desired audience for each content category you care about.
- Select Apply to past content before saving.
- Save the settings.
- Open a few representative existing items — an older activity, a map, a list — and confirm each shows the audience you intended.
- Repeat for any category you have not yet checked.
Step 5 matters because the setting is applied by category, and your older items may not be evenly distributed across categories. Checking one old activity does not tell you what happened to your maps.
What this does not do
- It does not remove copies outside AllTrails. If someone saved a shared screenshot or an external copy of an activity or map, changing the audience setting does not reach that copy. Do not treat the setting as a recall mechanism.
- It does not make your account completely hidden. Profile fields and high-level statistics are handled separately, as described above.
- It is not a deletion. Applying a more restrictive audience changes who can see content; it is not the same as removing the content or the underlying data.
- It does not cover every surface automatically. The reviewed claims describe the website’s Privacy settings and category-based defaults. Details such as exact menu labels, mobile parity and how every content type behaves are not established here; verify in your own account rather than relying on an assumed path.
If an item still shows the old audience after saving with Apply to past content selected, re-check that you saved after selecting the option, that the item belongs to the category you changed, and whether the item was created after the default change. If the discrepancy persists, the honest next step is to inspect that specific item’s own settings or contact AllTrails support; the reviewed facts do not describe a per-item override workflow.
Where TraceSeek fits — and where it doesn’t
TraceSeek is a separate public-username lookup app. It searches publicly accessible profile candidates using a supplied username, and its documented username scan is described as taking 20–30 seconds with a free first scan. It cannot change AllTrails privacy settings, recover private accounts, or verify anyone’s identity. A public username match is a lead, not proof of ownership.
If your concern is broader than one platform — for example, which accounts across the web are associated with a name you use — that is a different task from applying AllTrails defaults. You can review the related account task to see how that question is framed.