← PETRONATORLEGAL / cookies-2026-10-08-meta-v1

Cookies and browser storage

Version: cookies-2026-10-08-meta-v1 · 16 September 2026

Technologies

Cookies are small files sent to the browser. Local storage and session storage also store information on your device, but are not HTTP cookies; this policy covers them too. Basket and preference storage support the functions you request. Visiting the site alone does not authorise optional analytics, advertising or unnecessary external technologies.

Current inventory

Names may change with software versions; significant purpose changes require updated information. Local chat text is held in the open page's memory, and is not saved in localStorage. We do not create a persistent conversation identifier; the old unused petronator-anonymous-conversation-v1 record is removed when the chat next loads.

Stripe, Google Maps and external links

Card payment takes place in Stripe's environment. After navigating there, Stripe's information about its own payment-security and other technologies applies. This does not authorise the shop's own advertising trackers without a valid basis.

The address is displayed on this website. Google Maps opens only when you select the external “Open in Google Maps” link. Before that, the shop does not load the map. Google’s rules apply once you open the external service.

Viber and social-media links are opened at your choice. An ordinary link is not the same as an embedded tracking module.

Analytics and advertising

We use Google Tag Manager (container, when configured) purely as the technical mechanism that loads Google Analytics 4 (data stream G-D692VBKSSV). The purpose is usage statistics for the shop — visits, pages and shopping steps — so that we can maintain and improve the site. Google Tag Manager itself sets no measurement cookies; those are set by Google Analytics 4. More about Google Analytics cookies: https://support.google.com/analytics/answer/11593727.

We run Google Consent Mode v2 in basic/strict mode. Until you give explicit consent, every optional state — analytics_storage, ad_storage, ad_user_data, ad_personalization and personalization_storage — is “denied”, the Google container is not loaded at all and no request is sent to Google. Functionality and security states remain active because they serve the functions you request.

Analytics consent grants analytics_storage. Marketing consent grants ad_storage, ad_user_data, ad_personalization and personalization_storage. Consent for one category is not inferred from the other. Google Ads is not active. Meta is prepared and remains disabled until separately activated with valid consent.

On withdrawal we send an immediate update to “denied”, stop future optional measurement and remove the Google cookies known to us that the browser lets us reach. A Google library that has already loaded is not removed from the page; it simply has no permission to measure until consent is given again. Necessary PETRONATOR cookies and records are not deleted.

A saved preference is not consent to undisclosed future purposes or providers.

You can change preferences through “Cookies” in the footer. Refusing optional technologies must not prevent purchasing. Browser controls can remove stored information, potentially clearing the basket, preferences and checkout recovery. Changing local preferences is not a promise that an external provider has erased its records.

Contact: info@petronator.com. See the Privacy Policy for personal-data rights and international transfers.

Meta Pixel and Conversions API — when activated

The Meta integration is prepared and disabled by default. After activation and explicit marketing consent we use Meta Pixel and Conversions API for advertising attribution: visits, viewed or added product SKUs, checkout starts and actually paid purchases. Google analytics consent remains independent. An older choice without marketing version meta-v1 does not authorise Meta.

Meta may set _fbp and _fbc (normally up to 90 days). We use petronator-meta-consent, a necessary HttpOnly record proving and revoking your choice, for up to 12 months. Marketing version meta-v1 is stored in the existing consent record. Server events contain a pseudonymous identity, authorised Meta identifiers, SKUs, quantities and value in EUR; no name, email, phone, address, chat or health information.

Withdrawal stops future Meta events, sends consent revoke, removes accessible _fbp/_fbc and revokes server consent. Server revocation requires a successful connection to the shop and is retried when a request fails. Earlier events are never replayed after a later grant. Meta Platforms Ireland processing and international transfers are described in Meta privacy policy. Cash on delivery is recorded only after official proof of received payment.