Page traffic and performance
Cloudflare Web Analytics measures aggregate page traffic and site performance. It is configured without advertising cookies or visitor profiles.
Optional Google Analytics is not enabled on this site.
Website privacy
Simple measurement. Clear contact choices.
This site measures a few basic actions and offers a short help-request form. It does not use advertising cookies, create visitor accounts or advertising profiles, or sell website data.
Privacy at a glance
- No account is required.
- We do not use advertising cookies or create visitor advertising profiles.
- Form details are used only to reply and manage the request.
- Website form requests older than 180 days are removed.
What this website records
We collect only what is needed to understand the site and reply to a request.
Contact selections and form activity
We count when someone selects a phone, text, request-help, or Google Business Profile link, and when a help form is first used. We store the page and calendar day, but no form details unless the request is sent.
Help-request details
If you send the form, we store your name, the phone number or email you provide, your city if provided, your message, the page used, and the time of the request so we can reply. We may also store the first page visited, a selected problem type, campaign source, medium and name, and the referring website hostname when those details are available. Aggregate reports may identify a known search engine, Yelp, or ChatGPT from that hostname when no campaign labels were supplied. This is referral attribution, not proof that a particular answer or search result recommended the business. Campaign response links use only general source, medium, and campaign labels. They are not designed to include a recipient name, email address, phone number, company name, or problem details.
When the owner manually records a contact attempt, the site stores the request reference, the selected phone, voicemail, text, or email attempt type, the time, and a unique code used to prevent duplicate form submissions. That record documents the owner's selection. It does not prove delivery or a customer response.
The owner may record whether the request is qualified, booked, or completed, and the amount collected for completed work. These details stay in the private request record and may be combined into source-level business reports. They are not sent to public website analytics. The form does not collect payment-card or bank-account details.
Limited use and retention
Request details are used to respond and manage the requested service. They are not sold or added to an advertising list. Website form requests older than 180 days are removed during a daily cleanup and may also be removed when a new request is saved or the private request inbox is opened. Recorded contact attempts tied to a website form request are removed with that request, along with its recorded stage and collected amount. Separate service records may be kept when reasonably needed for a customer relationship or recordkeeping requirement.
Website delivery and security
The hosting service may process standard request information and set essential security cookies needed to deliver and protect the site. The request form does not store raw IP addresses. For abuse prevention, it may store a one-way code derived from the network address. The code is assigned an expiration of no more than 48 hours, and expired codes are removed during a daily cleanup or when a later request is saved. The form does not ask for browser identifiers, passwords, security codes, bank details, or attachments. For first-touch attribution, the browser keeps only the first page path, selected campaign labels, and referring hostname in session storage for the current tab. It does not keep the full referring address, the page query, a user ID, or a cross-session identifier. If email notifications are enabled, the email delivery provider processes the request so it can reach the business inbox. You do not need to create an account.