Secret-spot economics across niches

Part of the «Waze для рыбалки» wiki · Research stream · 2026-07-02 · Status: complete
Related: Reputation mechanics · Design principles

==== TOPIC: secret-spots ====
SUMMARY: Across surfing, hunting, foraging, climbing, birding, and fishing, location knowledge is a rival good: every domain that built a sharing platform hit the same backlash cycle (crowding, degraded resource, community revolt, sometimes vandalism or litigation), and every surviving platform converged on a small set of dampening patterns. Fishbrain is the cautionary tale — it launched without privacy controls, got branded "the spot burner app," and years later still fights that reputation despite now defaulting to waterbody-level sharing; onX/HuntStand survived by making everything private-by-default with small-circle role-based sharing; eBird/iNaturalist/BirdGuides survived via coordinate obscuring, taxon-based auto-suppression, and seasonal news delays; Strava's heatmap proved aggregation alone doesn't anonymize when user density is low. Russian and Latvian angling communities show the exact same norms as English-speaking ones (techniques are shareable, locations are not; first reaction to any app pitch is sarcastic distrust), and Latvia already has a normalized official catch-reporting rail (ManaCope) plus a Baltic precedent (Lithuania's Deeper) for depersonalized crowdsourced water data. The fisheries science confirms the fear is rational at spot level (localized depletion, fish becoming harder to catch) but not at stock level if regulations hold — which gives the app a defensible middle path: aggregate, delay, coarsen, and reward contribution without exposing pins.

KEY FACTS:
- Fishbrain launched with no location-privacy options and was community-branded 'the spot burner app'; it later added three catch-privacy tiers — Public (exact position), Competitive (waterbody name only, exact position hidden), Private (all location hidden) — with last-used tier remembered as default (fishbrain.com/blog/fishbrain/fishbrain-the-spot-burner-app; fishbrain.helpshift.com FAQ 159).
- A detailed Fishbrain App Store review documents a user who, after months of posting catches, saw his local spots hold fewer fish, was approached in person by strangers who followed his posts, and concluded he had 'knowingly burned one spot and possibly helped burn three others' (apps.apple.com Fishbrain reviews).
- Surfline's cams/reports triggered a documented localism backlash: purists accused founder Sean Collins of 'destroying surfing's mystique,' and some beach cameras were vandalized or destroyed (surfertoday.com 'The story of Surfline'; outsideonline.com 'Did Surfline Revolutionize the Sport or Kill Its Renegade Soul').
- Extreme end of rival-goods defense: the Lunada Bay Boys (Palos Verdes Estates, CA) used threats/violence to keep outsiders off 'their' break; a 2016 federal class action ended with individual settlements of $25,000–$90,000, stay-away orders, and a city settlement eight years later (theinertia.com, courthousenews.com, KTLA).
- onX Hunt: waypoints are private by default and framed as user-owned content; sharing is via folders/links with viewer-vs-contributor roles; live-location data is deleted when a session ends. Criticisms: 'erasure of secret spots' and the Waypoint 6 episode, where a waypoint was compelled into evidence in the Wyoming corner-crossing trial — private data isn't litigation-proof (outdoorlife.com 'The onX Effect'; onxmaps.com; Wikipedia onX Maps). Hunting advocate Randy Newberg's counterpoint: 'public-land secret spots are an oxymoron to begin with.'
- HuntStand's model is private circles: Group Hunt Areas with View-Only / Member / Admin permission tiers, plus club tools (stand reservations, group message board) — sharing happens inside a closed trusted group, not publicly (huntstand.zendesk.com; media.huntstand.com/promo/sharing.html).
- Mountain Project's explicit policy: routes on public land with legal access belong on the site; 'wanting to keep routes secret or uncrowded is not grounds for removing routes' — exceptions only for precarious access or artifacts. theCrag instead built a 'private, sensitive and closed crags' mechanism that hides a crag or just its access info without deleting logbook history (mountainproject.com/help; thecrag.com/en/article/sensitivecrags).
- iNaturalist geoprivacy: three tiers (open/obscured/private); 'obscured' displays only a 0.2°x0.2° cell (~400 km² at SF latitude); taxon geoprivacy AUTOMATICALLY obscures species threatened by location disclosure; true coordinates visible only to trusted users/project curators — trust-gated precision (inaturalist.org/pages/geoprivacy).
- eBird maintains a Sensitive Species list (hidden/regional-only coordinates) to prevent poaching and disturbance; UK's BirdGuides suppresses news of Schedule 1 breeding species during breeding season in coordination with RSPB, resuming reports after the season — an institutionalized time-delay/seasonal-suppression pattern (support.ebird.org; birdguides.com 'Species reported by BirdGuides').
- Strava heatmap lessons: 2018 heatmap exposed secret military bases; even with claimed multi-user aggregation thresholds and privacy zones, NC State researchers de-anonymized users' home addresses from the heatmap (confirmed via voter rolls) — aggregation fails where user density is low, which is exactly the situation on small lakes (fpf.org; conpro23.ieee-security.org childs paper; bleepingcomputer.com).
- Fishing spot-burning etiquette (Flylords, MidCurrent, Washington Fly Fishing forum): sharing techniques/tackle and state/region-level info is acceptable; naming specific streams, precise geotags, or identifiable photo backgrounds is taboo; 'Tag Responsibly, Keep Jackson Hole Wild' created a deliberately generic geotag as a pressure valve (flylordsmag.com/fishing-ethics-etiquette-spot-burning).
- Documented degradation cases: Kentucky Lake's Whopper Plopper bite 'went away almost overnight' after social-media sharing concentrated effort (northwoodsbass.com); fisheries science shows a red abalone reserve lost 65–78% of population within 3 years of exposure to fishing pressure, and pressure selects for harder-to-catch fish — but regional stocks survive spot-burning if catch regulations are followed; spot-level recovery can take ~10 years (ariellawrites.com 'The Science of Spot Burning').
- Russian angler norms mirror English ones: on rusfishing.ru, the first reply to a fishing-app pitch was 'Смешно. Скиньте мне все свои секретные точки рыбалки' ('Funny. Send me all your secret fishing spots'); the developer was pushed toward device-local spot storage; others suspected paywall motives or objected on conservation grounds (rusfishing.ru thread 582596). On fisher.spb.ru's ethics thread, the compromise norm is share techniques and tackle, never locations: 'Народ приезжает и как с цепи срывается. Никакого уважения' ('People show up and go feral. No respect').
- Latvia specifics: ManaCope (manacope.lv, run by LLKC) is the official licence-purchase + mandatory catch-report app — reports due within 5 days of licence expiry even for nil catches — so structured catch logging is already a normalized behavior; makskeresanaskarte.lv covers rules/waters; copeslietas.lv and parcopi.lv forums have active 'Copes vietas' (fishing spots) sections where the 'vietu neteikšu' (won't name the spot) norm appears; Latvian angling lore celebrates independent discovery of unknown waters (lielaisloms.eu).
- Baltic precedent: Deeper (Lithuanian company, Fish Deeper app) crowdsources user bathymetry into community depth maps but depersonalizes it (coordinates+depth only, no catches/marks), keeps shared trophy catches without exact spot disclosure, and lets private pond owners request map removal — though users still raised ownership/auto-upload concerns (fishdeeper.com; support.deeper.eu; deepersonar.com blog).
- Angler's Atlas / MyCatch (Canada) markets 'Our promise to anglers is that Secret Spots Stay Secret' — catch data goes to fisheries biologists under data-sharing agreements, a citizen-science framing that made logging acceptable (anglersatlas.com/mycatch).
- Give-to-get is a proven reciprocity gate: Glassdoor requires one contribution (review/salary/interview) for 12 months of unlimited access to community data (help.glassdoor.com 'Give-to-get policy'); mushroom-mapping apps (Mushroom Tracker, GeoForager) sell 'spots stay secret' encryption plus habitat-prediction layers (e.g., morel burn maps from wildfire perimeters) instead of spot disclosure — predict habitat, don't reveal spots (mushroomtracker.ca; salishmushrooms.com).
- Leave No Trace's geotagging guidance arc: 2018 'avoid geotagging specific locations,' softened in 2020 to 'not anti-geotagging' after critics argued location-hoarding is gatekeeping that excludes newcomers — the counter-pressure to secrecy is an access/equity argument, and it's live in hunting too (onX 'flattened the learning curve') (hcn.org; modernhiker.com).

IMPLICATIONS:
- The Waze analogy breaks at the core loop: traffic reports are anti-rival (sharing helps everyone), fish reports are rival (sharing costs the sharer). Design the public layer around non-rival data — water levels, ice conditions, access points/ramps, regulations, seasonal bans (lieguma laiki), bite-by-species-by-conditions forecasts — and treat precise 'fish are biting HERE' as the dangerous, gated exception.
- Default must be waterbody-level, not pin-level, from day one. Fishbrain's history shows privacy added later never erases the 'spot burner app' brand; launch messaging should lead with an Angler's Atlas-style promise ('secret spots stay secret'). Expect the first comment in every LV/RU forum thread to be the rusfishing sarcasm ('sure, send me your secret spots') and pre-empt it.
- Gamification and reputation must be decoupled from location precision: score verified catches, species diversity, streaks, technique write-ups, and report helpfulness at waterbody granularity. Never award extra points for exact coordinates — that monetizes spot-burning. The RU-forum compromise norm (techniques shareable, locations not) tells you what content the reputation system should amplify.
- Copy the three-tier catch privacy (public / waterbody-only / private) with waterbody-only as default and sticky last-choice, plus onX-style private-by-default personal pins and HuntStand-style small circles (roles: viewer/contributor/admin). Private circles are likely the highest-retention sharing feature — Latvian angling has strong club and licensed-water structures to map onto.
- Public aggregate views should be heatmaps with k-anonymity thresholds and time delay, never live pins: minimum N reporters per waterbody/time-window before anything renders (Strava's lesson — small Latvian lakes have low user density, so naive aggregation deanonymizes), coarse cells (iNaturalist's 0.2° obscuring, scaled down to lake-sized cells), and publication delayed hours-to-days so the 'bite window' expires before the crowd arrives (BirdGuides' seasonal suppression is the institutional template).
- Build automatic sensitivity suppression like eBird/iNat taxon geoprivacy: auto-obscure or block reports for salmon/sea-trout rivers, spawning seasons, and protected waters — this doubles as regulatory compliance in Latvia and gives BIOR/Zemkopības ministrija a reason to endorse rather than fight the app.
- Use give-to-get (Glassdoor model) as the freeloader valve: the regional heatmap/forecast layer unlocks only for users who contribute recent reports. This directly answers the rival-goods objection ('why would I feed tourists my spots?') — you only see aggregate intel if you're also feeding it.
- Ride Latvia's existing rails instead of duplicating them: ManaCope has already normalized mandatory catch reporting (within 5 days, even nil catches), so 'log your catch' is not a foreign behavior — position the app as the fun/social layer on top, and pursue a citizen-science data agreement (MyCatch model) to earn institutional trust. Deeper (Lithuanian) proves Baltic anglers accept crowdsourced water data when it's depersonalized and opt-out exists for private waters.
- Protect top contributors from real-world exposure: Fishbrain users were approached in person by followers. Support pseudonyms, home-water privacy zones (Strava-style, extended to aggregate layers), and no per-user public location history that reveals someone's regular waters.
- Have an equity counter-narrative ready: the anti-secrecy camp (LNT 2020 revision, onX 'flattened learning curve') argues gatekeeping excludes newcomers — which is your target user. Frame the app as teaching newcomers HOW and WHEN (technique, conditions, season) rather than exactly WHERE, mirroring the morel burn-map pattern: predict habitat, don't disclose spots.
- Ship everything bilingual (Latvian + Russian) — the secrecy norms, etiquette vocabulary ('vietu neteikšu' / 'палить точки'), and distrust patterns are identical in both language communities, and moderation prompts/etiquette nudges need to speak both.
- Plan for the revolt scenario anyway: every platform in this space (Surfline, Fishbrain, onX, Strava) went through a public backlash. Mitigations to have ready: fast owner/community takedown path for burned spots (Deeper's private-pond removal precedent, theCrag's hide-without-delete), a published data-use policy addressing law-enforcement/legal disclosure (onX Waypoint 6), and visible community governance so norms are enforced by anglers, not just the company.