GableGlim membership

DRAFT — requires GableGlim owner approval and qualified counsel review for applicable jurisdictions

These review drafts are not finalized binding policies. They are not represented as legally sufficient or exhaustive and do not eliminate lawsuit risk.

GableGlim legal documents

AI and Communications Disclosure

Draft disclosure for GableGlim website FAQ support, service requests, and appointment communications.

Version
0.1.0-draft.2
Effective date
Not effective · draft dated September 30, 2026

Draft status

This is a review draft, not a finalized or binding disclosure. It is not represented as legally sufficient or exhaustive and does not eliminate lawsuit risk.

Website FAQ support

GableGlim provides a website FAQ helper for contractor websites. The helper uses FAQs saved by the contractor. For answer support, the homeowner’s question and recent conversation context, together with selected saved-FAQ content, are sent to the AI proxy. If saved content does not support a response, the product returns a fixed fallback instead of treating an unsupported answer as confirmed.

AI-generated answers can be incomplete, inaccurate, outdated, or unsuitable for a particular situation. The helper does not answer phone calls, and SMS is not available in the checked-out product.

Website service requests

Homeowners can submit service requests through website forms for roofing and lawn-care work. The forms collect contact details, property or service details, and form answers; submissions are stored and shown in the authenticated lead inbox according to validated profile routing, while the configured owner admin account can administer the default request scope. For a new request, the app attempts to email its reference, form title, contact details, and submitted form answers to the configured company notification inbox. Email delivery is not guaranteed.

Lead qualification and configured destinations

When qualification is enabled for an eligible contractor account, the product sends homeowner form answers and contractor-configured criteria to the AI proxy for an assessment, then stores the result with the lead. This feature evaluates those inputs and does not perform a separate verification against outside records.

If the result is qualified and an HTTPS destination is configured, the product can send the lead contact, submitted answers, reference, form details, and qualification result to that destination. The destination’s recipient, legal role, and provider practices are not established here, and delivery is not guaranteed.

Appointment choices and messages

Appointment choices are shown only when a contractor has configured availability. A booking confirmation email is attempted after a booking, but delivery is not guaranteed. SMS is unavailable, so the product does not send appointment confirmations by SMS.

Analytics and tracking

The app code initializes Meta Pixel and sends PageView events, a Lead event after successful account signup, and a Purchase event after payment confirmation with value and currency. When the deployment injects the Polsia analytics slug, a separate Polsia visitor beacon can use a visitor identifier stored in browser local storage.

[OWNER/COUNSEL: confirm whether Meta Pixel and Polsia analytics are intended to run in production, what notices, consent, or opt-out apply, what each provider collects and retains under its governing terms, and whether any additional tracking or communications are used. This draft does not establish provider-side practices.]

Human review and sensitive information

[OWNER/COUNSEL: confirm whether any person reviews questions, AI answers, lead qualification assessments, service requests, or bookings; if so, describe when and for what purpose. Set sensitive-data limits and visitor notices. Confirm any email, marketing, or other communications beyond the observed booking-confirmation attempt and the consent or notices that apply. Do not imply a human reviews every answer.]

AI provider and operational limits

[OWNER/COUNSEL: identify the AI provider and its data use, retention, model-training and deletion practices from the governing provider terms. Confirm other operational limits, service availability, support route, and incident handling. This draft makes no provider-retention, uptime, or support-time promise.]