Cookie Policy
Tremo — mobile app and tremocoach.com
Last updated: 16 August 2026
This Cookie Policy explains how Mucha Solutions UG (haftungsbeschränkt), trading as Tremo ("we", "us"), uses cookies and similar technologies on tremocoach.com and in the Tremo mobile app, in accordance with § 25 TDDDG (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz, the German implementation of the ePrivacy Directive) and the GDPR.
It should be read together with our Privacy Policy.
1. What this policy covers
"Cookies" are small text files placed on your device by a website. On tremocoach.com, this means browser cookies. In the Tremo mobile app there are no browser cookies, but comparable technologies exist — local storage, mobile advertising identifiers (IDFA on iOS, GAID on Android) and push notification tokens. This policy covers both, referred to together as "cookies."
2. Current status: essential only
As of the date above, tremocoach.com and the Tremo app do not use any analytics, advertising, or marketing cookies. We only set the strictly necessary cookies listed in § 3 below, which are required for login and payment security and do not require your consent under § 25(2) TDDDG.
We do not currently run Google Analytics, Meta/Facebook Pixel, TikTok Pixel, Plausible, PostHog, Mixpanel, or any comparable tool. Sections 4–6 describe, concretely, what we would deploy if we activate analytics, functional preferences, or marketing tracking in future — so that this policy will already be accurate and a consent banner can be switched on without needing a rewrite.
3. Strictly necessary cookies (active now, no consent required)
These are set automatically because the service cannot work without them. Under § 25(2) No. 2 TDDDG they do not require consent, but we disclose them for transparency.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
sb-access-token, sb-refresh-token | Supabase (our backend, on tremocoach.com only) | Keeps you logged in and authenticates your session | Access token: 1 hour; refresh token: up to 30 days |
__stripe_mid | Stripe | Fraud prevention and risk assessment during checkout | 1 year |
__stripe_sid | Stripe | Fraud prevention during a checkout session | 30 minutes |
cookie_consent | tremocoach.com (first-party) | Stores your cookie banner choice so we don't ask again | 6 months |
In the app, the equivalent is a securely stored session token (device keychain / encrypted storage), which serves the same authentication purpose and is likewise exempt from consent requirements.
4. Functional cookies (not yet active)
If we add optional convenience features, we would use cookies such as:
| Name (example) | Purpose | Duration | Consent |
|---|---|---|---|
tremo_lang | Remembers your selected language on the website | 1 year | Not required (§ 25(2) No. 2 TDDDG — first-party, user-requested preference) |
tremo_theme | Remembers light/dark mode preference | 1 year | Not required, same basis |
These would only ever be first-party, first-request preferences (not tracking), so they would not require a consent banner, but they will be listed here when enabled.
5. Analytics cookies (not yet active)
If we introduce product or website analytics, the realistic candidates are:
| Tool | Example cookies | Purpose | Consent required |
|---|---|---|---|
| Google Analytics 4 | _ga, _ga_<container-id>, _gid | Aggregate website usage statistics (pages viewed, sessions, referrers) | Yes — opt-in via banner, Art. 6(1)(a) GDPR |
| PostHog (self-hosted or EU cloud) | ph_phc_* | Product analytics inside the app/website (feature usage, funnels) | Yes — opt-in via banner/in-app prompt |
| Plausible Analytics | None (cookieless by design) | Aggregate website traffic without personal data | No cookie consent needed, but would still be disclosed here |
| Mixpanel | mp_*_mixpanel | In-app event analytics | Yes — opt-in |
If activated, only one of these tools would be deployed at a time, it would be named specifically at the top of this table (removing the others), and it would only load after you accept analytics cookies in the banner. You would be able to withdraw consent at any time, and no analytics cookie would be set before consent is given.
6. Marketing / advertising cookies (not yet active)
We do not currently run paid advertising or retargeting. If we do in future, the realistic candidates are:
| Tool | Example cookies | Purpose | Consent required |
|---|---|---|---|
| Meta (Facebook/Instagram) Pixel | _fbp, fr | Ad conversion tracking and retargeting | Yes — opt-in |
| TikTok Pixel | _ttp | Ad conversion tracking | Yes — opt-in |
| Google Ads | _gcl_au, _gcl_aw | Conversion tracking for paid search/display ads | Yes — opt-in |
| LinkedIn Insight Tag | li_sugr, bcookie | B2B ad conversion tracking (e.g. coach acquisition campaigns) | Yes — opt-in |
None of these are currently loaded on tremocoach.com or in the app. If any is added, this table will be updated to reflect only the tool(s) actually in use, and each will require explicit opt-in consent before it loads — no marketing cookie will be set on page load or app open by default.
7. Mobile app identifiers
If we add attribution or push-notification analytics to the app, this may involve:
- IDFA (iOS) — only accessible after you grant permission via Apple's App Tracking Transparency (ATT) prompt. We do not access IDFA without this explicit OS-level consent.
- GAID (Android) — used only if an analytics/attribution SDK is added, and disclosed here at that time.
- Push token — used to deliver notifications you have enabled in-app; this is functional, not tracking, and tied to your notification settings rather than a separate cookie consent.
8. How consent works
Where a cookie in §§ 5–6 is activated in future:
- A consent banner will appear on your first visit to tremocoach.com (and, where relevant, an in-app prompt), before any non-essential cookie is set, in compliance with § 25(1) TDDDG and Art. 6(1)(a) GDPR.
- You will be able to accept all, reject all, or choose by category (essential / functional / analytics / marketing).
- You can change your choice at any time via a "Cookie settings" link in the website footer (once added) or in the app under Settings → Privacy.
- Withdrawing consent will stop new cookies of that category from being set and will not affect the lawfulness of processing before withdrawal.
9. Managing cookies in your browser
Independently of our consent tool, you can block or delete cookies at any time through your browser settings:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Safari: Settings → Privacy → Manage Website Data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Edge: Settings → Cookies and site permissions
Blocking strictly necessary cookies (§ 3) will prevent login and checkout from working correctly.
10. Changes to this policy
We will update this Cookie Policy whenever we activate a new category or tool from §§ 4–7, so the tables above always reflect what is actually running on tremocoach.com and in the app — not a generic list of possibilities. The current version is always available in the app and on tremocoach.com.
11. Contact
Questions about cookies or this policy:
Mucha Solutions UG (haftungsbeschränkt)
Zwillingstrasse 4, 80807 München, Germany
Email: muchasolutions.info@gmail.com
Phone: +420 601 359 752
Related documents
Controller: Mucha Solutions UG (haftungsbeschränkt) · Amtsgericht München HRB 315278 · Geschäftsführer: Adrian Malucha · Zwillingstrasse 4, 80807 München, Germany · muchasolutions.info@gmail.com · +420 601 359 752 · Last updated: 16 August 2026