PedalBase

Privacy Policy

Last updated: 30 July 2026

PedalBase (“we,” “us,” “our”) is responsible for the data described in this policy.

Who is responsible for your data

Controller: Martin Bargum (currently an individually-run site — no registered business yet; will be updated with CVR/company details once that exists)
Contact: info@pedalbase.eu

What we collect and why

Technical/server data. Our hosting provider (Vercel) automatically logs standard technical data — IP address, browser type, request timestamps — for security and operational purposes. This is standard for any web host and not something we separately access or repurpose.

Analytics. With your consent, we use Google Analytics to understand how visitors use the site (pages viewed, time on site, approximate location, device type). Google Analytics uses cookies and processes data on Google's servers, which may be located outside the EU/EEA (including the United States). This transfer is covered by Google's Standard Contractual Clauses. We do not combine this data with anything that identifies you personally.

Affiliate links. When you click an outbound link to a retailer, the affiliate network handling that link may set a cookie or pass a click identifier to attribute the referral, so we can earn a commission if you make a purchase. This happens between your browser and the affiliate network/retailer — we do not receive your purchase details, only aggregate confirmation that a referral occurred.

If you contact us. If you email us, we store your email address and message only for as long as needed to respond. We do not add it to a mailing list or share it onward.

Legal basis for processing

Who we share data with

We do not sell your data to anyone.

How long we keep data

Your rights

Under GDPR, you have the right to:

To exercise any of these, email info@pedalbase.eu.

Children

This site is not directed at children, and we do not knowingly collect data from children.

Changes to this policy

We may update this policy as the site evolves. The "last updated" date above reflects the most recent revision. Material changes (e.g. a new data use) will be reflected here and, where legally required, we'll ask for renewed consent.