Cookie Policy

Cookies are small text files that a website or an embedded service stores in your browser. Similar technologies, such as local storage and session storage, work in a comparable way.

GFitness itself does not use optional analytics, advertising or tracking cookies, and does not store anything in your browser's local or session storage. The technical hosting infrastructure may set cookies required for secure and reliable website delivery.

Our hosting sets two technically necessary cookies on every page: __cf_bm (Cloudflare bot protection) and __dpl (a technical hosting cookie). Both are listed in the overview below.

Your language is determined by the page address (for example /de), not by a cookie.

Our contact page includes an embedded Calendly booking calendar. The Calendly widget is loaded when the page is opened. Calendly categorises some cookies and similar technologies (from Calendly, Cloudflare, Stripe and Google reCAPTCHA) as necessary for providing, securing or operating the booking service. It also uses optional technologies depending on your consent.

Calendly provides its own cookie consent interface within the booking widget. You can reject optional cookies (Reject All), accept them (Accept All), or manage them individually through Cookie Settings.

According to the consent information shown in the widget, optional technologies may be used for purposes including personalisation, analysis of website interactions (including clicks, cursor movements and screen recordings) and marketing. In our test, these optional technologies were only loaded after Accept All — for example Google Analytics, Google Tag Manager, Meta (Facebook) Pixel, Segment, Sprig and Braze. After Reject All, none of them were loaded.

Pages on the GFitness website that do not contain the Calendly booking widget are not affected. More information: Calendly privacy notice.

The following cookies were observed on the GFitness website, including the contact page:

Before any choice, the Calendly widget also uses browser storage for security and operation: Calendly _cache (local storage, functional), Stripe fraud-prevention entries (session storage) and Google reCAPTCHA entries rc::a / rc::c (security). After Accept All, Calendly additionally stores analytics identifiers from Segment (ajs_anonymous_id, ajs_user_id) and Sprig (userleap.ids, sprig.anon.env.vid.map) in local storage. These are not set after Reject All.

Durations are those observed in our test. Third-party providers may change their cookies at any time.

The onboarding questionnaire uses Cloudflare Turnstile to protect against automated submissions and spam. Turnstile is only loaded on the final step. Our automated test observed one technical entry ( cf.turnstile.u) in the local storage of Cloudflare's challenge frame, but did not observe a Turnstile cookie. The test could not complete human verification, so storage after a successful check may depend on the applicable Turnstile configuration. Turnstile is not used for analytics or advertising (Cloudflare privacy).

The GFitness website itself does not use any non-essential cookies.

For the embedded Calendly booking calendar, you can reject or accept optional cookies directly in the consent banner provided by Calendly. Use Cookie Settings to manage your choice in more detail.

You can also view and delete cookies, or block third-party cookies, in your browser settings at any time.

If you block cookies required by Calendly, the booking calendar may not work fully. You can always contact us at andy@gfitness.eu.