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

Privacy Policy

Review draft describing confirmed GableGlim product data flows and unresolved privacy details.

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

Draft status and responsible entity

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

[OWNER/COUNSEL: identify the legal entity that determines the purposes and means of processing, its address, the jurisdictions covered, and whether GableGlim acts as a controller, processor, service provider, or in another role for each data flow.]

Information and sources currently confirmed

The checked-out product currently processes the following categories through the described features. [OWNER/COUNSEL: confirm the exact personal-data categories, whether this list is exhaustive, and the source of each category for every feature.]

  • Contractor account name, email, authentication account data, business profile details including business name, supported trade or trades, and service area, saved FAQs, and contractor-defined qualification criteria.
  • Homeowner service-request name, email, optional phone, property address, requested work, timing or notes when present, other form answers, and a validated contractor-profile routing identifier when supplied.
  • A homeowner’s FAQ question and recent conversation context, together with selected content from the contractor’s saved FAQs, sent to the AI proxy to support an answer.
  • Homeowner form answers and contractor-configured qualification criteria processed by the AI proxy for lead qualification, plus the resulting assessment stored with the lead.
  • Service-request and appointment records, including app-generated reference, form snapshot and version, received time, status and history, selected appointment time, and associated FAQ transcript where present.
  • Lead destination settings, including the configured HTTPS URL and authorization settings, plus app-side delivery attempt status.
  • For a qualified lead with a configured destination: the lead contact, submitted answers, reference, form details, and qualification result sent to that destination, plus an app-side delivery status record.
  • For a new service request, an email notification containing its reference, form title, contact details, and submitted form answers is attempted through the email service to the configured company notification inbox; delivery is not guaranteed.
  • An attempted booking-confirmation email using booking and contact details; the attempt does not guarantee delivery.
  • The contractor account email and account reference used with subscription-status checks and, if legally enabled later, hosted membership checkout.
  • Meta Pixel events emitted by the app: PageView, Lead after successful signup, and Purchase after payment confirmation with value and currency.
  • When the deployment injects the Polsia analytics slug, a Polsia visitor beacon can use a visitor identifier stored in browser local storage.

Purposes reflected in the product

The confirmed product purposes are to maintain contractor account and setup configuration; receive and retain website service requests; provide saved-FAQ answer support using the question, recent context, and selected saved-FAQ content; evaluate homeowner answers against contractor-configured lead qualification criteria; conditionally deliver qualified leads to a configured destination; show authorized records in the authenticated lead inbox; attempt an email notification to the configured company inbox for a new request and a booking confirmation after a successful booking; measure site and account events through the configured analytics integrations; and check the contractor’s subscription status. The hosted checkout integration is present but currently blocked while the legal documents remain drafts.

[OWNER/COUNSEL: confirm the complete purpose inventory and determine the lawful basis or other required justification for each purpose in each applicable jurisdiction. This draft does not select a legal basis.]

AI processing and sharing

For FAQ answer support, the question, recent conversation context, and selected saved-FAQ content are sent to the AI proxy. For lead qualification, the homeowner’s form answers and the contractor’s configured criteria are processed by the AI proxy. A qualified lead may be sent to a configured HTTPS destination with contact information, answers, reference, form details, and qualification result. The account email and reference are used with subscription-status checks; their use in hosted membership checkout is part of an integration that remains blocked while the legal documents are drafts. New requests are stored in the app’s intake records and appear in the authenticated lead inbox according to validated contractor-profile routing; the configured owner admin account can administer the default request scope. For a new request, the email service receives its reference, form title, contact details, and submitted form answers for attempted delivery to the configured company notification inbox. After a successful booking, the email service is also used to attempt a booking confirmation. Meta Pixel receives the app’s PageView, successful-signup Lead, and verified-payment Purchase events; the Purchase event includes value and currency. If the deployment injects the Polsia analytics slug, the Polsia visitor beacon can send its locally stored visitor identifier.

[OWNER/COUNSEL: identify each provider, recipient, its legal role and subprocessor relationships, the data it receives, its permitted uses and retention, and any other disclosures. Confirm the intended lead-inbox access and notification-recipient model, the configured company inbox, the CRM destination and its role, the production analytics settings, and provider-side collection. Do not infer provider retention, model-training practices, or data-location practices from this draft.]

Transfers and security

[OWNER/COUNSEL: confirm storage and processing locations, international transfer mechanisms, technical and organizational security measures, incident handling, and any security statements that can be substantiated. No location, transfer safeguard, or security certification is asserted here.]

Retention and deletion

[OWNER/COUNSEL: set retention periods or criteria for contractor accounts, profile and FAQ configuration, qualification criteria and assessments, homeowner requests, FAQ conversations, appointment records, CRM destination settings and delivery records, email notifications and provider mail logs, analytics identifiers and events, and billing references. Explain deletion, backup expiration, legal retention, provider-side retention, and account-closure behavior. No retention period is established in this draft.]

Individual rights and requests

[OWNER/COUNSEL: identify the rights available to contractors and website visitors by jurisdiction, any verification process, response timelines, appeals or complaints, and how requests are routed between GableGlim and a contractor. No rights process is finalized here.]

Privacy contact and changes

The company inbox supplied for this task is gableglim@polsia.app.

[OWNER/COUNSEL: confirm whether this inbox is authorized for privacy requests and legal notices; otherwise provide the designated privacy contact and address. Confirm how policy changes will be announced and when they take effect.]