Skip to content

Privacy review

Ottawa laundry privacy policy for Dirty Laundry Co. pickup customers.

This ottawa laundry privacy policy explains what Dirty Laundry Co. collects when you read service pages, start a booking draft, request a quote, or send a contact note. It covers laundry data handling Ottawa customers are most likely to ask about: pickup addresses, postal codes, quote photos, contact details, browser drafts, processors, retention, rights, and the privacy contact path. The policy is written for a single Ottawa operator, so information stays tied to service delivery, support, fraud prevention, and practical review rather than marketplace profiling.

  • Last updated May 9, 2026
  • Last reviewed May 12, 2026
  • Service area Ottawa
A closed notebook on a desk beside policy review notes
Last reviewed May 12, 2026

Policy map

What this privacy policy covers.

Use this numbered rail to jump through the ottawa laundry privacy policy before booking. The body sections stay stable so information collected, processors, retention, and rights can be reviewed without rereading the whole page.

Section01 路 Information Collected

Information Collected

Dirty Laundry Co. collects information that customers choose to provide when they use the public site, booking flow, quote form, or contact form. This can include name, email address, phone number, service selection, pickup address, postal code, item descriptions, quote notes, and photos attached to a quote request.

We also collect basic technical information that helps the site work, such as browser type, device size, page route, language preference, and error details when a frontend issue occurs. We do not ask for payment card numbers on the public site, and we do not collect account passwords in this surface. The public site is meant to explain the service and start a request, not to hold full account records.

Quote photos may show clothing, bedding, labels, room context, or other details a customer decides to include. Customers should avoid uploading government documents, payment cards, medical information, or anything unrelated to the laundry request. If a customer sends information that is not needed, the operator may ignore it, remove it from the request where possible, or ask for a cleaner version of the request.

Booking, quote, order, billing, and support records are stored only in the systems selected for the service. This policy is reviewed when those systems change so retention, processor, and access details stay aligned with the real implementation.

Back to policy map

Section02 路 How We Use It

How We Use It

Information is used to explain services, prepare booking or quote requests, respond to support questions, and improve the clarity of the public site. Standard laundry details help the later customer app continue the order flow. Quote details help the operator review custom work and respond within the published quote target.

We use contact details to reply to customers, clarify request details, and send service-related messages. We use address and postal-code details to check whether the requested pickup is inside the Ottawa service area. We use service selections, item notes, and photos to decide whether the request belongs in standard booking or needs a reviewed quote.

We do not sell personal information. We do not use information from the public site to create a marketplace profile or share customers with unrelated operators. The service is designed around one accountable operator serving Ottawa directly. Customer information is used for service delivery, support, safety, fraud prevention, legal compliance, and product improvement tied to this service.

Aggregated information may be used to understand which pages, services, and form steps need clearer wording. Aggregated reporting should not identify a specific customer. If analytics are added in the deploy phase, they must follow the project rule that no advertising tags are included in MVP unless a later approved task changes that scope.

Back to policy map

Section03 路 Cookies

Cookies

The public site may use essential browser storage to keep a booking draft, quote draft, or form state while the visitor completes the flow. These values can be cleared by the visitor through browser settings.

This storage is used to reduce repeated typing and to support the resume prompt in the booking flow. It is not a full account record. If the browser is shared, another person using the same browser profile may be able to see a saved draft until it is cleared. Customers should clear drafts on shared devices.

No advertising pixels are used in the MVP public site. If analytics or security tools are enabled, the service will document the active setting and update public policy wording where needed.

Customers can set their browser to block or delete cookies and site storage. Blocking essential storage may make the booking or quote shell less convenient, but it should not prevent a visitor from reading service pages, pricing pages, policy pages, FAQ content, or the accessibility statement.

Back to policy map

Section04 路 Third-Party Processors

Third-Party Processors

The public site may use Cloudflare Turnstile to help protect forms from automated abuse. Hosting, email, payment, and storage processors are limited to what is needed to provide the service.

When production processors are connected, only the information needed for the service will be shared with them. Hosting providers may process logs needed to serve pages and protect the service. Email providers may process names, email addresses, and message content needed to send service emails. Payment providers may process payment details in the customer app, not on the public site.

