Every clause below states what we collect and names who else sees it.
This policy took effect on 7 September 2026. Read it as a ledger, not a wall of text: each row names a clause, says what it means in plain words, and says why it applies to a visitor of pejera.com.
Rows marked in the source with a clause key so every requirement can be checked directly against the markup. On a phone each row reads top to bottom as its own block.
| Clause | What it means | Why it applies |
|---|---|---|
| Clause 01Effective date | This policy took effect on 7 September 2026 and governs pejera.com from that date forward. |
A visitor needs to know which version of the policy applies to their visit. |
| Clause 02Who operates this site | Pejera trades at pejera.com from 119 Workshop Way, Werkstatt 2, Austin, Texas 91826, United States. Pejera is the controller of the data described below. |
A reviewer or a regulator has to be able to identify the business behind the domain. |
| Clause 03Data collected |
The inquiry form takes name, phone, email, job address, the kind of job, your message, any device or breaker specification, and your consent tick. The support chat takes whatever you type, plus name, phone or email if you give them. Automatically, we log the IP address, browser user-agent string, referring URL, the moment a page rendered and the moment a form was sent. Cookie and local-storage identifiers are set as described in the cookie policy. Advertising click identifiers — gclid, msclkid and fbclid — are appended to the page URL by the platform when an ad is clicked and are read from that URL. |
Every field the site's own code actually writes has to be disclosed; nothing here is collected beyond that. |
| Clause 04Purposes |
Inquiry and chat data is used to answer the inquiry, schedule a walkthrough and follow up about a job. Technical and log data is used to keep the site running and to investigate abuse. Click identifiers and cookie data are used to measure which ad or search term led to a visit and, once allowed, to show relevant ads. |
A purpose has to be stated for each category, not assumed. |
| Clause 05Legal bases |
Responding to an inquiry rests on contract — you asked us to quote a job. Server logs and fraud checks rest on legitimate interest in keeping the site working. Advertising and analytics storage rest on consent, gathered through the banner described in Clause 07, and nothing in that category runs before that consent is given. |
Under the GDPR every purpose needs one of these bases stated explicitly, not implied. |
| Clause 06Advertising platforms |
Google Ads and Microsoft Advertising send paid traffic to this site today, and Meta Ads may. Google Ads attaches gclid to a clicked link; Microsoft Advertising attaches msclkid; Meta Ads attaches fbclid where a campaign is running. None of these platforms has reviewed or approved the content of this site; they only serve the ads that bring a visitor here. |
Ad platforms require their own click identifiers and their names disclosed on the destination page. |
| Clause 07Consent Mode v2 |
This site runs Google's consent mode v2. Until a visitor allows storage, the four signals ad_storage, ad_user_data, ad_personalization and analytics_storage are held denied. Choosing "Allow storage" in the banner sets them to granted; declining, or later withdrawing consent, sets all four straight back to denied. |
Google and Microsoft both require this signal from any site running their ad tags. |
| Clause 08Who receives this data |
Google Ireland Ltd and Google LLC receive the consent signals and the gclid tied to a Google Ads click. Microsoft Ireland Operations Ltd receives msclkid through Microsoft Advertising; its handling of that data is covered by the Microsoft privacy statement at privacy.microsoft.com. Meta Platforms Ireland Ltd receives fbclid where a Meta campaign runs. Our hosting provider stores the site and the enquiry database, and our mail provider carries the notification email to office@pejera.com. |
Naming each recipient, one by one, is what the GDPR and CCPA both call disclosure of third parties. |
| Clause 09Data transfers | The ad platforms named above are based partly in the European Union and partly in the United States and may process data outside the country where you are browsing. Where that happens under EU law, it relies on the platform's own standard contractual clauses; the hosting and mail providers store data in the United States, where this business is also based. |
A cross-border transfer needs a stated legal mechanism, not a silent assumption. |
| Clause 10Retention periods |
|
"As long as necessary" is not a period; a reviewer needs an actual number of months or days. |
| Clause 11Security measures | The site is served over HTTPS, the enquiry database sits behind the hosting provider's access controls, and only staff who need it to schedule or quote a job can read an inquiry. No card or payment data is ever collected, so none is at risk here. |
Stating what actually protects the data is more useful, and more honest, than a generic promise. |
| Clause 12Rights under the GDPR | A visitor reaching this site from Europe has the rights the GDPR sets out: access to their data, rectification of anything wrong, erasure, restriction of processing, portability of what was given directly, objection to processing based on legitimate interest, and withdrawal of consent at any time with no effect on anything done before that point. |
These rights have to be stated in full, not summarised down to "contact us." |
| Clause 13US state privacy rights | California residents have rights under the CCPA and its later amendments, including the right to opt out of the sale or sharing of personal information; other states with their own privacy laws in force carry equivalent rights. Pejera does not sell personal information, and the only "sharing" that occurs is the advertising data described in Clause 06, which stays switched off until a visitor allows it. |
California and the other states with active privacy statutes require this stated by name, not folded into the GDPR section. |
| Clause 14Global Privacy Control | If a browser sends the Sec-GPC header, this site treats it as an opt-out signal automatically — the same as declining the consent banner — and does not ask again for that visit. This is Global Privacy Control, honoured as such. |
Several US state laws make honouring this signal a requirement, not an option. |
| Clause 15Children | This site is built for adults arranging electrical work on a property. It is not directed at children, and no data is knowingly collected from anyone under 16. |
A stated age boundary is required even where the audience plainly isn't children. |
| Clause 16Complaints | A visitor may complain to their state Attorney General, or, in California, to the California Privacy Protection Agency, if they believe this policy hasn't been followed. A European visitor may complain to their own country's data protection authority. |
The right to complain has to point somewhere real, not just back to this site. |
| Clause 17Making a data request | Write to office@pejera.com or to 119 Workshop Way, Werkstatt 2, Austin, Texas 91826, or use the form on the data request page. We answer within 5 days, and we may ask for enough detail to confirm it's really your data before we act on it. |
Every rights clause above needs one working, stated process for actually using it. |
| Clause 18Changes to this policy | If this policy changes, the effective date at the top of this page moves forward and the new version replaces this one immediately. We don't maintain a public changelog beyond that date. |
A visitor returning later needs a plain way to tell whether the terms have moved. |
| Clause 19Contact a human | Email office@pejera.com or call +1 (296) 555-4780 during shop hours. A person answers both, not a queue. |
Every clause above is only as good as a real way to reach someone about it. |
Where GDPR and US law overlap
Most visitors to pejera.com are booking work in Texas and fall under US state privacy law. Where a visitor reaches the site from the European Union or the UK, the GDPR sections above apply in full alongside it; we don't run two different versions of the site, only two sets of rights against the same data.
Related pages
See the cookie policy for the specific cookies and storage keys this site sets, the terms of service for the contract behind a booking, and the data request page to exercise any right listed above.