{"page":{"id":3,"title":"Privacy Policy","handle":"privacy-policy","url":"https://teepalace.com/privacy-policy/","body_html":"<p class=\"policy-updated\">Last updated: <time datetime=\"2026-10-01\">October 1, 2026</time></p>\n<section class=\"policy-summary\">\n<h2>At a glance</h2>\n<p>TeePalace receives information you provide while shopping or contacting support, such as your name, email address, delivery details, order choices and support messages. Do not include information unrelated to your request. Product browsing and a cart can also create technical session information needed to remember selections. This page does not claim that no personal data is processed.</p>\n</section>\n<h2>1. Information you provide</h2>\n<p>TeePalace receives information you provide while shopping or contacting support, such as your name, email address, delivery details, order choices and support messages. Do not include information unrelated to your request. Product browsing and a cart can also create technical session information needed to remember selections. This page does not claim that no personal data is processed.</p>\n<h2>2. Why the information is used</h2>\n<p>Order information is used to process a legitimate order, provide delivery and answer order questions. Support messages are used to respond to your request and document its resolution. Technical information may help operate and protect the storefront. We do not claim that a particular analytics or marketing provider is active without verifying its actual configuration.</p>\n<h2>3. Payment information</h2>\n<p>Payment should be handled through a connected checkout provider once available. Do not send full payment-card details or authentication secrets to support. The storefront may retain an order reference and payment status needed for customer service; that is different from holding every piece of sensitive payment information. The current payment gateway has not been connected.</p>\n<h2>4. Delivery and service providers</h2>\n<p>A carrier or fulfillment provider may need the details required to deliver an accepted order, such as the recipient name and address. A service provider’s own privacy terms may also apply to its work. We do not list an unverified supplier as though a data-sharing connection were already active. Ask support if you need clarification about a specific order arrangement.</p>\n<h2>5. Cookies and your choices</h2>\n<p>Cart and session cookies may be needed to preserve your selected items and operate checkout. Your browser can remove or block cookies, but some store functions may then work differently. We do not describe a universal opt-out as a guarantee that all technical processing stops. Contact support to ask about access, correction or deletion of your information, identifying the relevant order or communication.</p>\n<h2>6. Requests and safety</h2>\n<p>Contact support@teepalace.com to make a privacy request. We may need proportionate information to locate the relevant record and avoid disclosing another person’s information. Do not send excessive identity documentation without an agreed need. Some records may need to be retained for legitimate order, accounting or legal obligations; the applicable details require owner review rather than an invented retention period.</p>\n<h2>Contact and related guidance</h2>\n<p>Contact <a href=\"mailto:support@teepalace.com\">support@teepalace.com</a> with a specific question. Read our <a href=\"/contact/\">contact guidance</a>, <a href=\"/returns-exchanges-policy/\">returns process</a> and <a href=\"/refund-policy/\">refund policy</a> for the relevant details.</p>\n<h2>Practical guidance and examples</h2>\n<h3>Information supplied for a shopping enquiry</h3>\n<p>When you ask about a design, size, price or order, you may provide a name, reply address, product reference and explanation of the question. Share only the details needed for that particular enquiry. A product question does not require a card number, government identifier or password. If an order number exists, use that reference so support can understand the relevant purchase without receiving unrelated private records. If you accidentally include sensitive information, tell support which message is affected so the conversation can be handled appropriately.</p>\n<h3>Information connected to a cart</h3>\n<p>A cart needs to remember selected products, size options and quantities during a browsing session. Such session information can be stored in a cookie or similar technical mechanism. A selected cart is not proof that a payment was made, and the current payment gateway has not been verified as connected. Clearing a browser session can affect a saved cart. If a cart displays another person’s information or behaves unexpectedly, stop using that session and contact support with the route and general issue, without sending another person’s details.</p>\n<h3>Information connected to an order</h3>\n<p>If checkout later accepts a real order, the store may need purchaser contact details, the delivery address, item and option selections, quantity, order reference and relevant status events to administer that purchase. A delivery address is used for the order rather than to identify a public visitor. Review the details before submission and report a correction promptly. The existence of an order record does not imply that a payment settled or that fulfillment occurred. Those events need their own actual confirmation.</p>\n<h3>Payment data and provider boundaries</h3>\n<p>Only enter payment information through a method actually offered by a verified checkout. TeePalace does not ask customers to email complete card details, security codes, authentication codes or account passwords. A provider can control its own authentication and payment records; the store may receive a transaction reference or status needed to reconcile an order. Do not assume a named provider is active simply because it is contemplated in a policy. If an unexpected link requests payment, verify it against the store’s actual checkout and contact route first.</p>\n<h3>Support messages and attachments</h3>\n<p>A support request may contain a product URL, order reference, photographs relevant to a claimed issue and your preferred reply address. Describe the problem in enough detail to let support assess it, but omit unrelated identity documents, other customers’ information and private account credentials. If an image includes a shipping label or another person, crop or obscure information not needed to explain the request. A support conversation may be retained with the case so earlier facts and responses remain understandable.</p>\n<h3>Technical records that operate the site</h3>\n<p>A website can process an IP address, browser information, request time, device characteristics and error details to serve pages and investigate availability or security problems. Those records are different from public product content. A visitor should not expect a public product JSON endpoint to expose customer sessions, orders or account details. Technical records should be used in relation to site operation, abuse investigation and troubleshooting; this page does not invent a particular retention period or claim an unverified security certification.</p>\n<h3>Cookies and settings</h3>\n<p>Functional cookies or session identifiers can support a cart, login or preference during a visit. Your browser may let you inspect or restrict them, although blocking essential functions may interrupt a cart or account session. Additional analytics or advertising technologies should be identified according to the actual deployed configuration; this policy does not assert that an unverified third-party tracker is active or absent. If a privacy choice is presented in the live interface, follow that control and contact support if its effect is unclear.</p>\n<h3>Sharing to complete a requested service</h3>\n<p>A real paid order may require limited details to be passed to a connected payment processor or a fulfillment or delivery provider. Share only information needed for the function involved, such as a delivery destination for shipping or transaction status for payment reconciliation. The actual provider relationship must be verified before naming it as active. A support request is not a reason to publish a customer’s address, payment reference or private correspondence in a public page or product feed.</p>\n<h3>Marketing and unrelated messages</h3>\n<p>A purchase or support question should not be treated as automatic consent to unrelated promotional messages. If a newsletter or similar choice is offered, read its own sign-up language and use the available unsubscribe or preference route. This policy does not claim a particular mailing platform is connected. If you receive a message you believe came from TeePalace and cannot tell why, provide the non-sensitive sender and subject details through support so the issue can be reviewed without forwarding credentials or authentication codes.</p>\n<h3>Access, correction and deletion questions</h3>\n<p>To ask about information connected to your own account, order or support conversation, contact support with a clear request and a safe way to identify the relevant record. A request for another customer’s data cannot be handled as though it were your own. A correction may need to be distinguished from an existing transaction record that must remain accurate. This page does not promise immediate deletion of every record regardless of transaction or legal obligations. The response should explain the applicable next step for the specific request.</p>\n<h3>Children and submitted details</h3>\n<p>This storefront is a general apparel store and its shopping flows are not designed as a collection channel for children’s personal information. Do not provide a child’s sensitive details in an ordinary product or order enquiry. If a parent or guardian believes a child has submitted information through a store form, identify the route and approximate date through support without repeating the sensitive data in a public comment. The report can then be considered against the actual record and applicable obligations.</p>\n<h3>Changes and questions about this notice</h3>\n<p>A policy update should be dated and presented on this page so readers can see the current guidance. A change to copy does not retroactively prove that a service, provider or data practice was active at an earlier date. If you need to understand how a particular order or support case was handled, ask with its reference and the privacy question. For a general question, contact support@teepalace.com. Do not send a password, complete card number or one-time code as part of that enquiry.</p>\n<h3>Keep a privacy request focused</h3>\n<p>A clear request can identify whether you want to correct an address, understand a support record, ask about an account or report an unexpected disclosure. State the relevant date and your own order or case reference where one exists. The store may need to confirm that the requester is entitled to receive the information before sharing it. Avoid publishing the request in a product review or social comment, where private facts could become visible to others. The support route is intended for a one-to-one response about the specific record and practical next step.</p>\n","visible_characters":10614,"meta_description":"Privacy Policy at TeePalace. Find clear guidance for original apparel, shopping and support, with free eligible shipping, 60-day returns and refund details.","parent":null,"published_at":"2026-10-01T15:39:10+00:00","updated_at":"2026-10-02T10:28:13+00:00"}}