- Home
- Privacy
We keep what a job inquiry needs, and ad tracking stays off until you say yes.
This is how a commercial electrician in Phoenix handles the details you send us: the inquiry form, the chat, the logs our server writes, and the click identifiers that Google Ads, Microsoft Advertising and Meta Ads put on a link. Real periods, named companies, one email address that reaches a person.
01 When this policy took effect
This privacy policy takes effect on October 2, 2026 and replaces anything this site said about personal data before that date. If we change it, the date at the top of the page changes with it. Section 19 says how.
Last updated: October 2, 2026
02 Who runs this site and holds your data
The site at phoenixelectricianstoday.de is operated by Phoenixelectricianstoday, trading as Phoenix Electricians Today, an electrical contractor working on commercial installations in the Phoenix metro. We decide what is collected here and why, which makes us the controller of that data.
Postal address: 23309 N 17th Dr, Phoenix, Arizona 85027, United States.
Email: [email protected]
Phone: 623-209-5244
This policy is governed by the law of Arizona, United States, and any dispute about it is heard in the courts of Phoenix.
03 Exactly what we take, and nothing past it
No accounts, no passwords, no card numbers. Nothing is sold on this site and no payment is taken here. What does come in falls into five groups.
- The inquiry form. When you send the form on the contact page or the home page,
vuge882.phpstores your name, phone, email, the job address, the kind of inquiry, your message, the specification you typed (amperage, phase, fixture count, whatever you put there) and the consent tick. - What rides along with the form. Your IP address, your browser's user-agent string, the referring URL, the moment the form was rendered and the moment it was sent. The two timestamps are how we spot bots that fill a form in 0.4 seconds.
- The support chat.
tomad87.phpkeeps the conversation, plus any name, phone or email you choose to give, and a token stored in your browser so you can come back to the same thread. - Your cookie choice. Stored in your browser under
site_consent_v2. Nothing else on this site persists a choice. - Advertising click identifiers and ad cookies. If you arrived from an ad, the link carries a gclid, msclkid or fbclid. Ad and analytics cookies are only set after you allow them. The cookie policy lists every one by name.
04 What each piece is used for
Your form details go to one place: the person who calls you back to set up a site walk. The address tells us which side of the 101 we're driving to and whether the building is likely on a 208V or 480V service. The specification field saves a phone call.
IP address, user-agent and timestamps are used to block spam and abuse of the form and chat, and to work out what went wrong when something fails. Chat messages are used to answer you. The consent record is used to remember your answer so the banner doesn't ask again on every page.
Click identifiers and ad cookies, when you allow them, tell the ad platform that a click turned into an inquiry. That's how we see which campaign is worth paying for and which one is burning money on searches for residential ceiling fans. We do not build profiles of you, and we do not sell or rent your details to anyone.
05 The legal basis for each purpose
For visitors reaching us from Europe, the GDPR asks us to name a legal basis for every use. Here they are. Visitors elsewhere get the same treatment.
| Data | Purpose | Legal basis |
|---|---|---|
| Inquiry form fields | Answering your request and preparing a site walk and written quote | Steps taken at your request before a contract; your consent tick for contact |
| IP, user-agent, referrer, timestamps | Stopping spam and abuse, fault-finding | Legitimate interest in keeping the form and server usable |
| Chat conversation and token | Replying to you and keeping the thread together | Consent, given in the chat before the first message |
site_consent_v2 | Remembering your cookie choice | Legal obligation to record consent; legitimate interest |
| gclid, msclkid, fbclid and ad cookies | Measuring which ads lead to inquiries | Consent, through the cookie banner |
| Analytics cookies | Counting visits and seeing which pages get read | Consent, through the cookie banner |
06 The ad platforms sending people here
We pay for clicks. Google Ads, Microsoft Advertising and Meta Ads send traffic to this site today, mostly on searches like "commercial electrician phoenix" and "electrician near 85027". When you click one of those ads, the platform adds its own click identifier to the address in your browser bar.
gclidGoogle AdsmsclkidMicrosoft AdvertisingfbclidMeta Ads_gcl_au, _uetvid, _fbpSet only after Allow
The identifier is a random string. On its own it does not name you. If you allow storage, the platform's tag can match that string to the fact that an inquiry was sent, and report the conversion back to our ad account. If you decline, the identifier sits in the URL and goes nowhere. None of these companies has reviewed this site on our behalf, and nothing here says otherwise.
07 Consent Mode v2 starts every signal at denied
We run Google Consent Mode v2. Before the page does anything else, it sets four signals to denied: ad_storage, ad_user_data, ad_personalization and analytics_storage. They stay denied until you press Allow on the cookie banner.
Press Allow and all four switch to granted, and your choice is written to site_consent_v2. Press Decline, or come back later and withdraw through the Cookie settings button in the footer, and all four go straight back to denied. No ad or analytics cookie is written while they are denied. Microsoft's UET tag reads the same choice.
The full cookie list and what each signal controls are on the cookie policy.
08 Who else receives data, one by one
- Google Ireland Ltd / Google LLC for Google Ads. Attaches gclid to a click and receives the Consent Mode signals. Its policy is at policies.google.com/privacy.
- Microsoft Ireland Operations Ltd for Microsoft Advertising. Attaches msclkid. Its handling is covered by the Microsoft privacy statement at privacy.microsoft.com/privacystatement.
- Meta Platforms Ireland Ltd for Meta Ads. Attaches fbclid where a campaign runs there.
- Our hosting provider, which serves this site and stores the inquiry and chat database on its servers.
- Our mail provider, which carries the notification of a new inquiry to our office inbox.
The hosting and mail providers act on our instructions only. The ad platforms are independent controllers for what they do with the conversion data once they have it. We share nothing with general contractors, suppliers or anyone else unless you've asked us to bring them into a job.
09 Data crossing borders
We're in Arizona. If you send an inquiry from Europe, your details travel to the United States to reach us. The ad platforms named above move data between their European entities and the United States as well.
Those transfers rest on the EU Standard Contractual Clauses and, where the receiving company is certified, the EU-U.S. Data Privacy Framework. Your inquiry itself crosses the Atlantic because you asked a Phoenix contractor to contact you, which the GDPR permits where a transfer is necessary to take steps you requested.
10 How long each thing is kept
Fixed periods. When they run out, the record is deleted, not archived.
| Record | Kept for | Why that long |
|---|---|---|
| Inquiries and their email copies | 36 months | Repeat jobs on the same building often come back two or three years later, and the old notes save a site walk |
| Chat transcripts | 12 months | Long enough to pick a thread back up |
| Server and access logs | 30 days | Fault-finding and spotting abuse |
| Record of a consent choice | 6 months | After that the banner asks again |
If an inquiry becomes a signed job, the scope, permit and inspection paperwork follows the job file and its own record-keeping rules, not this table.
11 How the data is protected
Every page and form travels over HTTPS. The inquiry database sits behind a login that only the office uses, and the files that hold it are not reachable from the public web. Form and chat input is checked on the server before anything is stored, and the hidden fields and timestamps throw out most automated junk before it lands.
No system is perfect, so we keep less. No card data, no ID documents, no passwords. If a breach ever touches your details, we tell you and the relevant authority within the time the law sets.
12 Your rights under the GDPR
If you reach this site from the European Union, the European Economic Area or the United Kingdom, the GDPR gives you these rights over what we hold about you:
- Access: a copy of everything we hold on you.
- Rectification: wrong phone number, wrong address, we fix it.
- Erasure: we delete it, unless the law makes us keep a record.
- Restriction: we keep it but stop using it while a dispute is sorted out.
- Portability: your form and chat data in a plain machine-readable file.
- Objection: to anything we do on legitimate interest, including the spam screening run on your form entry.
- Withdrawing consent: any time, through Cookie settings in the footer for cookies, or by email for contact. It does not undo what was lawful before.
Section 17 explains how to use any of them.
13 Your rights under US state privacy law
Residents of California have rights under the CCPA as amended by the CPRA: to know what personal information we collect and why, to get a copy, to correct it, to delete it, to limit use of sensitive information, and to opt out of the sale or sharing of personal information for cross-context behavioral advertising. We don't sell personal information. Allowing ad cookies so a platform can measure a conversion can count as "sharing" under California law, so declining on the banner, or sending a Global Privacy Control signal, is your opt-out.
Residents of the other states with privacy laws in force, including Colorado, Connecticut, Virginia, Utah, Texas, Oregon and others, get the same rights on the same terms. We will not charge you more, refuse a quote, or treat a job differently because you used any of them. An authorized agent may make a request for you with your signed permission.
14 Global Privacy Control is honored
If your browser sends the Global Privacy Control signal (the Sec-GPC header), we treat it as an opt-out of sale and sharing and as a Decline on the cookie banner. All four Consent Mode signals stay denied. We don't ask you again and we don't put a banner in your way to change your mind.
15 Not a site for children
This site is for property managers, general contractors and business owners booking electrical work. It is not aimed at anyone under 16 and we do not knowingly take data from children. If a child has sent us something, email us and we delete it.
16 Complaining to a regulator
Talk to us first if you can; most things get sorted in one email. If you're not satisfied, you can complain to your state Attorney General. In California you can also go to the California Privacy Protection Agency. Visitors from Europe can complain to the data protection authority in the country where they live or work.
17 Making a data request
Email [email protected] with "Data request" in the subject, or write to 23309 N 17th Dr, Phoenix, Arizona 85027, United States. Tell us which right you're using and give us the name and the email or phone you used on the form or in the chat, so we can find the record.
- We confirm we've received it, usually the same working day.
- If the details don't match a record cleanly, we ask one question to check it's you. We don't ask for ID documents.
- We answer within 7 days of receiving the request, with the copy, the correction or the confirmation that the record is gone.
There is no charge. If a request is plainly abusive or repeated, we will say why we're refusing it and you can take that to a regulator under section 16.
18 Accessibility of this site
We build this site to WCAG 2.1 level AA as the working target. Every page has a skip link, one main heading and a logical heading order. Every control can be reached and used with a keyboard and shows a 2px orange focus outline. Text sits on the dark ground at contrast ratios above 4.5:1. Tap targets are at least 44 pixels. Animations stop when your system asks for reduced motion, and the layout holds from a 320-pixel phone to a wide monitor.
Known gaps: the panelboard diagram on the home page is described in a numbered list rather than read out from the drawing itself, and the cookie table needs sideways scrolling on narrow screens. If something blocks you, call 623-209-5244 or email [email protected] and we'll take the inquiry by phone and fix the page.
19 When this policy changes
A change is published here with a new date in section 01. If it changes what we collect or who receives it, the cookie banner shows again so you can make a fresh choice, and anyone with an open inquiry gets an email about it. We don't apply a new use to data collected under the old wording without asking.
20 A person answers privacy questions
The same office that books site walks answers these. Email [email protected], call 623-209-5244, or write to Phoenixelectricianstoday, 23309 N 17th Dr, Phoenix, Arizona 85027, United States.
For the cookie detail see the cookie policy. For quotes, site access and the workmanship warranty see the terms. If you came here to book work, the contact page takes the job details, or see what we install first.