Updated 22 October 2026
Cookies & consent
Google Ads and Meta Pixel remain blocked until you allow advertising measurement. Rejecting them leaves the website, WhatsApp, email and telephone links available.
Necessary preference storage
numuno-consent-v1 is a first-party localStorage entry, not an advertising cookie. It records the consent version, your yes/no choice and the time saved. Both acceptance and refusal are valid for 180 days. An expired or outdated consent version cannot enable tracking. Adding Meta requires a new choice from visitors whose old choice covered Google only. The entry remains until replaced or cleared. Clearing browser storage prompts a new choice.
Before consent and after refusal
Google Basic Consent Mode v2 starts with ad_storage, analytics_storage, ad_user_data and ad_personalization denied. Neither Google's script nor Meta's Pixel is downloaded before permission, so neither can send cookies or measurement pings. No earlier actions are queued for later reporting. There is no unconditional Meta noscript tracking image.
What acceptance changes
Allowing ad measurement loads one Google tag AW-18484830809 and one Meta Pixel 1666154745177549 per page document. For Google, ad_storage and ad_user_data are granted; analytics_storage and ad_personalization stay denied. Google may send base measurement requests containing technical connection data, page context and ad click identifiers. Google personalisation, remarketing, Google Signals and Enhanced Conversions are not enabled by this integration. Meta sends PageView for actual page changes and one Lead for a successfully accepted live contact form when consent and the Pixel were active both on submission and confirmation. Failed and demo submissions are excluded. Automatic event configuration and automatic history views are disabled to avoid extra events. Our code supplies no advanced-matching data, form contents or custom-audience configuration.
Advertising cookies
When allowed, Google may set first-party _gcl_ cookies, including _gcl_au and, depending on advertising entry and Google configuration, _gcl_aw or _gcl_gb. Cookie expiry is configured to 90 days. Actual cookies depend on your browser and entry route. Browser expiry does not specify how long Google retains server-side records. Google explains its cookies and information use in the links below.
Meta cookies and page views
With permission, Meta may create first-party _fbp and _fbc cookies to identify a browser and advertising clicks. Actual cookies and their expiry depend on Meta, your browser and how you arrive; see the Meta cookie policy below. Meta receives page URLs, referrer and technical connection data and may associate visits with an account. PageView measures a visit, not a message, enquiry or sale. We do not send earlier visits or clicks after you accept.
Conversions remain separate
WhatsApp conversions are not active until the real Conversion Label is configured. The base tag can send page-view/context requests after consent; these are not treated by our site as enquiries. Visiting the contact page, email or call clicks and form button presses do not send conversion events. Only a live form submission confirmed by the server can send Meta Lead and the separate Google Ads lead conversion, under the consent and SDK-readiness conditions above. A random submission identifier prevents duplicates. Form fields and sale amounts are not sent to either measurement service.
Change or withdraw your choice
Open Cookie settings in any page footer. Accept and reject are equally available. Withdrawal saves your refusal, removes readable first-party Google Ads and Meta _fbp/_fbc cookies on this site and reloads the page to unload both providers. The refusal is also applied in other open tabs. Unsent form contents would be lost on reload. We cannot delete cookies on other domains or data Google or Meta have already received; use your browser and the providers' privacy controls for those.
Other services
WhatsApp, email and telephone are ordinary external links and do not depend on advertising consent. Opening them uses the relevant service with its own privacy rules. Vercel delivers this site; our implementation includes no Vercel analytics script.