This notice names every cookie pejera.com sets and who else reads it.
Read it in order: what a cookie is, what's on this site, which platforms set one once you allow storage, and exactly what keeps working if you decline.
This notice describes the cookies and browser storage keys used on pejera.com, the advertising identifiers attached to a paid click, and the consent framework that keeps advertising and analytics storage switched off by default.
Effective date. This cookie notice took effect on 7 September 2026 and describes the site as it runs from that date. Where we change what a cookie does, the change lands here on the same day it ships, not on a delay.
Categories in use. Three categories of storage run on this site. Strictly necessary storage keeps the site and the chat widget working and cannot be switched off, because without it the contact form and chat token wouldn't function at all. Analytics storage measures how many visitors reach a page and which one they came from. Advertising storage lets Google Ads, Microsoft Advertising and, where a campaign runs there, Meta Ads connect a click to whatever happens on this site afterward.
Only the first category is active by default. The other two stay off until a visitor actively allows them through the banner described below.
The cookie table. Below is every cookie or storage key this site or its advertising partners can set, what sets it, what it's for, and how long it lasts once it's allowed to run.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
| site_consent_v2 | Pejera Electric, first party | Remembers whether you allowed or declined advertising and analytics storage. | 12 months |
| pejera_chat_token | Pejera Electric, first party | Reconnects you to an open support chat conversation in your own browser. | Until you clear browser storage |
| _gcl_au / gclid | Google Ads | Links a click carrying gclid to a later enquiry, once ad_storage is allowed. | 90 days |
| _ga, _ga_* | Google Analytics | Counts repeat visits and page views, once analytics_storage is allowed. | Up to 2 years |
| _uetsid, _uetvid | Microsoft Advertising | Links a click carrying msclkid to a later enquiry, once ad_storage is allowed. | Session, and up to 16 days |
| _fbp / fbclid | Meta Ads | Links a click carrying fbclid to a later enquiry, where a Meta campaign is running. | 90 days |
Advertising platforms. Google Ads and Microsoft Advertising run paid traffic to pejera.com today, and Meta Ads may. A click from a Google Ads campaign carries gclid in the landing URL; a click from Microsoft Advertising carries msclkid; a click from a Meta Ads campaign carries fbclid. Each identifier is read from the URL and, once advertising storage is allowed, stored so a later enquiry can be attributed back to that click.
Consent Mode v2. This site runs on Google's consent mode, version 2. Four signals govern it: ad_storage, ad_user_data, ad_personalization and analytics_storage. All four load denied on every visit. They switch to granted only after a visitor chooses "Allow storage" in the banner at the bottom of the page. Choosing "Decline," or withdrawing consent later from the cookie choices link in the footer, sets all four straight back to denied, immediately, for the rest of that visit and any that follow until consent is given again.
Giving or changing consent. The choice is made through the banner that appears on first visit, and it's stored under the key site_consent_v2 described in the table above. To change a choice already made, use the "Cookie choices" link in the footer of every page on this site, which reopens the same banner and lets a visitor allow or decline again.
If you decline. The site itself, the inquiry form and the support chat all work exactly the same whether advertising and analytics storage are allowed or not — none of that storage is required to book a job. What stops is measurement: without it, we can't tell which ad or search term brought a given visit, and the ad platforms can't personalise anything shown to that visitor on this site.
The platforms' own policies. Google's account of its own cookies and data handling sits at policies.google.com. Microsoft's is the Microsoft privacy statement at privacy.microsoft.com. Meta publishes its own cookie and data policy directly on its own site. None of these documents is ours to edit or to guarantee; we link to them because the platforms, not us, control what those cookies do once they leave pejera.com.
Questions about a specific cookie. Email office@pejera.com naming the cookie or the page it appeared on, or call +1 (296) 555-4780 during shop hours, and we'll trace it back to the platform that set it. See the privacy policy for how the data behind any of this is used and kept, and the data request page to ask for a copy or a deletion.