Cookie Policy
Effective date: March 29, 2026
1. What Are Cookies?
Cookies are small text files placed on your device when you visit a website. They serve various functions such as remembering your preferences, enabling core functionality, and helping us understand how the Platform is used. This Cookie Policy explains which cookies myHERALD uses, why we use them, and how you can manage them.
2. Legal Framework
We comply with § 25 TTDSG (Telekommunikation-Telemedien-Datenschutz-Gesetz) and the ePrivacy Directive. Strictly necessary cookies are set without consent as they are essential for the Platform to function. All other cookies are only set after you have given your informed consent via our cookie banner.
3. Cookie Categories
3.1 Strictly Necessary Cookies
These cookies are essential for the Platform to function correctly. They cannot be disabled. No consent is required for these cookies under § 25 Abs. 2 TTDSG.
| Cookie Name | Provider | Purpose | Duration |
|---|---|---|---|
| sb-*-auth-token | Supabase | Authentication session token. Keeps you signed in and identifies your session securely. | Session / 1 year |
| sb-*-auth-token-code-verifier | Supabase | PKCE code verifier for secure OAuth flows. | Session |
| cookie_consent | myHERALD | Stores your cookie consent preferences. | 1 year |
3.2 Analytics Cookies
These cookies help us understand how visitors interact with the Platform. They are only set after you give consent via our cookie banner ("Accept All"). They are not activated if you choose "Necessary Only."
| Cookie Name | Provider | Purpose | Duration |
|---|---|---|---|
| _ga | Google (GA4) | Distinguishes unique visitors. Used by Google Analytics 4 to measure site traffic and usage patterns. | 2 years |
| _ga_<ID> | Google (GA4) | Maintains session state for Google Analytics 4. | 2 years |
| ph_<token>_posthog | PostHog | Identifies unique visitors for product analytics. PostHog instance is EU-hosted (eu.posthog.com). | 1 year |
3.3 Functional Cookies
These cookies are set by third-party services that provide specific functionality on the Platform. They are loaded only when you interact with the relevant feature.
| Cookie Name | Provider | Purpose | Duration |
|---|---|---|---|
| __stripe_mid | Stripe | Fraud prevention during payment processing. Set when interacting with checkout or payment forms. | 1 year |
| __stripe_sid | Stripe | Session identifier for payment processing. Set during active payment sessions. | 30 minutes |
| cal.com cookies | Cal.com (Cal.com Inc.) | Scheduling and booking functionality. Loaded on pages with embedded booking calendars. | Session / varies |
4. Cookie Banner and Consent Management
When you first visit our Platform, you are presented with a cookie banner that allows you to:
- Accept all cookies
- Accept only strictly necessary cookies
You can change your cookie preferences at any time by clearing your browser cookies for this site. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.
5. Managing Cookies via Browser Settings
Most web browsers allow you to control cookies through their settings. You can typically:
- View and delete existing cookies
- Block all cookies or only third-party cookies
- Set preferences for specific websites
Please note that blocking strictly necessary cookies may impair Platform functionality, including the ability to sign in.
6. "Do Not Track" and "Do Not Sell" Signals
We honor the Global Privacy Control (GPC) signal. If your browser sends a GPC signal, we treat it as a valid opt-out request under the California Consumer Privacy Act (CCPA/CPRA).
We do not sell or share your personal information for cross-context behavioral advertising.
7. Third-Party Cookies
myHERALD does not set any third-party cookies for advertising or cross-context behavioral advertising. However, certain third-party services used on the Platform, including analytics providers (PostHog, Google Analytics 4) and our payment processor (Stripe), may set cookies as described in Sections 3.2 and 3.3 above. Analytics cookies require your consent; functional cookies related to payment are set only when you initiate a payment interaction.
8. Changes to This Cookie Policy
We may update this Cookie Policy to reflect changes in our practices or for legal, regulatory, or operational reasons. If we add new cookie categories requiring consent, we will re-display the cookie banner so you can make an informed choice.
9. Contact
If you have any questions about our use of cookies, please contact us:
Email: [email protected]
For more information about how we process your personal data, please see our Privacy Policy.