Skip to content
The Lionsgate GroupConstruction & property operationsTalk to us
The Lionsgate Group · BUILDiQ · FIXiQ

Privacy Policy

Last updated July 25, 2026.

We collect and use client-provided information only to deliver our services, support project and property operations, manage communications, organize documentation, and improve client workflows. Client records, project documents, property information, communications, and operational data are treated as confidential business information. We do not sell client or visitor data.

What we collect

Client records may include documents, communications, photos, reports, contact information, issue history, property information, project records, and operational notes — provided by clients, their representatives, or generated in the course of an engagement.

Public website analytics

When someone views our public website, the browser sends our same-origin visitor endpoint only the normalized page path, referrer origin used to derive a fixed source category, allowlisted campaign values, coarse device class, browser automation flag, and the bounded engagement/action signals described below. Cloudflare also supplies approximate city, region, country, and optionally bounded ASN and organization context. Referrer origins and arbitrary query values are not written to the ledger.

To distinguish a new browser from a returning browser, your browser stores a first-party cookie named __Host-lg_visit_v1. The cookie contains random anonymous browser and session identifiers, first- and last-seen times, current-session activity times, visit and page-view counters, bounded per-route/section/signal/action state, and bounded alert-deduplication state. Our server signs this state with a keyed cryptographic signature so altered values are rejected. The cookie is Secure, HttpOnly, host-only, restricted to this site with SameSite=Lax, and unavailable to website JavaScript.

Lionsgate may separately enroll an authorized owner browser for internal traffic attribution. Enrollment sets a signed, first-party cookie named __Host-lg_internal_owner_v1 with only a fixed internal-owner value, the fixed label “Tyler browser,” a format version, and an expiry. It is Secure, HttpOnly, host-only, SameSite=Lax, and unavailable to website JavaScript. Controlled Lionsgate automation may instead authenticate each test request with a dedicated secret header. Neither mechanism identifies unmarked public traffic.

  • The visitor-alert implementation does not read or store the source IP address, exact GPS or street-level location, a browser fingerprint, an advertising identifier, or a person's name.
  • The signed cookie expires no later than one year after the latest accepted page view. Clearing this site's cookies removes the anonymous identifier and counters, so a later visit appears as a new browser.
  • A new anonymous session starts after 30 minutes of inactivity. Same-page refreshes within 15 seconds and static-file requests are suppressed. Likely automation is retained as a bounded classification for aggregate verification but does not generate routine prospect-style alerts.
  • Accepted events are classified server-side as internal, probable automation, low signal, engaged, high intent, or conversion using separate human-confidence and intent scores with bounded reason codes. These are evidence summaries, not identity certification. Public-unclassified does not mean a verified person, prospect, unique human, or confirmed lead.
  • The site measures only bounded page, 30-second active-visible-time, 50/90-percent scroll, curated section dwell, and explicitly tagged CTA, phone, download, contact, and showing actions. It does not collect keystrokes, form contents, mouse traces, arbitrary link labels, or arbitrary query strings.
  • Telegram may receive a concise alert only for the first useful external browser event, a first engaged/high-intent/conversion threshold transition, or a first allowlisted high-value action. Routine Tyler/Avery internal activity, probable automation, refreshes, and repeated signals are suppressed.
  • Accepted, nonduplicate events are kept in a dedicated server-side anonymous ledger for up to 90 days. Records are limited to random browser/session/event IDs, UTC time, normalized path, bounded event/action/milestone/section values, traffic class, approximate city/region/country, coarse device and ASN/organization context, fixed referrer category, allowlisted campaign values, anonymous counters, scores/reasons, classification, and alert disposition.
  • The anonymous event ledger does not contain a raw or hashed source IP address, exact coordinates, a browser fingerprint, names, arbitrary internal labels, full referrer URLs, arbitrary campaign/query values, either internal authentication secret, either cookie value, contact-form content, Telegram credentials, or cookie-signing secrets.

How it is used

Client information is used to deliver the services engaged: project oversight and reporting (BUILDiQ) and maintenance operations, issue tracking, and building records (FIXiQ). Project and property records are treated as confidential business information belonging to the engagement.

How it is stored and accessed

  • Data may be stored in privately managed systems and proprietary databases designed for project- and property-specific records.
  • Access is limited to authorized users and service personnel.
  • Records are organized per client and per property or project — not pooled into public systems.

Data privacy in practice

  • Portal access should be scoped by role, property, project, and client audience.
  • Sensitive information should only be uploaded when it is needed for the engagement.
  • Resident, legal, insurance, dispute, claim, financial, and confidential records should be clearly identified so access can be limited appropriately.
  • Operational summaries, AI-assisted drafts, retrieval results, and reports should be checked against source records before being used for decisions.
  • Client information is not sold as advertising data or data-broker records.

Automation and AI-assisted workflows

BUILDiQ and FIXiQ may use automation to support intake, retrieval, drafting, summaries, routing, and operational review. These tools are intended to assist authorized users. They do not replace professional judgment, and they should not be used as the sole source for legal, engineering, insurance, accounting, regulatory, or construction decisions.

Retention and correction

Records are kept as needed for the applicable engagement, operational continuity, audit history, and legal or business requirements. Clients may ask Lionsgate to review access, correct inaccurate information, or clarify how a record is being used in the service.

Your questions

Clients and public website visitors may request clarification, access, correction, or deletion where information can reasonably be identified — reach our concierge at thelionsgategroup.ca or call 780-800-0050 or 825-360-1090.