Website privacy
Privacy Policy
This development policy describes the intended handling of personal information collected through the service-request form. Before launch, the operating legal entity, privacy contact, processors, retention schedule and cross-border data flows must be inserted and reviewed for the laws that apply.
Privacy information for Toronto HVAC service requests, contact preferences, retention and customer rights.
Build a service requestInformation collected for a service request
The form may collect name, phone, optional email, postal code, property type, HVAC system, symptom, status, preferred timing, contact method, notes and consent choices. Server security records may retain limited technical information such as timestamp and a protected network identifier.
Do not submit government identifiers, financial details, medical information, alarm codes, lease documents or images containing unrelated personal material. The published form should collect only what is necessary to review and route HVAC service.
Why the information is used
Service-request data is intended to confirm geographic and equipment coverage, contact the requester, plan access, create a service record and meet legitimate security or legal obligations. It is not automatically used for marketing.
Operational text consent applies only when the customer selects text as a preferred contact method. Optional marketing consent is separate, unchecked and should be recorded with its wording and date.
Storage, disclosure and retention
Before launch, the operator must list hosting, email, CRM, analytics, call tracking and messaging providers, where they process data and the safeguards used. Access should be limited to people who need the information for service, administration, security or lawful requirements.
A documented retention schedule should remove rejected or completed inquiries when no longer necessary, subject to warranty, tax, dispute and legal needs. Backups and exported records must follow the same policy.
Access, correction and privacy contact
The final policy must name the privacy contact and explain how an individual can ask about access, correction, consent withdrawal or a privacy concern. Identity may need to be verified without collecting more information than necessary.
PIPEDA and other requirements may apply depending on the organization and data flow. This template is not legal advice and needs review for the operating company.