Privacy

CoachBadge does not use cookies, does not store anything in your browser and does not run advertising or analytics trackers.

Newsletter

What we store: your email address, the time you signed up, a random unsubscribe code and the time the welcome email was sent. Nothing else: no name, no browser details.

Abuse protection: to limit sign-ups to five per connection per hour, the sign-up service keeps a one-way hash of your IP address combined with the current hour (not the address itself), and deletes it after two hours.

Why: to send you the weekly email you asked for, with newly opened courses and deadlines coming up. We do not sell or share the list, and we do not use it for anything else.

Where: the list is kept in a database run by Supabase, in its EU (Frankfurt) region. Only the site team can read it; the sign-up form can add an address but cannot read the list.

Sending: emails are sent through Resend, an email service, from hello@coachbadge.com. You get one welcome email when you sign up, then the weekly email. Your address is passed to Resend only to deliver them.

How to unsubscribe: every email has a one-click unsubscribe link (and an unsubscribe header your mail app can use). It deletes your address, sign-up time and unsubscribe code straight away and keeps no record of the request.

Affiliate links

Some links are affiliate links: if you buy through them, CoachBadge may earn a commission at no extra cost to you. These links carry a referral code in the address so the other site can credit CoachBadge. CoachBadge sets no cookies; the site you visit may set its own, under its own privacy policy.

Visits

The pages include a tiny visit counter that is currently switched off. If it is ever switched on, it would only send the page address, with no cookies or identifiers, and it stays off when your browser sends Do Not Track or Global Privacy Control, or when the page is loaded by an automated browser.

The site is hosted on GitHub Pages. GitHub may log technical data such as IP addresses to run and secure the service; see GitHub's privacy statement.

Corrections are sent as public GitHub issues, so please do not include personal details in them.