Privacy Policy

Who we are

Cyclismo is an independent, individually operated site for tracking professional road cycling. If you have questions about this policy or your data, contact [email protected].

What we collect and why

• Cookieless site analytics. We use Cloudflare Web Analytics, a privacy-first, cookieless measurement beacon that reports aggregate traffic (e.g. page views) without fingerprinting visitors or setting a tracking cookie. It only loads when an analytics token is configured for the deployment.
• Anonymous comment identity. If you post a comment, we set a single strictly-necessary cookie (cyclismo_anon) so your comments can be attributed to a consistent anonymous identity. It is httpOnly, signed, and expires after 30 days.
• Optional account. If you choose to sign in, we use Supabase to manage authentication (e.g. email sign-in). We do not require an account to browse or read the site.

Cookies

We do not show a cookie-consent banner because we do not use advertising or tracking cookies. Our site analytics are cookieless, and the only cookie we set is the single strictly-necessary comment-identity cookie described above.

Who processes your data

We rely on a small number of infrastructure providers to run the site: Cloudflare (content delivery, security, and analytics), Microsoft Azure (hosting and file storage), and Supabase (account authentication). We do not sell your data or share it with advertisers.

Your rights

You have the right to access and delete the personal data we hold about you. If you have an account, you can delete it yourself at any time from your profile; this removes your comment history and, in production, your authentication account. To request access to your data, or for help with deletion, contact [email protected].

Data retention

The anonymous comment-identity cookie expires automatically after 30 days. Account data and comments are retained until you request deletion.

Changes to this policy

We may update this policy as the site changes. The "Last updated" date above reflects the most recent revision, and this page describes the site's actual data-handling behaviour as of that date.