Legal document
Cookie Policy
Last updated: 30.06.2026
1. What Cookies Are
Cookies are small text files saved on your device by the browser when you use TrainTeam. Local browser storage and session storage may work in a similar way. They help us recognize the session, remember preferences, keep sign-in secure and - with your consent - measure how the application works.
2. Which Cookies We Use
We use cookies that are necessary for the application to work, cookies from providers that support billing and integrations, and analytics cookies that run only after consent. We do not use advertising cookies or remarketing.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| sb-* (Supabase auth) | Supabase | Keeps the signed-in user session active. | up to 30 days |
| cookieyes-consent | CookieYes | Stores your cookie consent preferences. | up to 12 months |
| trainteam_google_calendar_oauth_state | TrainTeam | Protects against CSRF attacks while connecting Google Calendar. | 10 minutes |
| __stripe_mid, __stripe_sid | Stripe | Fraud prevention during checkout and in the billing portal. | up to 1 year |
| ph_*, posthog_* | PostHog | Product analytics, errors and performance after analytics consent. | up to 12 months |
| _ga, _ga_* | Google Analytics | Usage statistics after analytics consent. | up to 2 years |
| cf_*, _vercel_* | Cloudflare / Vercel | Security and performance of the hosting infrastructure. | session |
3. Your Cookie Controls
You can change consent at any time in the CookieYes preferences panel available from account settings, or disable/delete cookies in your browser settings. Disabling cookies required for the service may prevent you from signing in to TrainTeam or may stop some features from working correctly.
Third-party provider cookies, such as Stripe or Google cookies, are set only when you use features that require them, such as payment, calendar integration or analytics after consent.
4. Contact
Send cookie questions to contact@trainteam.pl. You can find the full data-processing information in the Privacy Policy.