I'm Nico Ferreira, and this page is the closest thing Trail Tattler has to a rulebook. Not because hiking needs bureaucracy, but because I've watched people get into real trouble …
I'm Nico Ferreira, and this page is the closest thing Trail Tattler has to a rulebook. Not because hiking needs bureaucracy, but because I've watched people get into real trouble following advice that was written by someone who never left their desk. This policy explains how I decide what to cover, how I check my facts, what I'll say about gear, and how you can call me out if I get something wrong — because eventually, I will.
Trail Tattler exists to tell on trails. Not on hikers. Every piece I publish is trying to fill in what the official trailhead sign, the tourism-board blurb, or the vague AllTrails description leaves out: how much elevation you actually gain per mile, when the parking lot fills, what the tread looks like after rain, and where the unsigned junction will make you second-guess yourself. My background is six years volunteering with search and rescue and eight years before that in outdoor retail, and both jobs taught me the same lesson — the word "moderate" has ruined more afternoons than any storm. You can read more about how I got here on the About Us page.
Every route or gear article on this site is written by me, and I hike or test whatever I write about — not a review pieced together from other blogs. My process, generally:
When I bring in outside information — a closure notice, a permit change, a rescue statistic — I link back to the source or name the agency so you can verify it yourself. I'd rather under-claim than pad a page with confidence I haven't earned.
I choose what to cover based on three things: trails and gear I have direct, current experience with; questions I see hikers actually ask (in trip reports, at trailheads, from friends who show up in cotton in November); and seasonal relevance — flash flood risk in summer, ice on north-facing switchbacks in winter, that kind of thing. I don't chase every trending destination just because it's trending. If a place is getting overloaded past what its parking lot or trail can handle, I'll say so rather than send more traffic its way.
Trail conditions change — a bridge washes out, a permit system launches, a fire reroutes an entire section. I revisit older posts and update numbers, closures, and photos when I learn something has shifted, rather than leaving stale information live indefinitely. If I haven't personally been back to a trail in a while, I'll say so in the article rather than imply it's a fresh report.
I spent eight years selling outdoor gear before I ever wrote about it, and that job taught me that the wrong pack or boot ruins more trips than bad weather does. My approach to recommendations:
Some pages on this site contain affiliate links, meaning I may earn a small commission if you buy through them, at no extra cost to you. That never determines what gets recommended — it just helps keep the lights on. Full details live on the Affiliate Disclaimer page, and our broader stance on advertising and partnerships is on the Disclosure page.
Trail Tattler runs ads and occasionally works with outdoor brands on sponsored content or gear loans. When that happens, I disclose it clearly within the article itself — no hidden sponsorships, no disguised advertorials. If you're curious about a collaboration or want to propose one, the Collaboration page explains how that process works and what I will and won't do.
I'm one person hiking a lot of miles, and I get things wrong sometimes — a mile marker, a reopening date, a water source that's since dried up. When that happens, I correct the article as soon as I confirm it, and for anything safety-related, I update it immediately rather than waiting for a scheduled review. If you spot something off — a closed trailhead, an outdated shuttle schedule, a number that doesn't match what you saw on the ground — email me directly at [email protected]. I read every message, and trail reports from actual hikers are often more current than anything I can find from an agency website.
Comments and shared trip reports are welcome, and they're genuinely useful — some of the best condition updates on this site have come from readers. But I moderate with the same philosophy as everything else here: no shaming hikers for gear, pace, or turning back, and no unverified claims presented as fact. Our full expectations for how people engage here are laid out in the Community Guidelines, and I'd rather remove a comment than let bad advice sit unchallenged on a page people use to plan an actual hike.
For how we handle your data, cookies, and site terms, see the Privacy Policy, Cookie Policy, and Terms of Use. Our general limits on liability and advice are covered in the Disclaimer — trail conditions change fast, and no article replaces checking current conditions before you go.
If any of this raises a question I haven't answered, reach out. I'd rather explain my reasoning than have you guess at it.