Cookies and browser storage have separate jobs.
Browser storage / paid arrivals / withdrawal
Necessary operation.Some processing is needed to deliver a page, defend the forms against abuse and pass a message to Tervuq. Strictly necessary operation is separate from an advertising choice. Refusing optional storage does not turn a public service page into a restricted page, and it does not stop you using an email or telephone link.
A remembered preference.The browser record site_consent_v2 stores the versioned consent choice. Its purpose is to apply your decision on later pages without repeatedly asking. The consent record is retained for 6 months. A browser can remove local data earlier, including through private browsing or a manual clear operation.
Requested conversation.Starting a support conversation creates a token that connects later messages to that conversation. The token is stored in localStorage so you can return from the same browser. This is user-requested chat continuity, not an advertising identifier. The server keeps the conversation separately; deleting the browser token does not itself delete the transcript.
Analytics.Optional analytics storage supports measurement of site use. It is governed by the storage choice, not by whether you submit a project request. A transcript, message or requested specification does not belong in analytics, and inquiry contents are not used as analytics payloads.
Advertising.Optional advertising storage supports attribution and advertising measurement, and personalization where allowed. It is distinct from the records needed to answer a business website development inquiry. Permission to handle an inquiry or a support conversation does not authorize advertising storage.
Paid arrivals.Google Ads, Microsoft Advertising and Meta Ads send traffic to this destination. Their click identifiers can arrive in the address bar: gclid for Google Ads, msclkid for Microsoft Advertising and fbclid for Meta Ads. These parameters identify an advertising click; their presence in a URL is not a consent choice.
Link parameters are not cookies.A click identifier is carried in a link before any decision to persist it in browser storage. Do not assume that removing a visible URL parameter deletes a provider's existing records, or that seeing the parameter means you have accepted cookies. Optional identifier persistence remains governed by your storage choice.
Referral context.The inquiry route records the referring URL along with technical request details. A referral can contain a query string. If you send a page address yourself, remove private tokens or account details first. There is no reason to include a signed-in link in a general website technical support inquiry.
Consent mode defaults.Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied before advertising and analytics processing begins. All four remain denied until you allow optional storage. Choosing Allow optional storage updates those signals to granted.
What each signal decides.ad_storage concerns advertising-related storage. ad_user_data concerns sending user data for advertising purposes. ad_personalization concerns personalized advertising. analytics_storage concerns analytics-related storage. They are separate signals even though this site's controls apply a single optional-storage decision to all four.
Withdrawal.Declining or withdrawing explicitly restores ad_storage, ad_user_data, ad_personalization and analytics_storage to denied. This applies to the present choice, not just to a future visit. Withdrawal does not reverse processing already carried out lawfully before the choice changed.
Denied is not disconnected.Consent-aware network signals can still occur while storage is denied. A refusal is not a claim that no tag loads or that every network request disappears. The important boundary is that optional storage and the four consent signals stay denied until allowed, and return to denied after refusal.
What still works.You can read the service pages, use the transfer calculation and send an inquiry after declining optional storage. A support conversation can use its requested token independently of advertising permission. The site does not put a cookie wall between you and its contact details.
What stops.Optional advertising and analytics storage is not permitted after decline. Previously granted consent signals are reset to denied. The necessary preference record may still remember that refusal, which avoids treating the next page load as an invitation to ask again.
Browser-level opt-out.Global Privacy Control, including the Sec-GPC header, is honored as an opt-out without asking again. While that signal is active, Allow optional storage is disabled and the current-choice message explains why. It is not a request to remove operational records that Tervuq needs to answer an inquiry. For a record request, use the personal data request route.
Blocked storage.If preferences cannot be saved, optional storage retains denied defaults and the interface explains the limitation. A browser that blocks localStorage may also prevent a conversation token from surviving a reload. Use email or phone if the browser cannot preserve the conversation you need.
Clearing a browser.Most browser privacy settings let you inspect site data and remove cookies or localStorage. Clearing site_consent_v2 removes the remembered choice; it does not grant consent. Clearing a chat token can break the link back to an existing conversation. Clearing local data is different from asking Tervuq to delete server records.
A different device.A choice made on one browser does not automatically apply to another browser or phone. Check the controls in the browser you are using. Private windows may discard both the preference and chat token when closed.
Google.Google Ireland Ltd / Google LLC receives Google Ads click and consent information as applicable. Read the Google privacy policy at policies.google.com for Google's own processing and controls. A provider policy describes the provider, not the terms of a Tervuq development project.
Microsoft.Microsoft Ireland Operations Ltd handles Microsoft Advertising data. Its own handling is explained in the Microsoft privacy statement at privacy.microsoft.com. That statement includes information about Microsoft advertising technologies and privacy choices.
Meta.Meta Platforms Ireland Ltd handles Meta Ads information where a campaign runs there. The Meta privacy policy explains Meta's processing. Visiting a provider link takes you to its own website and its own privacy controls.