Trackables are the individual items that carry public codes, secret access, route history, optional images, and optional verified outside links.
That split is why Geotrackable keeps public-code pages, secret-code access, activation, map logging, images, and support reporting as related but separate workflows.
The public code is the safe share code for the public page. The secret code or private QR is the private control path that unlocks remembered browser access and protected workflow steps.
Secret codes and private QR values are intentionally shown only on the creation reveal page, so creators should save, print, or label them before leaving that screen.
A trackable can stay under one person or be activated to a team. Group-created items can begin with shared default title, description, status-message, and link values until item-level edits take over.
Public pages can show a route map, journey stops, public-safe images, and a verified external link without exposing the private controls used to move the item.
A public trackable page can show the public code, title, story, route map, logged stops, owner or team label when that information is meant to be public, uploaded images that are visible to the page, and one verified external link when the owner has added one.
Public links can open through a Geotrackable-owned exit page first so the visitor can review the destination before leaving the site. Report buttons and support paths exist for public pages, images, and suspicious links.
Secret codes, private QR values, remembered-access tokens, one-time creation reveal details, and private workflow controls are not copied onto the public page.
That is why the public code is the safe code to print or share widely, while the secret code should stay with the person physically handling the item or managing the private workflow.
Use the single-item flow when one physical item needs its own title, visibility choice, image set, external link, category, and activation plan.
Create a Single TrackableUse the group flow when multiple items should start from one shared setup and then diverge later through overrides or activation.
Create a Group of TrackablesUse journey pages for owned, team, and unlocked trackables with real routes, and public pages for intentionally shared stories, public codes, public images, and public-safe links.
Trackable JourneysUse the field guide when you want the full path from creation to cache placement to finding and logging the next move.
How to Geocache GeotrackablesTrackables usually become more useful when their stops are logged as real locations instead of guesses, and when any uploaded images actually help people recognize the item or understand the story.
Images are screened before they are saved, processed into Geotrackable-managed image files, and tied to the visibility of the parent trackable or team page. Image reports should go through the public report buttons or the support page when something looks unsafe or out of date.
Trackable links are verified before saving. Geotrackable checks that the link is a valid outside address, tries to read the page title, and rejects localhost-style or private-network destinations instead of storing them.
If a link later looks broken, misleading, or unsafe, use the support page or the report path tied to that page so support can review the destination and decide whether it should be removed.
Use the public code for public browsing, use the secret code or private QR only for the person with real access to the item, and use support reporting when a page, image, or link no longer matches what should be public.
That keeps the route story readable, keeps the private controls private, and makes it easier for Geotrackable to stay accurate even when the trackable changes hands many times.
