Section01 路 Acceptance
Acceptance
By using the Dirty Laundry Co. public site, you agree to use it for lawful service inquiries, booking starts, quote requests, and support contact. The public site starts service requests and does not create a completed paid order by itself. A completed order requires the required customer app and backend steps, including email verification, card setup, payment authorization, and operational confirmation.
These terms apply to the public website, including service pages, pricing pages, quote forms, booking shell, contact form, blog shell, policy pages, and accessibility statement. If a later customer app or admin surface has its own terms, those terms may apply to that surface as well. If these terms conflict with a customer-facing policy page, the more specific policy usually controls for that topic.
Do not use the site to send unlawful content, abuse the service, test security controls without permission, upload unrelated files, impersonate someone else, or interfere with another visitor. The operator may refuse, pause, or close a request that appears unsafe, fraudulent, outside the service area, or outside the service scope.
Back to policy mapSection02 路 Account
Account
Guest quote submission is allowed. A visitor can request a dry cleaning, bedding, commercial, or Airbnb laundry quote without creating an account, verifying an email address, or adding a payment card first. The quote path exists so custom work can be reviewed before a price or service commitment is promised.
Guest booking can start on the public site, but final confirmation requires email verification and card setup in the customer app. The booking flow creates a draft and hands the customer to the app path. A draft does not reserve capacity forever and does not guarantee a pickup window until the confirmation step is complete.
Customers are responsible for giving accurate contact, address, item, and pickup details. Do not share another person鈥檚 contact information without permission. If a request is for a household, office, rental unit, or business location, the person submitting it must have authority to request pickup service at that address.
Back to policy mapSection03 路 Service Availability
Service Availability
Dirty Laundry Co. serves Ottawa at launch. Service availability depends on address, daily capacity, pickup windows, item eligibility, weather, building access, and operational confirmation. The public site may explain the planned service area, but the final operational check happens in the booking and order systems.
Flat pricing applies across served Ottawa postal-code prefixes at launch. The public site should not imply zone-based pricing or marketplace coverage. If an address is not supported, the operator may decline the request or place the postal code on a waitlist. Neighbourhood pages are not part of this public-site spec unless a later content task opens them.
Same-day delivery is a target for eligible standard laundry when pickup happens before the daily cutoff and capacity allows. It is not a guarantee for every order, custom item, commercial request, weather event, building access issue, or backend incident. The service policy gives more customer-facing detail about pickup windows, turnaround, and item eligibility.
Back to policy mapSection04 路 Pricing and Payment
Pricing and Payment
Standard laundry prices are shown on the public site from pricing fixtures. Those fixtures allow customers to compare fixed bag and per-pound options before starting a booking. Exact production numbers remain governed by the pricing module in the later admin and backend work, so public-site copy must avoid hardcoded dollar amounts outside the approved pricing fixture.
Quote-first work is reviewed before a final price is offered. Dry cleaning, comforters, commercial laundry, and Airbnb laundry may start from a public anchor, but the final quote depends on item type, size, condition, volume, frequency, timing, and handling notes. A customer does not owe a quote-service charge until a quote is accepted through the later flow.
Payment timing follows the product rules for the service. One-time fixed bag orders charge at booking confirmation. Recurring fixed bag orders charge when the pickup order is generated. Per-pound orders authorize before pickup and capture after weigh-in, subject to the cap and email-confirmation rule. No automatic payment retry is part of MVP.
Back to policy mapSection05 路 Cancellations
Cancellations
Cancellation handling depends on order type, timing, pickup state, and whether custom work has been reviewed. The refund and cancellation policy gives the customer-facing detail. As a simple rule, earlier cancellation is easier to handle than cancellation after a pickup has been assigned, items have been collected, or custom review has begun.
If a customer cannot be reached, the pickup location is inaccessible, the address is outside service, or the request includes unsupported items, the operator may pause or cancel the request. The operator may also ask for clarification before accepting the work. A paused request is not a penalty; it is a way to keep the service practical and avoid unclear obligations.
Recurring pickup is not a prepaid subscription in MVP. It is a rhythm for generating pickup orders, and each generated pickup follows the payment model in steering. If a recurring payment fails or the customer pauses service, the next pickup should pause until the issue is resolved.
Back to policy mapSection06 路 Liability
Liability
The public site is provided for service information and request intake. Dirty Laundry Co. is not liable for interruptions, browser storage loss, or incorrect customer-provided information. The site may change as service operations, customer app, admin console, email templates, and deploy settings evolve.
Laundry service involves real items, addresses, timing, and customer expectations. Production liability rules for damaged or lost items will be handled through the service policy, support process, operating procedures, and any required legal review before production cutover. The public-site terms do not promise a broader remedy than the final production policy provides.
To the extent allowed by law, Dirty Laundry Co. is not responsible for indirect, incidental, special, punitive, or consequential losses from use of the public site. Nothing in these terms limits rights that cannot legally be limited under Ontario or Canadian law.
Back to policy mapSection07 路 Governing Law (Ontario)
Governing Law (Ontario)
These terms are intended for an Ontario service context and are interpreted under the laws of Ontario and applicable Canadian law. The service is Ottawa-first at launch, and the public site is written for customers in that local operating context.
If a dispute cannot be resolved through support, the parties should first try to resolve it in a practical way before taking formal steps. The small-operator nature of the service does not remove customer rights, but it does mean communication should be direct, specific, and tied to the relevant booking, quote, or policy issue.
Back to policy mapSection08 路 Changes
Changes
Dirty Laundry Co. may update these terms as legal review, implementation, and operating procedures are finalized. Updates may be needed when payment capture, quote acceptance, account login, email delivery, support workflows, file uploads, or deploy settings change.
When the terms are updated, the last-updated date should change. Material changes should be clear enough for a customer to understand what moved. The project should not hide important changes inside vague wording or policy text that contradicts steering.
Back to policy mapSection09 路 Contact
Contact
Questions about these terms can be sent through the contact page. Support response target is within 48 business hours. A useful message includes the page, service, booking or quote context if one exists, and the specific term or policy question.
Do not send passwords, card numbers, government documents, or unrelated sensitive information through the contact form. If the operator needs more detail, the operator will explain what to send next and how it should be sent.
Back to policy map