How Tifolab handles user data
This public release is deliberately small. The privacy surface should be just as explicit.
What we collect
Tifolab stores the search parameters, page views, and in-session shortlist state needed to run the product and understand where the workflow fails. When support emails are sent to the team, the contents of that message are also retained.
How data is used
Usage data is used to operate the service, diagnose broken routes, improve ranking and comparison flows, and monitor abuse. Tifolab does not sell personal data or run an ad network.
Cookies and local storage
Tifolab uses two categories of browser storage. Essential storage holds session shortlist state, onboarding state, and authentication. Analytics storage powers product analytics through PostHog (cookies prefixed with "ph_") and is only set after explicit consent. The cookie banner shown on first visit records the choice in the "sd_consent" cookie for one year; clearing site data resurfaces the banner.
Third-party services
Tifolab relies on infrastructure partners for hosting (Hetzner, Germany), product analytics (PostHog, US region — only after consent), error monitoring, payments in private environments, and football data delivery. Only the minimum data required to operate each integration is shared.
Retention and deletion
Operational logs are retained only as long as needed for reliability, fraud prevention, and legal obligations. Contact the team if you need a data-access or deletion request handled manually.
Need a manual privacy request handled?
Use the support contact listed on the contact page and include the browser or email context you want reviewed.