Privacy information

Browsing and contacting are different actions

You can read the public pages and installation guides without sending a message to the team. Browsing still involves technical requests to the hosting service so the page can be delivered, as described above. Opening an external contact button is a separate action that takes you to another service. You choose whether to continue there and whether to send information in the conversation.

This distinction helps you control an enquiry. Reading a plan or device guide does not require you to provide your name in a public comment. If you need assistance, begin with the details relevant to that question rather than sending unrelated personal documents. A device model and a short description can often identify the next support question without exposing an account password.

How the automatic currency feature fits into browsing

The theme uses the connection IP address to choose its currency display. A local database on the server identifies British addresses for GBP, with USD displayed elsewhere. The feature described here does not send that address to an external geolocation API and does not require a tracking cookie or a stored manual currency preference in your browser.

The connection location is an approximation. A VPN, mobile network or other exit point can affect the result. The displayed currency therefore describes how this feature classified the connection used for that visit; it is not a request for your home address or proof of your residence. Check the currency and full-period total shown in the order summary before continuing with a purchase enquiry.

What the public theme's cookie statement covers

The statement above concerns the public theme's advertising and analytics behaviour. It is separate from the necessary authentication and security functions that WordPress can use for an administrator sign-in. A visitor reading a public guide and an administrator opening the editing area are different uses of the website. The presence of an administration function does not mean visitors must sign in to read the guide.

It is also separate from third-party pages opened through external links. Their services can apply their own cookies and privacy practices. If you follow a link to an app publisher, platform documentation or a messaging service, review the information provided by that destination when it matters to your decision. The website's explanation of its own theme should not be read as a description of every external service.

External contact and offer links

Contact and offer buttons can open WhatsApp, sometimes through a redirect service. Following the link allows the relevant external services to process technical connection information under their own practices. An offer route may also prepare a message about the selected plan. Review the proposed conversation and amount rather than assuming that opening it completes an order.

You decide which message to send. Keep full payment-card details and passwords out of ordinary chat. If a conversation concerns a technical fault, start with the screen model, player name and the visible error, with private fields removed. Information you choose to send is used for the enquiry, order or support request you make, as described in the existing contact section above.

Keep access-bearing details private

A complete playlist URL, server entry, username or device key can be more sensitive than it first appears. Before sending a screenshot, inspect the address bar, menus and corners of the image as well as the main error. Keep only the parts needed to explain the problem when sharing publicly. A loading symbol or menu mismatch can usually be described without displaying the full source address.

If support needs a private technical detail to examine a specific account, confirm the appropriate route and purpose before sending it. Do not place someone else's account information in a shared example. The guide to private setup information explains practical ways to prepare a support record while keeping recovery details under your control.

Preparing a question about information you supplied

Use the contact route linked on the website and describe the relevant conversation or information. State the practical question you want answered, such as asking about details you previously sent while arranging an order. Include enough context for the enquiry without reposting an entire private conversation or attaching unnecessary documents. If another step is needed, clarify it through that route.

This page does not specify a new retention period for an order or an external messaging account. Any required retention for the particular order should be confirmed with the seller during the conversation, as noted above. The external service's own account and message controls are separate from the public theme's browsing features.

Understand the limits of this feature description

This information describes the site's current browsing, currency and contact features. It does not turn an external publisher's page into part of the same service, and it does not claim that a technical request leaves no hosting record. The earlier hosting section explains the request information processed to deliver and protect a hosted website. Read the sections together rather than treating a single sentence about cookies as a description of all technical processing.

If new analytics, advertising, registration or another feature is introduced, this information should be reviewed before relying on it to understand the changed website. Likewise, a device app installed from a separate publisher has its own features and practices. Installing that app is distinct from reading an installation guide on this site.

Practical choices while using the resources

• Read the public guides without providing a name or contact message.
• Check the destination when deciding whether to open an external support, publisher or documentation link.
• Review the selected duration, currency and prepared enquiry before sending a message.
• Keep passwords, full card information and private source links out of public screenshots.
• Ask a focused question through the existing contact route when you need clarification about information you supplied.
• Keep your own recovery information securely rather than publishing it as part of a technical example.

The contact page explains how to prepare a concise enquiry, and the editorial information describes the preparation and limits of the explanatory resources. These pages address different questions: one concerns communication, while the other explains how to read the site's guides and illustrations.

Example: reading a guide before asking for help

You might read a device guide, compare the current subscription totals and leave without sending a message. The browsing and automatic-currency explanations above apply to those website features. If you later choose to open WhatsApp, that is a separate external step with its own service practices.

Before sending the enquiry, review the prepared text and remove anything unrelated to the question. A device name and an error description can begin a support discussion without a public password or a full private source link. This example explains the difference between the available actions; it does not change the existing description of hosting requests or the external service's practices.