How service-request information is handled

Information collected

We collect the information you choose to submit: your name, phone number, optional email address, ZIP code, requested service, problem description, preferred contact method, consent, and the page used to submit the request.

We also collect limited first-party traffic data: a random session identifier, page path, referring hostname and path without its query string, allowed UTM campaign fields, advertising click identifiers, device category, browser and operating-system family, coarse version, language, screen and viewport size, pixel density, touch capability, processor and memory class when the browser exposes them, and coarse connection-quality settings.

Behavioral events include page views, ten-second visible engagement, total visible time, 50% and 90% scroll thresholds, form starts, submissions, phone-link clicks, performance measurements, and anonymous element impressions and click positions. Element tracking uses predefined labels such as “hero phone” or “form submit”; it does not collect the text a visitor types.

When call tracking is active and you call a displayed tracking number, we collect the caller number when supplied by the telephone network, the number called, call status, connection result, duration, time, and the site session and acquisition source associated with that temporary number lease. Calls are not recorded.

Our hosting provider processes the complete network address and request headers to deliver and secure the site and may retain them in infrastructure or security logs under its own retention rules. Our application analytics database does not copy that complete address: it stores a masked network range such as an IPv4 /24 or IPv6 /48. The hosting provider may also supply approximate country, state or region, city, metro area, timezone, network number, network organization, and optional bot-management signals. We store a coarse browser or crawler family, not the complete user-agent string, so server requests can be grouped as likely human, verified bot, likely bot, suspected automation, or unknown.

How it is used

We use submitted information to review your request, contact you, evaluate service-area coverage, prevent abuse, and arrange follow-up with an appropriate service provider when one is available. We do not promise that a provider will accept the request.

Traffic data is used to understand which pages, search engines, referral placements, campaigns, keywords, creatives, devices, browsers, viewport sizes, locations, networks, and page elements produce engaged visits and service requests; compare first-touch with last non-direct attribution; identify low-quality or abusive traffic; exclude identified internal testing; and improve speed, usability, and conversion performance.

Analytics boundaries

The analytics system does not store full IP addresses, full user-agent strings, precise latitude or longitude, browser fingerprints, keystrokes, form-field values, payment data, or arbitrary URL query strings. It also does not capture session video or create persistent fingerprints. Heatmaps are aggregated from anonymous click coordinates and predefined element labels; they are not recordings of individual visitors. Network and bot categories are probabilistic and can be wrong, especially when a visitor uses a VPN, cellular network, corporate gateway, or spoofed crawler name. A random session identifier and last-activity time may be held in first-party browser storage so visits can be grouped into a 30-minute session.

Sharing and retention

If a match is available, request and call information may be shared with one selected provider, buyer, or dispatcher only to evaluate, route, respond to, and account for the service request. That organization acts separately and may contact you about the request. This site may receive compensation if the selected provider accepts or purchases the lead. Email, hosting, analytics, CRM, and telephone infrastructure providers process information for those operations. We do not disclose submitted customer information to multiple competing providers and do not sell it as an unrelated marketing list.

Open leads are kept while the request is being handled. Closed leads are deleted or irreversibly redacted during routine retention cleanup after they are 24 months old unless a shorter period is requested or a longer period is required for security, disputes, accounting, or law. Masked network ranges are cleared after 30 days. Raw analytics events, page interactions, performance measurements, and advertising click identifiers are cleared after 90 days. Anonymous session and attribution records are cleared after 13 months. These application cleanups run as new requests or traffic are processed. Infrastructure and security logs are controlled by the relevant hosting provider’s retention policy.

Your choices

You can choose not to submit the form and can call instead. You may also ask that we stop contacting you or request deletion of your submitted information, subject to legal and security requirements.

Contact

Email the shared campaign privacy inbox at tom@charlottegaragedoorhelp.com to ask a privacy question, stop contact, or request deletion or correction of submitted information.