TokenAud Privacy Policy

1 Scope of this Privacy Policy

This Privacy Policy applies to the confirmed privacy boundaries of TokenAud.org, the Official TokenAud Brand Website. It sets out what this website does and does not request, how information reaches TokenAud when you choose an external support channel, and where account and transaction activity takes place instead.

This policy is not a complete account privacy statement for the TokenAud.com live environment. Information entered there is handled within that live interaction. For processing details, review the current information published in that environment where available; this TokenAud.org policy does not state or infer missing facts.

Where a privacy fact has not been confirmed for publication, this policy says so plainly rather than filling the gap. Sections 6 and 8 use a disclosure-status structure for exactly that reason, and the topics involved are listed for verification before any claim is added here.

In this policy, TokenAud means the brand name. The brand and domain roles do not identify or imply a company, data controller, operator, licensee or contracting entity.

2 TokenAud.org and TokenAud.com roles

Two domains carry two distinct roles within one TokenAud brand. The privacy boundary follows that split.

TokenAud

The brand name. Also written in search as Token AUD or token.aud, which are name variants of the same brand.

TokenAud.org

The Official TokenAud Brand Website, first-party publisher and owner of this Privacy Policy. It publishes brand information, policies, help content, security guidance and owner-page routing.

TokenAud.com

The connected account, game and transaction platform. Registration, login, account management, gameplay, deposits and withdrawals are carried out there.

Live environment

The account or transaction interface currently displayed on TokenAud.com. Information entered there is handled within that action context.

Confirmed record

The set of facts currently approved for publication on TokenAud.org. This policy publishes only from that set.

The full domain-role explanation is published on About TokenAud, and hostnames can be checked against the official TokenAud domains record. This policy does not infer company ownership, a controller or processor relationship, or any licensing arrangement between the two domains.

3 Information TokenAud.org does not request

TokenAud.org does not request or collect any of the following on any page of this website:

• passwords;
• one-time codes or OTPs;
• PINs or card security codes;
• account credentials;
• payment details;
• identity documents.

TokenAud.org pages carry no account form, no login or registration form, no cashier, no document upload and no transaction interface — including this page, which publishes no privacy request form.

If any page presenting itself as TokenAud.org asks you for the information above, treat it as unverified. Check the hostname against the official TokenAud domains record, and report it through Contact TokenAud before entering anything.

4 Information sent through support channels

When you choose to contact TokenAud through a confirmed public channel, you are sending information through an external service, not through a form on this website. The confirmed channel directory is published on Contact TokenAud.

• Opening a support channel takes you away from TokenAud.org. Check the destination before you send anything, and use only the routes published on the contact directory.
• Review the external service's current interface, terms and privacy information before sending a message there.
• Send only the minimum needed to resolve your issue. A clear description, the exact page or wording involved and a redacted screenshot are usually enough.
• Never send a password, one-time code, PIN, card security code or seed phrase through a support message. Minimise bank or identity information in messages; provide it only through a confirmed live interface when an explicit current requirement is displayed.

5 Account and transaction data boundary

Registration, login, account management, gameplay, deposits and withdrawals are carried out on TokenAud.com, the connected account, game and transaction platform. TokenAud.org does not reproduce those interfaces, and information entered there is handled within that live interaction.

TokenAud.org publishes route explanations for those actions so you know where to go and what to prepare — the registration guide, the login help page, the payment methods page and the withdrawal guide. Those pages explain routes and conditions; they do not describe how account data is processed.

When you are ready to carry out an account action, continue to the TokenAud account platform. This opens the connected platform in a new tab.

6 Cookies, analytics and technical data

Disclosure status

The current confirmed record does not provide a publishable inventory of the technical processing used by this website. Specifically, no confirmed cookie inventory, no confirmed analytics, advertising pixel or session-replay tooling, and no confirmed server-log field set, retention period or handling description is available for publication.

For that reason, this policy does not name any such tool or category, and it does not deny their presence either. Publishing a claim in either direction without verified deployment evidence would be inaccurate, and an inaccurate privacy statement is worse than a stated gap.

Your browser's own controls let you view and manage website data stored locally on your device, including clearing it. Those controls act on your own device only — they do not remove information that may be held by a server or by a third party, and this policy makes no claim about what such information consists of.

A technical deployment check must be completed before any statement about cookies, analytics or technical data is added to this page. Until then, questions on this topic are routed through Contact TokenAud, and this section will be updated when confirmed facts are available.

7 External services and links

This website links to destinations outside TokenAud.org. The two categories visible in the current confirmed record are the connected account platform and the confirmed public support channels listed on Contact TokenAud.

• An external destination has its own URL, interface, terms and privacy information. Activity after you arrive there falls outside the TokenAud.org policy boundary; review the destination's current published information where available.
• Check the domain before acting. The official TokenAud domains record is where TokenAud hostnames can be verified; a route that does not appear on the relevant record is not currently confirmed there.
• TokenAud.org does not claim control over the data practices of any external service, and this policy does not characterise external destinations as processors, service providers or agents of TokenAud.

8 Data use, sharing and retention status

Disclosure status

No verified operational inventory has been supplied for data purposes, sharing, disclosure, service providers, cross-border storage or retention for TokenAud.org. This policy therefore publishes the boundaries confirmed in sections 3 to 7 and does not substitute generic wording for missing evidence.

Accordingly, this policy makes no assertion in either direction about the sale, rental or sharing of information, names no service provider or processor, states no retention period or deletion schedule, and identifies no storage location or transfer arrangement. It also states no legal basis, consent model or automated decision-making practice.

These statements will be added only once the underlying facts are verified and approved for publication, and the review date on this page will be updated at the same time. Sections 6 and 8 are the two areas where that verification is outstanding.

9 Privacy and security practices

The protective measures this policy can state are the ones that follow directly from the confirmed website boundary. They are practical rather than technical claims:

• TokenAud.org does not collect the sensitive account information listed in section 3, so that information is not entered on this website at all.
• Account credentials belong only inside your own TokenAud.com session. No page on this website, and no support conversation, requires them.
• Verify the official domain before acting on any link, page or message, using the official domains record.
• Minimise what you send. Before sharing a screenshot or message, remove account identifiers, balances and personal details that are not needed to resolve the issue.
• Report an unexpected request for personal or account information through Contact TokenAud.

10 Privacy questions, corrections and requests

Privacy questions and requests are handled through the confirmed support channels published on Contact TokenAud. That page is the single route for all of the following:

• ask a question about this Privacy Policy or about the website's data boundary;
• report wording on this page that appears inaccurate or out of date;
• ask which confirmed channel is appropriate for a particular request;
• request correction or deletion of information you previously sent through a confirmed channel;
• report impersonation, or a page or message making an unexpected request for your information.

11 Adults aged 18 and over

TokenAud is for adults aged 18 and over. This website and the connected account platform are not intended for anyone under 18.

Adults are responsible for keeping account access away from minors in their household: do not let a minor use your account, your payment details or a logged-in device, lock your devices, and log out when you finish. Age guidance, warning signs and independent support are published on the TokenAud responsible gambling page.

12 Policy updates and related pages

This Privacy Policy is updated as confirmed facts become available. The two areas currently marked as disclosure status — technical processing in section 6, and use, sharing and retention in section 8 — will be revised once verified information is approved for publication.

On every substantive change, the visible review date on this page and the structured review date published with it are updated together. The version currently published on this page is the version that applies. No notification by email or message is promised, because no such notification arrangement is confirmed.