A recorded activity is not an approved territory
A Walk or Run can record a route, duration, distance and pace even when no virtual area is created. Recording answers what activity data Marchh accepted; eligibility answers whether the route can change territory on the shared map.
Keeping those outcomes separate prevents a normal activity from being treated as a failed record merely because it did not produce territory.
The route needs usable closed-area geometry
Territory begins with a route that returns around an area. The accepted points need to form geometry Marchh can evaluate, not just a line that appears close to its start at one zoom level.
Marchh does not publish an exploitable closure distance, minimum shape formula or guaranteed area threshold. A safe natural loop is a better basis than attempting to engineer an exact limit.
Location quality affects the geometry
Buildings, tunnels, tree cover, device conditions and permission interruptions can introduce gaps or jumps. If accepted samples cannot describe a reliable area, the activity may be ineligible even when the person physically returned to the start.
Enabling suitable location and Precise Location access and recording outdoors can improve conditions, but no setting promises perfect GPS or territory.
Movement and activity data must be genuine
Marchh can apply integrity rules to protect a map shared among accounts. Spoofed location, fake-location tools, automated movement, replayed data, duplicates, corrupted information or implausible activity may be rejected.
The relevant fraud tolerances, detection signals, internal weights and review methods are not disclosed here. Genuine movement recorded by the device is the expected input.
Existing territory can affect the outcome
The covered area does not exist in isolation. It may meet territory already represented on the shared map, and current ownership or overlap mechanics can cause a proposed result to be changed or rejected.
Marchh does not promise that apparently open space will remain available or that a particular overlap will resolve in one account's favor. The live product result is authoritative.
Completion cannot guarantee eligibility
Finishing correctly gives Marchh an activity to evaluate; it does not bypass geometry, location, integrity or territory rules. The service may also evolve those rules to maintain operation and fairness.
If a genuine route is not accepted, inspect the recorded shape and permissions, compare it with the closure guidance, and use the failure guide for targeted troubleshooting. Do not repeat an unsafe route simply to seek a different outcome.
How to respond to an ineligible result
Start with the evidence visible to you: whether the activity saved, whether the recorded line is continuous, whether it appears to enclose an area and whether existing territory is relevant. These observations can guide ordinary troubleshooting without reverse-engineering validation.
If the result still appears inconsistent, contact Support with non-sensitive identifying detail. Support may explain a user-facing issue without disclosing fraud rules, moderation signals or exact system thresholds.
Questions people ask
Does a closed route always create territory?
No. Closure supplies an area to evaluate, but location quality, route geometry, activity integrity, territory conflicts and other rules still determine eligibility.
Why does Marchh withhold exact eligibility thresholds?
Exact tolerances and validation signals could help someone manipulate activity data, so this public guide stays with principles useful to genuine participants.
Can a valid activity remain useful without territory?
Yes. It can still preserve the recorded route and available movement metrics even when the separate territory decision is negative.
