Privacy Policy

If you visit the site, then technical information may be recorded automatically, including the device type, browser version, approximate location derived from an IP address, and pages viewed. When that information is used alone, then it does not identify you by name.

When you place an order, then we collect the name, email address, delivery and billing addresses, contact number where a carrier requires one, items purchased, and the payment result returned by the processor. When you send a message, then the correspondence and order reference are added to the support record.

If a checkout field is optional, then leaving it blank does not prevent the order from proceeding. If a field is required, then it is marked before submission rather than being discovered through an error message.

When a detail is not needed to fulfill an order, answer a question, prevent fraud, or meet an accounting duty, then it is not requested. If you ask why a particular item is held, then the answer identifies the operational, contractual, or legal reason for that record.

If you leave an optional field blank, then that choice is recorded only as part of the order flow.

When information is used to fulfill an order, then it supports payment, stock reservation, packing, dispatch, delivery updates, returns, refunds, and customer support. When it is used for accounting, then the order record supports tax, reconciliation, and fraud-prevention obligations.

If technical information is used for analytics, then the result is reviewed in aggregate to understand page performance, broken journeys, and unusual traffic patterns. If information is used for security, then the purpose is to detect card testing, automated abuse, and unauthorized access.

When consent is the basis for a use, then you can withdraw that consent at any time. When withdrawal occurs, then it stops future use but does not undo a lawful action that was completed before the request.

If you ask why a detail is needed, then the answer identifies the specific purpose rather than offering a general statement about improving service. When information is no longer needed for its stated purpose, then it moves into the retention or deletion path described below.

When information is used to prevent fraud, then the review may compare order details, payment results, and delivery patterns. If a transaction is flagged, then the order may be held while the customer is contacted. When the check is complete, then the order is released or declined with an explanation.

If a cookie is essential, then it supports the basket, checkout session, security checks, or basic site preferences. When an essential cookie is blocked, then the basket or checkout may fail because the site cannot remember the choices needed to complete an order.

When an analytics cookie is set, then it records page views under a random identifier so traffic can be measured in aggregate. When analytics data is reviewed, then it is used to understand which pages work and where visitors encounter friction rather than to identify an individual shopper.

If you block analytics cookies, then the site and checkout remain available. If you clear browser storage, then a saved basket or session preference may disappear, and you may need to enter the information again.

When you return to the site, then an analytics identifier may recognize the browser as a previous visitor. When that recognition occurs, then it does not change prices, unlock special treatment, or connect the visit to your order record.

When a consent tool is shown, then the choice recorded by that tool controls non-essential cookies for that browser.

When information is shared with a payment processor, then the processor receives the payment details needed to authorize or refund the transaction. When information is shared with a carrier, then the carrier receives the delivery address and a contact number where one is required.

If hosting or email services process data, then they receive only the information required to provide storage, deliver messages, or keep the site available. If a supplier handles support tools, then access is limited to the records needed to answer the customer request.

When a supplier is appointed, then the contract limits the supplier to processing information on our instructions and requires appropriate confidentiality and security. When a supplier no longer needs the data, then it must delete or return it according to the agreement.

If a legal authority requires information, then disclosure is limited to what the applicable law compels. When disclosure is permitted, then you are told unless the law or an active investigation prevents us from giving notice.

When a supplier changes, then the same purpose and access limits continue to apply to the replacement.

If an order record is retained, then the usual period is seven years because tax, accounting, warranty, and fraud-prevention rules may require it. When the record contains a delivery address, items purchased, payment result, or refund history, then the accounting need applies to the transaction rather than to unrelated browsing activity.

When support correspondence is retained, then it is kept for two years so a later question can be answered with the same facts. When an item is returned, then the inspection notes, photographs, and refund record follow the order retention period rather than a separate indefinite schedule.

If an account is closed, then information that is not legally required is deleted. If a deletion request concerns an order that must remain for tax or fraud purposes, then the retained record is limited and the reason for keeping it is explained.

When a retention period ends, then the record is deleted rather than hidden in a secondary system. If a backup contains the record, then it is removed when the backup cycle completes and is not restored for ordinary business use.

When payment security is considered, then card details are entered on Stripe's hosted page rather than on our own checkout. When data moves between your browser and the site, then encryption protects it in transit. Full card numbers and PayPal passwords are not stored by us.

If an employee needs order information, then access is granted through an individual account for a defined role. When that role changes or employment ends, then access is removed on the same day rather than left active for convenience.

When unusual activity appears, then the pattern is reviewed and may lead to a payment hold, access restriction, or request for verification. When a security incident affects personal information, then the response identifies what happened, what data was involved, and what steps are being taken.

If an email asks for a password, card number, security code, or payment outside checkout, then treat it as suspicious and report it to [email protected]. When a message cannot be verified, then do not send credentials or payment details through email.

Physical records are kept in locked storage and accessed only when an order issue requires them.

If you request access, then we provide a copy of the personal information held about you. If you request correction, then inaccurate details are updated after verification. If you request deletion, then information that is not legally required is removed.

When you object to a use, then the objection is assessed against the purpose and any legal basis that applies. When you request portability, then the information is provided in a structured format where the request covers data supplied by you or generated through your use of the service.

If a request cannot be granted in full, then the reply identifies the rule or operational limit that prevents it and explains any option that remains. When the request affects an order record, then the review also considers tax, fraud, warranty, and dispute obligations before deletion.

When you no longer want marketing email, then use the unsubscribe link in the message or contact [email protected]. When the message concerns an order, dispatch, return, refund, or security issue, then it is a service message and may still be sent after marketing consent is withdrawn.

When a child or minor visits the site, then the service is not designed to collect personal information from a child under 13. If an order is intended for a child, then the adult placing the order provides the contact and payment details.

If a parent or guardian makes a privacy request for a child, then the request follows the same verification and response process as any other request. When the request concerns deletion, then information that is not required for an order, tax, fraud, or safety purpose is removed.

When someone believes a child has sent personal information, then a short message to [email protected] is enough to begin a review. If the information is not needed, then it is deleted, and the sender is told what action was taken.

If a product page mentions an age range, then that statement concerns safe use rather than the age at which someone may place an order. When a child uses a product, then an adult remains responsible for the purchase, supervision, and care instructions.

If a request concerns information sent by a child, then the review focuses on deletion and on preventing further collection. When the information is needed for a safety or legal reason, then the retained part is limited and the reason is explained.

If you contact us about privacy, then write to [email protected] and identify the right you wish to exercise or the question you want answered. When the request concerns an order, then include the order reference so the correct record can be located.

When we receive a request, then identity may be verified before information is released, corrected, or deleted. When the request is clear and verification is complete, then a response is normally sent within one working day, and a formal request is answered within 30 days.

If the response does not resolve the issue, then ask for a review and explain which part remains unclear. When a review is needed, then the matter is handled by someone who was not responsible for the original decision.

When the privacy policy changes in a material way, then the revised version is published with a new effective date. If a change affects an order that has already been placed, then the version that applied when the order was placed continues to govern that transaction.

If the request is urgent because of a security concern, then mark the subject line accordingly.