Data Privacy and Security Guidelines

We built giantlittlerock for people who love bikes, not for people who love handing over personal data. This policy lays out what we collect, why we collect it, and the controls you get to keep. No legalese maze.

Last updated: June 16, 2026.

Here's the short version before the details: we ask for the minimum we need to run route guides, bike reviews, and training plans. When you read a trail write-up or save a workout, that shouldn't cost you your privacy. The longer version below explains the mechanics, because you deserve specifics rather than vague reassurances.

Third-Party Integrations and Analytics

A cycling site doesn't run in isolation. We lean on a handful of outside tools to keep pages loading fast and to understand which routes riders actually click on.

Analytics platforms tell us aggregate patterns. How many people opened a winter training plan, which gravel route got shared most, whether a review page loaded slowly on mobile. That data arrives stripped of anything that names you personally.

What these partners can see

• Aggregated page views and session duration, never tied to your real identity.
• General location at the region level, used to suggest nearby local routes.
• Device and browser type, so we can fix display bugs.

Embedded maps and video players sometimes set their own cookies. We flag those interactions where we can, and you can manage cookie behavior through our Cookie Policy. If a third party changes how it handles data, that's governed by their terms, not ours, which is why we keep the list of integrations lean.

Information We Collect from Riders

Two buckets. Things you hand us directly, and things your browser reports automatically.

When you sign up for a newsletter, leave a comment on a bike review, or message us through the Contact page, you give us your email and whatever you choose to type. That's the direct stuff. We don't ask for a home address to read a training plan, and we never will.

Automatic collection

Servers log standard technical data on every visit. IP address, timestamp, the page you landed on. This is how websites work, and it's how we catch abuse and keep the lights on. We keep these logs short-lived.

If you submit a ride photo or route correction, that content becomes part of the relevant article unless you ask us to remove it.

How We Use Your Information

Every piece of data we hold maps to a concrete purpose. If we can't point to a reason, we don't keep it.

We do not sell your data. Not to advertisers, not to data brokers, not to anyone. Newsletter emails get used for newsletters, full stop. The one exception to our keep-it-internal rule is when a law requires disclosure, which has not been a routine occurrence for a publication our size.

Your Data Protection Rights

You own your information. These rights apply whether you're a daily reader or someone who landed here once searching for a gravel loop.

• Access. Ask what we hold about you and we'll tell you.
• Correction. Spot something wrong? We'll fix it.
• Deletion. Want out entirely? Say so and we erase your records, subject to any logs we're legally required to retain.
• Unsubscribe. Every email has a one-click opt-out. No hoops.

To exercise any of these, message us through the Contact page. We aim to confirm receipt quickly and resolve the request within a reasonable window. We may ask you to verify your identity first, because handing data to the wrong person would defeat the purpose.

Policy Updates and Contact Information

Privacy practices shift as tools and laws change. When we update this policy, we revise the date at the top and, for significant changes, flag it on the site.

We'd rather be honest about scope than overpromise: this policy covers giantlittlerock itself. Once you click off to a partner's video player or an external trail map, their rules take over, and we can't speak for them.

Questions about anything here? Head to our Contact page and write to us directly. A real person on the team reads those messages. You can also review the related Terms of Service and our Cookie Policy for the full picture.