Privacy
This notice explains how Sprinkler Blowout 406 handles information collected through this website. Preferred-date requests do not reserve an appointment. Online booking is available through the business's hosted Zenbooker page, where Zenbooker confirms completed bookings.
Preferred-date requests and business records
A request may contain a name, email or phone, requested service, service area, preferred date and optional note. Authorized Google administrators with Site access can view the shared business workspace. Legacy inquiry evidence is retained. A preferred-date request is not a confirmed booking or marketing consent. When owner-configured notifications are enabled and sender setup is ready, a request may generate an email notice; saving a request does not guarantee email delivery.
Contact messages
The separate contact form asks for your name, email address and message; it accepts no attachments. A receipt means the message was saved to this app's private workspace. It is not an appointment, a promise of a response time, or proof that an email notification was delivered. Authorized administrators can view contact messages for up to 30 days. Deleting a message immediately removes its content from app access and cancels a notification that has not been sent; a minimal record remains to prevent stale requests from restoring it. Expired content becomes unavailable and is removed through the existing bounded Admin retention operation; cleanup is not scheduled.
If owner-configured notifications are enabled and their sender setup is ready, the message may be sent to owner-configured recipients through Cloudflare Email. If notification setup or sending is unavailable, the app can still save the message; no email delivery or reply is guaranteed. Contact details and message text are not sent to the assistant model, application analytics or shared help-content review. Email notification routing stays on the server. Cloudflare may process a message when a configured notification is sent.
Hosted booking
The booking links on this site continue to Zenbooker, where you provide the address and booking details requested for your service. Zenbooker controls its catalog, service area, availability, displayed price and appointment record. A displayed time is not held until Zenbooker confirms the appointment. The booking form and its contact details are submitted to Zenbooker; this site does not receive the full hosted form or import all Zenbooker customer history.
With a current verified Google customer session, a fresh booking page can show your name and email prefilled. Blank, untouched name and email fields on the Contact and preferred-date inquiry forms may also be prefilled; edits, clears and browser autofill are preserved, and a profile email is never used as a phone number. This uses the existing session, requires no separate sign-in for each form or Analytics grant, and does not submit a booking or inquiry. The per-field prefill state stays in page memory and is not added to browser storage, URLs, analytics or assistant inputs. If you submit a form, its normal data handling described above applies. The app verifies the Google identity using sign-in scopes only; this does not link an email to a local appointment, grant administrator access, or authorize Google Business actions. The verified subject and encrypted name/email are kept in a separate local session for no more than one hour or until the Google identity token expires, whichever is earlier. Google access and refresh tokens are not retained. Clearing booking details stops automatic prefill for that booking link; signing out separately revokes the local customer session and its profile access. Neither action signs you out of Google or revokes a Google grant. Expired local rows may remain until a later bounded support-maintenance cleanup run, so no fixed physical-deletion deadline is promised. If the hosted page loads with prefilled fields, Zenbooker receives them under its own privacy practices. Guest booking remains available without sign-in.
A separate owner-configured reporting connection may receive limited event identifiers such as account, webhook and job IDs. Setup samples and unverified events are excluded from reported booking counts. This connection does not receive or store the hosted form's contact fields. Reporting availability and provider status are not guaranteed by this website.
Earlier appointments created through a previous local booking flow, if any, remain separate from appointments made on the hosted Zenbooker page. Local account access does not import hosted appointment history and does not replace the provider's confirmation or management instructions. This site does not provide SMS booking or sign-in codes in the current hosted flow.
Visitor support chat
The optional support chat does not require a Google or customer account and cannot view customer contacts or appointment records. A random browser session is used to keep your conversation. Redacted chat messages and replies are available for up to 24 hours; expired text is cleared when a later chat or owner content review runs, so this is not a fixed deletion deadline. Deleting a conversation removes its local messages and feedback; forgetting the session also clears saved preferences and closes that session. Preferences are not remembered unless you choose to save them, and saved preferences expire within 30 days. Up/Down recall is limited to confirmed text in the current conversation; photos are not recalled, and this control does not add a separate history store.
If the assistant is separately configured and enabled, it may process your redacted question, recent redacted conversation, saved preferences you chose to keep, and relevant approved public help information through the site's Cloudflare AI service to prepare a reply. If the assistant is unavailable, the chat provides basic help. It does not create, change or cancel an appointment.
If optional photo assistance is enabled, you may attach one JPEG or PNG image per message, up to 5 MiB and 16 megapixels. The image is normalized to a metadata-stripped WebP no larger than 1,280 pixels on either edge or 1 MiB before private storage; the original upload and filename are not retained. A normalized image may be processed by Cloudflare image and AI services to describe visible equipment. This is not a diagnosis, safety assessment, or repair procedure. Photo access is limited to 24 hours; deletion or expiry immediately blocks app access and invalidates photo-derived replies, while physical object cleanup is retried later and may take longer. Photo content and photo-derived replies are excluded from analytics and public-help curation. If camera capture is available, choosing Take photo opens a video-only preview in the browser; nothing uploads until you choose Use photo. Canceling, closing or hiding the help dialog, or leaving the page stops the preview. Upload photo remains an alternative.
You may submit a simple rating and a fixed reason for a completed reply. Feedback is available for up to 24 hours and expired feedback is cleared when a later chat or owner content review runs; this is not a fixed deletion deadline. If an authorized administrator later requests a help-content review, a limited set of redacted questions, replies and feedback may be sent to the configured AI service to prepare a draft. A person must review and approve any public help change; feedback does not publish content automatically.
The application's own analytics events do not include chat text, replies, preferences or feedback. The owner controls any remotely configured tag-container behavior, which may collect additional page data; see Optional measurement below.
Account and data controls
Choosing “Sign in to keep this visit” can associate the current visit with the verified Google subject. The app records only fixed activity metadata: a current app offering selection, opening the booking panel, or starting a help thread. It does not import earlier chats, photos, appointments or hosted booking records, and it does not link records by email. Anonymous visit metadata expires within two hours and after 30 minutes without activity; at most 50 events are accepted per visit. When saved to an app account, current-visit metadata and explicitly remembered answer-length/service-interest preferences expire within 30 days. The app account stores a pseudonymous subject key, not Google name or email. Identity and activity metadata are excluded from the app's analytics payloads and assistant prompts. If you explicitly choose to remember support preferences, only the selected answer-length and service-interest values may guide a support reply; those preferences personalize support but do not identify your account. Owner-managed tags are separate and may collect additional page data as described below.
Eligible customers can export or forget their local app-account preferences and activity. Forgetting removes those preferences and activity but retains a minimal revision fence to prevent stale requests from restoring erased records. This does not sign you out of Google, revoke an upstream Google grant, cancel an appointment, or delete Zenbooker records. Logging out revokes the local customer session separately. Google name/email remain in the separate encrypted prefill session described above and are cleared when that session is revoked. When account sign-in is offered from an existing help conversation, its current unsent question and a still-current approved service choice may be kept in this browser tab for up to ten minutes; photos and hosted booking form fields are not saved, and an already-open Zenbooker form may not preserve its progress. Administrators have bounded workspace export, correction, contact erasure, trash/undo and permanent erasure controls. Local deletion may leave noncontact audit or experiment evidence. Saved retention policies are applied manually in bounded batches; no recurring cleanup is activated by saving a policy.
Optional measurement
After Zenbooker confirms a job, the app records a minimal operational count of provider-confirmed bookings. This is separate from a preferred-date request and does not represent a payment, collected revenue or ROI.
Analytics and Experiments are separate optional choices and start off. A signed choice may remain active for up to 30 days. Analytics sends controlled events only after consent. In a version with first-party element measurement, it records only fixed registered element views and actions: a view requires at least half the element to remain visible for one second while the page is visible. The event may include the site's canonical page location and fixed element/source metadata; query strings, fragments and referrers are omitted. It does not collect page text, form values, account identity, chat or photo content. Each document and element is counted once; an action does not create a view. Measurement documents expire after 30 minutes, and aggregate event records are retained for up to 30 days. Withdrawal stops further eligible collection; bounded cleanup may continue afterward, while grant revisions immediately exclude withdrawn data. With Analytics consent, a hosted booking link may include a random utm_content reference. The app stores only its hash and consent revision; the association becomes unusable after seven days or earlier consent expiry. An expired hash may remain locally, but it no longer authorizes use; withdrawing Analytics removes its associated local references. An eligible current experiment exposure may be associated separately. An existing utm_content value is left unchanged, and the app cannot recall a link already sent to Zenbooker. The reference records a handoff only: a Zenbooker receipt or click-to-booking join has not been verified, and it does not confirm an appointment. With experiment consent, a pseudonymous subject may be used to record served exposures, eligible preferred-date request attribution and section feedback. The separate provider-reported booking count is operational and is not gated by experiment consent; it is not joined to a person or experiment. These records do not prove attention, causality, payment, revenue or a statistical winner. Contact details, addresses, OTPs and account identities are excluded from analytics payloads.
Withdrawal stops future eligible measurement but does not remove information already received by Google or erase completed aggregate evidence. GTM tags are controlled remotely by the owner; the app's local event allowlist cannot constrain a tag configured to collect additional page data. Admin and credential routes exclude analytics, and public analytics is suppressed while an admin session is present.
Customer reviews
In a published version where the owner enables the review display, the public home page may load review content from Trustindex inside an isolated frame, independently of the optional Analytics choice. The site passes public widget identifiers and may show a configured "Read customer reviews" link; it does not pass account identity, booking details or chat content to the widget. Trustindex and resources loaded by its frame may make requests or use browser storage under their own practices. Browser network, storage and rendering behavior have not been independently verified.
Administration and connected providers
Administration is available only through the restricted Admin console and requires Site identity plus a Google identity with an allowed verified email. Customer email verification does not grant administrator access. Google Business Profile, GA4, Search Console, Cloudflare AI, Vectorize, Zenbooker and Cloudflare Email are separate services with separate configuration and permissions. A saved credential does not prove a provider connection or activate a feature. Do not treat a model response or local status as provider confirmation.
Optional AI and application memory are restricted to approved public copy, numeric evidence and scoped administrator context. Customer contacts, appointment details, secrets and Google identities must not be placed in model prompts or shared curation. Local erasure does not imply deletion from an external service.
Hosting and limits
This Site uses its configured hosting platform and D1 storage. No particular data-residency location, legal certification, Google endorsement or guaranteed provider availability is claimed. The live business website has its own privacy and service terms. This notice covers this website; policies at other destinations apply separately.