Secrets, storage keys, and payment credentials are never exposed to the public frontend. Quote photos and private upload files are planned to use signed access in later backend work, so the public site does not receive storage credentials. The customer should not email or upload payment card details through the quote or contact form.

Dirty Laundry Co. may also disclose information when required by law, to protect the service from abuse, to respond to a security incident, or to handle a customer dispute. Disclosure is limited to what is reasonably needed for the purpose.

Back to policy map

Section05 路 Retention

Retention

Browser drafts remain until the visitor clears them, starts over, or the browser removes them. Production retention periods for account, payment, quote, support, and file records will be finalized when the backend and policy review are complete.

Operational records will be kept only as long as needed for service delivery, legal obligations, dispute handling, tax records, security review, and support history. A quote request may need to stay available long enough for the seven-day quote validity period and any follow-up. An order record may need to stay available long enough to resolve service, billing, or damage questions.

When information is no longer needed, the operator will delete it, anonymize it, or keep it only where law or legitimate business needs require retention. Backup copies, logs, and security records may take longer to age out because they follow operational backup and incident-response procedures.

Browser-draft behaviour is not a promise that service records can be removed by clearing a browser. Customers should use the published contact path to request access, correction, or deletion of records held by the service.

Back to policy map

Section06 路 Rights

Rights

Customers may ask to access, correct, or delete personal information where the law allows. Some records may need to be retained for legal, accounting, security, or dispute reasons.

Requests should include enough detail for the operator to identify the relevant booking, quote, or support conversation without sharing more information than needed. A useful request may include the email address used, the approximate request date, the service involved, and whether the question is about a booking, quote, contact message, or policy issue.

The operator may need to verify the requester before sharing or changing information. Verification protects the customer from someone else trying to access an order, quote, address, or support record. If the request cannot be verified, the operator may ask for more information or decline to disclose details.

Customers may also ask questions about how information is used, object to certain uses where the law allows, or request a copy of information in a practical format. The response will explain what can be done, what cannot be done, and why.

Back to policy map

Section07 路 Contact DPO

Contact DPO

Privacy questions can be sent through the contact form or by email at hello@dirtylaundry.local. The operator will review the request and respond through the most appropriate contact path.

Dirty Laundry Co. is a small single-operator service, so the privacy contact is handled through the same service channel rather than a separate enterprise privacy office. The contact path is still treated seriously. Privacy questions are routed for review and answered clearly.

This policy is written for the public site and is reviewed when the information collected, processors used, storage location, retention period, or customer rights process changes.

Customers should not send sensitive documents, card numbers, passwords, or unrelated personal information through the contact form. If a sensitive issue needs discussion, send a brief note first and wait for the operator to confirm the safest next step.

Back to policy map

Privacy limits

What we do not do with laundry data.

  • We do not sell customer information.
  • We do not run advertising pixels in the MVP public site.
  • We do not share customers with unrelated marketplace operators.

Receipt ledger

Last reviewed and how to reach us about laundry data handling Ottawa.

The ottawa laundry privacy policy is reviewed when public-site forms, quote photos, processors, browser storage, or customer rights wording changes. If laundry data handling Ottawa details are unclear before you book, use the privacy contact link and include the page or section you are asking about.

Contact us about privacy

PRI-2026-05-09 Reviewed

Last updated May 9, 2026

The policy text reflects the current public-site intake surface and booking shell.

Last reviewed May 12, 2026

Review dates move when laundry data handling Ottawa rules, processors, or forms change.

Ad pixels 0

The MVP public site does not use advertising pixels or marketplace profiling.

Processor scope Limited

Hosting, email, payment, storage, and protection tools stay tied to service delivery.

Policy map 7 sections

The body stays split into stable review sections for scanning and direct links.

Popular searches

Related Ottawa laundry privacy searches.

These internal links collect the common ottawa laundry privacy policy and laundry data handling Ottawa questions around quote photos, booking drafts, service terms, accessibility, refunds, and the contact path.

Next step

Ready to book, or need something clarified first?

If the privacy policy answers your laundry data handling Ottawa question, you can book standard wash and fold or request quote review for custom items. If something still feels unclear, contact Dirty Laundry Co. first with the policy section, service, and request context so the answer stays specific.

A smartphone, notepad, and pen ready for a policy question
Privacy note ready Use the contact path when laundry data handling Ottawa needs review before booking.