Cookie Policy

Authentication and keeping you signed in (HttpOnly, Secure, SameSite)

BeRelevant (first-party, berelevant.now)

The primary record of your cookie decision - stored in your browser's localStorage (not as a cookie), containing your choice for each category separately, the date it was given, and the policy version

BeRelevant (first-party, localStorage in your browser)

A flag indicating that you have already made a cookie decision, so the server does not show the banner repeatedly

BeRelevant (first-party, berelevant.now)

A short-lived record of the campaign you arrived from - it holds only the utm parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term), the landing page address without its query string, and a timestamp. Advertising click identifiers (gclid, fbclid and the like) are never stored in it. Our server writes it at the moment of a redirect (for example / to /sk), because the redirect strips those parameters from the address and they could not be recovered otherwise. It exists solely so we can tell which channel brought your current visit.

BeRelevant (first-party, berelevant.now)

Remembering the language version of the site (sk / cz / en)

BeRelevant (first-party, Next.js)

Storing your interface theme setting (light / dark / follow system). Written only when you switch the theme yourself, and mirrored in localStorage under the key theme. It contains no identifier and is never used for tracking.

BeRelevant (first-party, berelevant.now + localStorage)

Short-lived memory of your signed-in session inside the browser tab, so the interface does not briefly render as signed out while the session is being verified. It holds your user id, email address, role and subscription tier. It is written only after you sign in, never for a signed-out visitor.

BeRelevant (first-party, sessionStorage in your browser)

Timestamp of an in-progress sign-in redirect, used solely to detect and stop an infinite redirect loop. It contains no personal data.

BeRelevant (first-party, sessionStorage in your browser)

Security flag marking that the current session is an administrator session temporarily acting on behalf of a user (impersonation). It keeps the warning banner visible in the interface. It is set only during that administrative action, never on a normal visit.

BeRelevant (first-party, berelevant.now)

Bot and spam protection on forms (CAPTCHA alternative)

Cloudflare, Inc. (third-party, USA - DPF certified)

Detecting and diagnosing application errors to keep the service reliable. Sentry stores NOTHING on your device - no cookie, no storage entry. An error report is sent directly to its European ingest endpoint (ingest.de.sentry.io) and contains technical error data, the page address, browser type and your IP address. It is sent before any cookie consent is given, because it is necessary to keep the service running - the legal basis is legitimate interest under Art. 6(1)(f) GDPR, not consent, and you may object to it (contact details in section 10).

Functional Software, Inc. (Sentry, third-party, EU data ingest - Germany, SCC safeguards)

Remembering whether you keep the in-app sidebar collapsed or expanded

Remembering that you skipped the onboarding guide so it is not shown again

Remembering that you dismissed the email verification notice

Remembering which of your brands you last had selected, so the same one opens when you come back. It is written only when you pick a brand yourself, and only inside the signed-in part of the app.

Temporary copy of the values you typed into the run-audit form (industry, location, notes) so they are pre-filled the next time you run an audit in the same session. It is written only after you submit the form.

A note about the last quick audit you ran - the audited domain and its score, nothing else. It lets us offer to continue where you left off after a reload or after closing the result, instead of showing an empty form. The analysis itself is not stored, nor is anything you told us about yourself, and an audit is never re-run from it automatically.

List of premium features whose limits you have already hit in this session, used solely so we do not repeat the same prompt (and the follow-up email). It is written only after you sign in and only on first contact with such a feature.

Stores your conversation with the voice assistant - a transcript of the last 50 messages (both your questions and the assistant's replies), a summary of the last call (its length and message count) and the assistant language you picked, so you can pick up where you left off after a reload or a page change. It is written only after you start the assistant yourself, and only if you allowed functional storage. If you withdraw functional consent we delete the stored transcript immediately; you can also delete it yourself with "Clear conversation" inside the assistant panel.

A flag recording that the voice assistant's introductory bubble should no longer be shown. It holds the single value "true", contains no identifier, and is written when you close the bubble yourself OR when you open the assistant - in both cases only after your own click. It is an interface preference, not strictly necessary storage. It is not used for tracking. Like the transcript, it is kept only with functional consent - if you withdraw that consent we delete it together with the transcript.

Purpose: When you start a call yourself, the browser asks for microphone access and connects directly to wss://api.elevenlabs.io, streaming your microphone audio there in real time; the voice reply and its transcript come back over the same connection. ElevenLabs therefore processes your voice and the content of the conversation together with your IP address and browser details. The short-lived access URL for that connection is issued at our request by the Prebi platform (api.prebi.eu), to which we pass your IP address to protect the service from abuse. Neither ElevenLabs nor Prebi stores anything on your device. Until you start a call the microphone stays off and nothing is sent - simply loading the page does not begin a conversation.

Provider: ElevenLabs, Inc. (third-party, USA - Standard Contractual Clauses) and Prebi (voice platform operator, EU)

Shared Data: ElevenLabs: real-time microphone audio, the content of the conversation and its transcript, IP address, browser and device details. Prebi: your IP address (to cap how often a call can be started and to prevent abuse); nothing else about your visit is passed to Prebi, not even the address of the page you start the call from. If you fill in the contact form at the end of a call, we process the details you submit ourselves - see the Privacy Policy.

Purpose: Google Analytics 4 - traffic measurement and on-site user behavior

Provider: Google Ireland Limited / Google LLC (third-party, USA - Data Privacy Framework certified)

Shared Data: Truncated IP address, device and browser data, visit time, pages visited, on-page events. The same events (e.g. a completed payment) may also be sent server-side via the Google Measurement Protocol, carrying the same event identifier so the two are deduplicated.

Purpose: Measurement script management - Google Tag Manager loads analytics and marketing tags only after the relevant consent is granted (Google Consent Mode v2). Tag Manager itself stores no cookie on your device.

Provider: Google Ireland Limited / Google LLC (third-party, USA - Data Privacy Framework certified)

Shared Data: Loaded tags, device data, on-page events (only after consent). Note: the _gcl_au cookie belongs to the Google Ads conversion linker, which is NOT deployed on berelevant.now and is never set.

Purpose: Our own visit attribution - stores the source of a visit (utm parameters, referrer, landing page) at the first and the most recent touch so we can tell which channels bring users. It contains no advertising identifiers.

Provider: BeRelevant (first-party, berelevant.now)

Shared Data: Not shared with third parties. After sign-up the contents are sent to our own backend to evaluate acquisition channels.