Policy on Cookies and Similar Technologies

1. Scope

This policy explains how information is stored on devices on Detailero websites and web applications. The mobile apps use similar local identifiers and device permissions; push notifications can be turned off on the device.

Besides classic cookies, this also covers the localStorage and sessionStorage technologies; for simplicity, we refer to all of them together as cookies.

2. Necessary technologies

Without consent, we use only technologies required for signing in, security, maintaining the session, storing your cookie choice, storing your language choice, protecting forms with Cloudflare Turnstile, routing traffic and the basic functioning of the application. These technologies cannot be turned off in the banner, because the service might not work without them.

3. Choices

On your first visit, you can accept or reject analytics and marketing; each category is separate, and consent to one does not mean consent to the other. Rejecting them has no effect on the service. You can change your choice at any time using the Cookie settings link in the footer or, once signed in on the web, in your account settings (Ad measurement). When you withdraw consent to analytics, we delete the analytics identifier from your device and from then on measure only without cookies, just as for someone who never gave consent. When you withdraw consent to marketing, we delete the Meta Pixel cookies (_fbp, _fbc) and the Pixel stops sending data. We do not treat earlier consent to analytics as consent to marketing; if you gave it before 24 October 2026, the banner will ask about marketing again.

4. Overview

• Supabase authentication and session storage – necessary, for the duration of the session or while you are signed in.
• Detailero cookie choice – necessary, stores your consent or refusal under the key ph_consent, recommended period 6 months.
• Language choice – a necessary technology, no consent required. When you choose a language (or the site redirects you once to the Slovak version based on the country of your connection), we store the choice in the cookie detailero_locale and on your device under the key detailero.locale, for 12 months. It is used only so that the site is displayed in the language you chose.
• Cloudflare Turnstile – necessary security check of forms, short-term.
• PostHog – analytics with European storage. Without consent, it stores nothing on your device. It assigns the visit to an identifier that PostHog computes on its servers from the IP address, browser data and a random key; the key changes every day and is deleted when the day ends. Visits from the same browser therefore cannot be linked across days. Such an identifier is not anonymous: it is pseudonymous personal data and we handle it in accordance with the Privacy Policy . Only with consent does it use cookies and a persistent identifier, which allow it to recognize a repeat visit and, for a signed-in user, to link it to the account, that is, to its identifier and e-mail. We use it to measure which pages people use and where the application gets stuck, including records of application errors. PostHog keeps records of visits and events for no more than 1 year and then deletes them.
• Meta Pixel (Marketing category) – measurement of ads on Facebook and Instagram. It loads exclusively on the studio page (/for-studios) and only after your consent in the Marketing category; it does not load at all in the mobile app. When you visit the studio page it sends a PageView event, and when you click the studio registration button it sends a Lead event. The request also carries the address of the page (including campaign parameters and the ad click identifier) and the address of the page you came from. Meta may match the data with its own cookies on facebook.com or with a signed-in Facebook or Instagram account. On our website Meta stores the _fbp cookie (browser identifier) and, if you arrive from an ad, also _fbc (ad click identifier). The retention period is set by Meta under its own policies. The recipient of the data is Meta Platforms Ireland Ltd., Ireland; the data may also reach the USA, where the transfer is covered by certification under the EU-U.S. Data Privacy Framework. When you leave the studio page the Pixel is paused, and when you withdraw consent we delete the cookies. See the Privacy Policy for details.

5. Contact

Send questions about these technologies and privacy to info@detailero.com.

6. Status at launch

Detailero uses no Google Analytics or remarketing pixels and does not share data with advertising networks, with one exception: on the studio page (/for-studios) we use, with consent in the Marketing category, the Meta Pixel to measure ads on Facebook and Instagram. No advertising pixel loads on other pages or in the mobile app. The other optional technologies are the PostHog analytics and the Meta Pixel described above. If others are added later, they will not be activated before this document is updated and valid consent is obtained where it is required.

7. Legal framework in the Czech Republic and Slovakia

Necessary storage of information on the device, or access to it, is used only to the extent required for a service explicitly requested by the user. Analytics, personalization and marketing technologies that store information on the device or access it are activated only after prior consent; traffic measurement without cookies under point 4 stores nothing on the device. We apply the same rules to Czech and Slovak visitors.

8. Banner requirements

The first layer offers equivalent buttons Accept all, Reject optional and Customize. Optional categories are not enabled in advance. Consent is recorded together with the version of the text, the categories and the time; withdrawing it is as easy as giving it.

9. Mobile apps

The mobile apps may use secure local storage for sign-in, a device token and a push identifier. The system permission for push notifications can be changed in the device settings. Marketing push notifications require, in addition to the system permission, the corresponding marketing permission; operational push notifications may be necessary for a requested feature.

How we handle personal data in general is described in the Privacy Policy .