Last updated:
Your privacy at a glance
Dwtees uses website data to operate WordPress and WooCommerce, protect the site and answer questions. There are no paid orders through the current preview. The owner has not supplied a marketing list or verified retention schedule, so we do not claim one here.
Information you choose to provide
If you email support, the message may include your name, email address, product title and any information you choose to share. Do not include passwords, complete payment card numbers, government identifiers or other unnecessary sensitive data. If ordering opens later, WooCommerce will need contact, address and order details to fulfill purchases; this policy will be updated with the actual payment and shipping providers first.
Technical data
Normal website operation can produce server and security records such as IP address, browser information, requested URL, time, referring page and error events. WordPress and WooCommerce may use essential cookies to keep a cart or signed-in session working. Cloudflare is visible as the public delivery layer and may process traffic to serve and protect the site. We will document active retention periods after the owner verifies hosting and service settings.
Why the information is used
Data can be needed to display pages, maintain a login, answer a support request, detect abuse and, once orders open, process a purchase, delivery, return or refund. We do not sell a customer’s support message as a product. We do not claim a newsletter or behavioural advertising program that has not been configured.
Sharing and payment
Hosting and security providers necessarily handle some traffic data to make the site available. A future payment provider will process payment details only after it is connected and shown at checkout. Dwtees’s server should not store a complete card number. The site currently has no active payment gateway; no one should send payment details to support by email.
Your choices and requests
You may request access to, correction of or deletion of personal information by contacting [email protected]. We will verify the request before disclosing account or order data. Some records may need to be retained for a valid legal or accounting purpose once sales begin. We will explain any limit rather than silently ignoring a request.
Children and changes
The current catalog is directed to adult shoppers. We do not knowingly ask children to submit personal information through the site. We may revise this policy when actual checkout, carriers or other services are connected; the updated date above will change, and the active version will be linked from the footer. See our Terms of Service and Contact Us page for related information.
Questions and support
Email [email protected] with the product or order number and a short explanation. Never include a password or full payment card number. You can also start at the Help Center, read the FAQs, or use the support ticket link.
Who this notice describes
This notice describes the information that can arise when someone visits Dwtees, contacts support, signs into a WordPress account or, after checkout is enabled, places an order. The catalog has active made-to-order products, but no payment gateway is active yet. The public contact route is [email protected]. The owner has not yet supplied a confirmed legal entity name and suite for a public business address; this page will be updated when those facts are available. A prospective print-on-demand provider named in a planning discussion is not automatically a recipient of customer data. Before a provider handles orders, Dwtees must confirm the integration, explain the data it receives and test the transfer.
Data given in a support message
An email to support may include your name, reply address, product link, question and any order reference you choose to include. If you report a damaged item later, you may also provide photographs of the garment, label or parcel. Please remove unrelated people, addresses and account information from images when they are not needed to solve the case. Do not send passwords, complete payment-card numbers, security codes or government identity documents for an ordinary shopping question. Support should use the information to answer the request, identify the affected order and document the resolution. A message about a concept does not subscribe you to marketing or authorize a payment.
Accounts and future order details
WordPress and WooCommerce can store account and order data when those features are used. A future paid order will need the recipient name, contact email, delivery address, selected product and size, price, tax and order status so the seller can fulfill it and help with later questions. An account may also hold login credentials in protected form and an order history. The site has no paid orders yet through its checkout. When checkout opens, Dwtees should verify the guest and account paths and identify what fields are required rather than collecting unrelated information. A customer should be able to inspect the final delivery address and amount before paying.
Technical records needed to run the site
A web request can create server, security and performance records including an IP address, requested URL, time, browser information, referral and error event. Those records help deliver a page, investigate an outage and defend against automated abuse. The public site is delivered through Cloudflare as well as the WordPress host, so traffic may pass through that service. We do not infer that every possible Cloudflare feature or cookie is active merely because the domain uses its network. The specific protection and retention settings should be reviewed by the owner. Technical records should not be repurposed into an invented marketing profile; any new analytics or advertising service needs a fresh disclosure.
Cookies and local browser storage
WordPress may use cookies to maintain a logged-in session, and WooCommerce may use essential cart or checkout cookies once shopping is active. Cloudflare may set cookies for security or challenge functions depending on the configuration and a visitor’s request. A cookie can help a site remember a session or distinguish ordinary traffic from automated requests, but its exact name and lifetime depend on the feature used. Dwtees should audit the live browser cookies before naming a precise list or retention period in this notice. If nonessential analytics or advertising cookies are added later, the store must explain and manage them as applicable. Clearing essential cookies may require a visitor to sign in again or lose an in-progress cart.
Why information is processed
Information is used to make the website load, maintain an account session, answer support questions, protect against abuse and, once orders open, accept payment and arrange delivery. An order record can also be needed to provide a return, exchange, refund or accounting record. The purpose should match the actual operation: a product question is not a reason to request a date of birth, and a tracking inquiry is not a reason to collect a card security code. Dwtees does not claim a newsletter or behavioural advertising program that has not been configured. If such a program is added, the notice and any consent or opt-out mechanism must be updated before the data is collected for that new purpose.
Payment information
The owner intends to connect PayPal later, but no gateway currently accepts payment on the site. A future connected provider may process payment details needed to authorize and refund a transaction. Dwtees’s WordPress server should not store a complete card number or security code. The precise provider, method and transfer need to be tested and described here before paid checkout opens. A receipt or order record may include a transaction reference, amount and payment status so a support agent can reconcile a problem without seeing sensitive credentials. Customers should never send a card number, password or one-time authentication code to support by email. A refund should go through the original provider to the original method.
Fulfillment and delivery recipients
A future print or delivery provider may need the selected garment SKU, artwork reference, recipient name, shipping address and contact details needed to make and deliver a parcel. Dwtees has selected BurgerPrints catalogue blanks for its made-to-order products; automated store connection and production-file mapping remain under review. Merely reading BurgerPrints public policies does not transfer customer information to it. Before the integration is enabled, the owner should confirm the exact fields sent, fulfillment location, tracking return flow and service terms. A carrier handling a parcel will necessarily receive delivery information for its route. Support should not send an entire customer account history to a provider when only one order needs attention.
Retention and deletion
The owner has not verified the retention settings of WordPress, WooCommerce, server logs, Cloudflare or a future payment and fulfillment provider. We therefore do not publish a fabricated number of months or promise that every record can be erased instantly. Once sales begin, some order and accounting information may need to be kept for legitimate legal or tax reasons, while an unnecessary support attachment can often be removed sooner. Dwtees should set and document a retention schedule for each data category and update this page with concrete periods. If you request deletion, support should identify the data it can remove, what must remain and why, after confirming that the requester is entitled to the information.
Access, correction and export requests
Email [email protected] with the type of information you want to access or correct. We may need to verify control of the account or order email before disclosing private data. WordPress provides tools for personal-data export and erasure, and WooCommerce can contribute order information to those workflows; using a tool responsibly still requires a human review of the request and applicable retention obligations. If a shipping address changes after an order is placed, correction may need to reach both the store and a fulfillment provider before a parcel is produced. We will explain what was corrected and what could no longer be changed rather than silently editing an old order history in a misleading way.
Security of accounts and messages
Use a unique password for any future Dwtees account and keep one-time codes private. Dwtees should maintain WordPress, WooCommerce and payment software and limit administrative access to people who need it. Transport encryption helps protect data in transit, but no website can promise that every risk is eliminated. A suspicious email about an order should be checked by opening the store directly and writing to the official support address. Do not rely solely on a logo or display name in an email. If a genuine security incident affects customer information, Dwtees should investigate the scope, take corrective action and provide any notice required by the circumstances and applicable law.
Children and unnecessary sensitive data
The collection is directed to adult shoppers and ordinary apparel purchases. It does not ask children to create accounts or provide private information. A support question about size or a design does not require health information, identity papers or a body photograph. If such information is sent accidentally, Dwtees should avoid retaining or sharing it when it is not needed to resolve the request. The site also does not currently offer a personalization feature that requires customers to upload family photographs or names. Any future feature that changes the kind of information collected must be reviewed and explained before it launches.
Changes to this notice
When Dwtees connects a payment provider, print supplier, carrier, analytics tool or marketing service, this notice should be updated to describe the actual recipient and purpose. The visible update date should change when a material edit is published. The footer should continue linking to the active version so a visitor can find it before giving information. A new public business identity or return address must be verified for its correct role before it is added here. If a customer has a question about a past version that affected an order, support should review the order’s date and explain the applicable records. This policy should be maintained as a record of real site operation, not a copy of a generic software template.