Cookie policy
Updated 30 October 2026.
What we use and why
Data Studio Connect uses necessary cookies for sessions, security and remembering your decision. Optional measurement technologies remain blocked until you accept them. You do not need to accept them to visit the website.
Cookies and measurement technologies
| Type / provider | Purpose | Duration |
|---|---|---|
| Necessary · Data Studio Connect | Sessions and security for the private area. The dsc_cookie_consent cookie remembers your choice and its date; dsc_cookie_language remembers the language you choose for the banner. | Sessions according to their configuration; cookie choice and banner language, 180 days. |
| Necessary · measurement withdrawal | The technical dsc_commerce_revoke cookie is HttpOnly and allows withdrawal of server measurement categories even after signing out. It only permits reducing permissions: it cannot grant them or read account data. | Up to 180 days. |
| Analytics · Google Analytics 4 | Measure visits and navigation on public pages through _ga and _ga_*, and the subscription journey. When server measurement is configured, Google Analytics 4 Measurement Protocol receives checkout starts, purchases and renewals confirmed by Stripe, and confirmed refunds. It uses pseudonymous GA4 client/session identifiers and connector, currency, amount and VAT data. Measurement ID: G-G6QYP2ZZKN. Only after analytics consent. The optional analytics cookie dsc_ga_session stores the session identifier obtained through gtag.get for 30 minutes to preserve attribution from the website to checkout after signing in. It is created only with analytics consent and removed on withdrawal; it contains no user or organisation identifiers. | Cookies configured for up to 180 days. Pseudonymous server context lasts no longer than consent (180 days); event and delivery records default to 30 days, configurable. dsc_ga_session: 30 minutes. |
| Advertising · Meta Pixel | Measure visits, viewed content and campaign effectiveness through Meta Pixel; it may use _fbp and _fbc. When configured, Conversions API receives checkout starts, purchases and renewals confirmed by Stripe, and refunds identified as a custom Refund event rather than negative purchases. Pixel ID: 1424675016504629. Only after advertising consent. Only with advertising consent, we retain the browser’s real technical User-Agent string, obtained from the request header, in encrypted form. Meta Conversions API receives it only for website-originated checkout starts and the initial purchase. System-generated renewals, refunds and adjustments omit it, and our server does not send this field to GA4. It is neither fabricated nor derived from personal information. It expires with the consented context after at most 180 days and is removed when advertising consent is withdrawn; email, IP address, names and internal user or organisation identifiers are not sent. | Cookies typically last up to 90 days, according to Meta. Pseudonymous server context lasts no longer than consent (180 days); event and delivery records default to 30 days, configurable. |
Google Ireland Limited and Meta Platforms Ireland Limited provide these tools. They may process browser, visit and connection information according to their terms. Their processing may involve international transfers and is described in their policies.
Choose and withdraw your consent
In the banner, you can reject all optional cookies, accept them or configure analytics and advertising separately. Neither option is selected initially. You can reopen your preferences using the Cookies button, visible on every page. Reject and accept are offered at the same level.
When you withdraw permission, we stop the corresponding measurement, remove cookies in that category accessible from our domain and reload the page to unload tags that were already active. Your decision is stored for 180 days; we will then ask you again. Withdrawal does not reverse data already processed by providers or remove their cookies on other domains. You can also manage cookies in your browser. When you are signed in, your choice is also recorded on our server. Pseudonymous context is stored encrypted. Withdrawal or expiry blocks new submissions in that category, including pending renewals. Server submissions are not used to bypass your choice. The technical dsc_commerce_revoke cookie is HttpOnly and allows withdrawal of server measurement categories even after signing out. It only permits reducing permissions: it cannot grant them or read account data. Pseudonymous Google or Meta identifiers are encrypted and expire with consent, after at most 180 days. Minimal Checkout attribution and cumulative refund state are retained to link renewals and prevent duplicates while a subscription remains active or consent remains valid. They are purged once both purposes have ended and 180 days have elapsed since the last attribution activity; this period can be configured shorter. They contain no provider credentials and are not sent to the platforms. Event and delivery records keep their separate default retention of 30 days.
Protected data and pages
We measure visits to public pages without sending form fields, names, emails, passwords or connected-account data as event parameters. Private routes, OAuth callbacks and URLs with unrecognised parameters remain excluded from third-party tags. Server commerce measurement, when enabled and consented to, uses pseudonymous GA4 or Meta identifiers, opaque event/transaction identifiers and catalogue, currency, amount and VAT data from operations confirmed by Stripe; it does not send email, IP address, internal user/organisation identifiers or credentials. Only with advertising consent, we retain the browser’s real technical User-Agent string, obtained from the request header, in encrypted form. Meta Conversions API receives it only for website-originated checkout starts and the initial purchase. System-generated renewals, refunds and adjustments omit it, and our server does not send this field to GA4. It is neither fabricated nor derived from personal information. It expires with the consented context after at most 180 days and is removed when advertising consent is withdrawn; email, IP address, names and internal user or organisation identifiers are not sent.
See the privacy policy for the controller’s identity, contact information and how to exercise your rights. Google advertising signals and Meta advanced matching are not enabled. Purchases, renewals and refunds use a single server source to avoid duplication with the browser pixel. TikTok is planned, but is not active and receives no data.