Privacy Policy

Information we collect

Customers may provide a name, email address, optional telephone number, general neighbourhood, vehicle details, requested service, desired timeframe, photos, messages and appointment information. A confirmed booking can include a privately shared service address.

Detailers provide account identity, business contact information, service coverage, descriptions, pricing information and portfolio photos. A DetailLink account stores your email address and a salted hash of your password, never the password itself. A secure cookie keeps you signed in. Account emails, such as confirmation and password reset messages, are sent through our email provider, Resend. If you turn on email updates, Resend also handles short notices containing a title and a link, and reports whether they were delivered. Guests get one email to confirm their address first; that link does not open their request. We keep a hashed record of addresses that bounced, complained or unsubscribed so we stop emailing them. You can stop email updates at any time.

Independent detailers may optionally submit a separate founding-pilot interest application with their business name, contact name, email, optional phone and public business link, work style, service area, selected services and notes. It is not an account or public listing. The application records consent and an optional outreach campaign tag.

If you file an in-app report, we store the case category, your description, supplied contact details, linked booking if any, case messages, status changes and administrative investigation notes. Quote change proposals and customer responses are retained with the booking.

If monitored privacy intake is active and you submit a personal-information request, we store the request type, supplied contact details, description, private case messages and staff review history, including an attestation of any independent identity check. The platform also stores an admin-only incident register for documenting privacy and security events.

We also record limited first-party activity events, such as quote-flow milestones, and operational records needed to manage quotes, bookings, notifications and moderation. Notification preference records are scoped to a signed-in account or an individual guest request, and delivery records describe in-app availability or withheld email—not proof the person read a message. When a signed-in detailer uses the lead dashboard, we record the first time an eligible lead card remains on-screen and whether they explicitly open it to prepare a quote. These records contain the detailer account and request identifiers and event times, not browsing history across other websites.

For quote requests submitted after the acquisition reporting update, we may store a coarse first-observed browser-session source (for example organic search, social or direct), recognized source, sanitized campaign tag and landing-page category. This attribution is kept with the request to evaluate which marketing sources produce submitted requests and bookings. The raw referrer URL, its path and query, and a cross-session visitor identifier are not collected for this feature. Older requests remain unattributed.

Why we use information

• Create, display and manage customer quote requests and detailer offers.
• Match open requests with participating businesses by services and work location.
• Coordinate bookings, private messages, in-app notifications and completed-job reviews.
• Operate business profiles, prevent abuse, support moderation and diagnose reliability problems.
• Review founding-detailer applications and contact consenting applicants manually about pilot participation, only while an administrator has confirmed that this recruitment queue is being monitored.
• Understand aggregate use of the marketplace, evaluate lead response times and help businesses and administrators identify unanswered requests.
• Compare request-source and booking outcomes and measure repeat usage of authenticated customer accounts. Guest submissions are not merged by matching contact details.

Who can see your information

Approved, active, eligible detailers may view relevant request descriptions, broad service districts and customer-uploaded vehicle photos for quoting. Customer contact email, name and phone are not shown in the general lead feed; contact details and addresses pasted into free-text notes are also filtered from the provider-facing view. This filtering cannot reliably find every sensitive detail, including items visible inside an image. Details needed for an accepted job may be available in authorized booking workflows.

Messages are scoped to the request and participating business. Customers can see their own information using their account or private guest key. Support case details are accessible using the case access code or the original signed-in reporter account. Only updates explicitly marked for the reporter are shown outside administration. Authorized administrators can inspect case records, including linked booking evidence, for moderation and platform operations.

Privacy case details are available to the submitting signed-in account or someone with its private access code. That code allows case follow-up but does not independently establish identity for release or alteration of personal records. Identity checks and internal privacy case notes are visible only to configured administrators.

Founding-detailer application contact details and internal follow-up notes are visible only to configured marketplace administrators. They do not appear in the public directory, and submitting an application does not authorize a seller account.

Detailer lead-view records support internal marketplace response reporting and individual business inspection by authorized administrators. They are not published as customer contact lists or shared as a public business ranking.

Cloudflare provides database and private image storage infrastructure. Identity and other technical service providers may process information needed to deliver their respective services. We do not sell detailing payments or customer contact lists.

Storage, guest access and security

Marketplace records are stored through Cloudflare D1 and uploaded images in a private Cloudflare R2 bucket. New image uploads are stripped of embedded metadata on the server; authorized image reads also filter metadata from historical files without deleting the originals. The application uses role- and request-specific access checks, private response caching rules and upload size restrictions. No internet service can guarantee absolute security.

Guest request keys, support case access codes and privacy case access codes are held in the submitting browser, while hashes are stored server-side. A guest can reveal and save a quote-request recovery key and restore access from another device. A privacy requester should separately save their case link and its code. Anyone possessing a case code and link can read that case, so keep both private. Clearing browser data can remove access if the information was not saved. There is not yet an email recovery flow.

Retention and your choices

A private staffed-on-confirmation request intake and manual review ledger are available. A formal retention schedule, independently verified access and correction procedures, and deletion/export tooling are being prepared. No request automatically discloses, alters or deletes marketplace data.

You may have rights to request access to or correction of your personal information under applicable privacy law. Information cannot always be immediately removed where retention is lawfully required or necessary for a legitimate dispute or safety investigation.

Service providers and location of processing

The production review will document where each hosting, authentication, communications and other service provider processes personal information, including any processing outside Canada, and provide required contact and policy information.

Until that review is complete, do not assume all data stays in Canada.

Privacy contact

The responsible operator is Chromegreen Media Limited. A dedicated monitored privacy address and request channel have not yet been configured; no unverified contact address is published here. See the personal information requests page for the current status.

This notice will be updated after production data-flow verification and professional legal review.