Data and trust

Privacy Policy

Privacy guidance for Exquisite Windows & More quote requests, contact forms, photos, measurements, analytics, WhatsApp follow-up, and future costing-app integration.

Current public reference

This privacy page explains how quote intake, customer follow-up, uploaded project media, analytics, and future costing-app handoff should be handled. Final legal and business review should approve the wording before launch.

Quick facts

  • Data collected: Contact, project, photos, measurements - Only collect what helps staff respond, quote, support, or plan the project.
  • Primary use: Quotes and customer service - Information should support staff review, follow-up, project records, and support questions.
  • Future bridge: Costing app handoff - The future API should create customer and estimate records without exposing unnecessary internal data.
  • Customer control: Ask, correct, or request removal - Customers should have a clear contact path for privacy questions or corrections.

Privacy needs to match the real quote flow

The website asks customers to share practical project details: name, phone, email, WhatsApp contact, parish or site location, product interest, measurements, notes, photos, drawings, and builder/cart configurations. The privacy page should explain why those details are collected and how they support staff-reviewed quotes.

Photos and measurements are project records

Uploaded photos, drawings, and measurements may show rooms, openings, addresses, fixtures, construction conditions, or other site details. They should be handled as project records, used for quoting and support, and carried into future systems only when needed.

The future API bridge needs privacy boundaries

When the website connects to the costing application, the bridge should pass structured lead and quote details with clear purpose: creating or matching customer records, creating estimate records, preserving referral context, and helping staff follow up. The website should not expose internal costing details back to public pages.

Analytics should help improve the site without overcollection

Analytics can help identify which products, gallery pages, and quote flows are useful, but tracking should be documented and kept proportionate. Any advertising, remarketing, or advanced tracking should be reviewed before launch.

Privacy Policy Scope

  • Name, phone, email, WhatsApp, and preferred contact method
  • Site location, parish, address notes, room names, and project notes
  • Product interests, builder/cart configurations, measurements, sketches, and drawings
  • Uploaded photos and files showing openings, rooms, products, and site conditions
  • Referral URL, campaign details, analytics events, and device/browser information where used
  • Staff follow-up, quote preparation, customer service, support review, and project records
  • Future costing-app/customer-record/estimate handoff
  • Correction, deletion, retention, and privacy-question process

Privacy Topics Covered

This structure is meant to be customer-readable and useful for the future API bridge. Final legal wording should be reviewed before launch.

Quote and Contact Information

The quote flow should collect only the contact details needed for staff to respond and prepare the next step.

  • Name, phone, WhatsApp, email, and preferred contact method help staff follow up.
  • Site location, parish, and access notes help with measurement, delivery, and installation planning.
  • Product categories, measurements, and notes help staff understand the request before quoting.
  • Customers should avoid sending unrelated personal documents unless staff specifically requests them.

Photos, Drawings, and Measurements

Project media can be very helpful, but it may also reveal private home or site details.

  • Photos may show rooms, addresses, fixtures, site conditions, or unfinished construction.
  • Drawings and sketches may include dimensions, layouts, contractor notes, or product requirements.
  • Uploaded files should be used for quote review, support review, project planning, and staff communication.
  • Public gallery or case-study use should require a separate business decision and should not be assumed from a quote upload.

Website Analytics and Referral Context

Analytics can improve SEO and conversion when it stays clear and proportionate.

  • The site may record page visits, referral URLs, campaign details, form events, and broad device/browser context.
  • Analytics should help identify which product pages, gallery items, and quote flows are useful.
  • Advertising or remarketing tags should be documented before launch if used.
  • Customers should not need analytics tracking for staff to respond to a direct inquiry.

WhatsApp, Email, Phone, and Staff Follow-Up

Customers may contact Exquisite through multiple channels, so the privacy page should acknowledge real-world follow-up paths.

  • A website quote request may lead to WhatsApp, email, phone, or in-person follow-up.
  • Staff may need to reference the submitted photos, measurements, reference page, or builder configuration during follow-up.
  • Customers should be able to ask which information is needed before sending more details.
  • Sensitive payment or card details should not be requested through ordinary website forms.

Future Costing App and Customer Records

The future bridge should be designed around purpose-limited customer and estimate creation.

  • The website may later send customer details, project location, product interests, measurements, photos, notes, and referral context to the costing application.
  • The bridge should avoid duplicating customers when a match already exists.
  • Raw website payloads may be useful for audit, troubleshooting, and staff review.
  • Internal costing formulas, margins, and private business data should not be exposed to website visitors.

Retention, Corrections, and Deletion Requests

Customers should have a practical way to ask about their information after sending a quote request.

  • Customers should be able to request correction of contact details, project details, or uploaded information.
  • Deletion or retention requests may need staff review if the information is tied to quotes, invoices, warranties, support, or legal/accounting requirements.
  • The site should define a privacy contact path before launch.
  • Final retention periods should be approved before the API bridge goes live.

Before Sending Personal Or Project Data

These prompts help customers share useful quote information without oversharing unrelated personal details.

  • Send only the contact, location, measurement, photo, drawing, and project details needed for the quote or support request.
  • Remove unrelated people, documents, or private items from photos where practical before uploading.
  • Use WhatsApp, phone, or email if you prefer to ask staff what information is needed before sending files.
  • Do not send card numbers, passwords, bank login details, national IDs, or unrelated sensitive documents through ordinary website forms.
  • Ask staff if you want to correct a phone number, email address, project location, measurement, or submitted file.
  • Wait for the final privacy wording before using the website for large-scale or automated CRM/costing-app intake.

Related Trust Pages

Website terms
Understand the website, quote, builder, product-information, and approval boundaries.

Payment planning
Keep payment, receipt, tax, currency, and quote status fields staff-confirmed.

Project process
See how quote information, photos, measurements, and staff review move forward.

Start a quote carefully
Send only the project details needed for staff to understand your request.

What to prepare for a window quote

  • Width and height for each opening
  • Room name or location for each window
  • Preferred style such as slider, casement, awning, or fixed
  • Glass and frame color preference
  • Photos from inside and outside where possible

Common Questions

Why add privacy now?

It prevents the quote system and future costing-app bridge from being designed in a vacuum. The site should know what data it collects before intake becomes more advanced.

Is this final legal language?

No. This is website guidance for review. Final wording should be approved before launch.

What information does the quote flow need?

Usually name, contact details, site location or parish, product interest, measurements if available, photos or drawings where helpful, and notes about timing or access.

Will uploaded photos be used in the public gallery?

They should not be treated as public gallery content by default. Public case-study use should require a separate business decision and supported project details.

Can website data go into the future costing app?

Yes, after the bridge is designed. The purpose should be customer matching, estimate creation, staff follow-up, audit, and project recordkeeping.

Can customers ask for corrections or deletion?

Yes. The page should provide a practical contact path, while final retention and deletion rules should be approved before launch.