TAXIS33 Privacy Policy: What the Platform Asks For, What It Is Used For and What Is Not Published
TAXIS33 operates taxis33.org for Australian players aged 18+, and this page sets out the information the platform visibly asks for, the operational purpose each piece is visibly used for, and — just as plainly — the data-handling questions this website does not answer. It is written to the same standard as every other page here: stated where it can be evidenced from the live platform, and marked as not published where it cannot.
Quick answer: what does TAXIS33 ask for, and what does this page not cover?
The platform visibly asks for account details at registration, login credentials, payment details you enter or use in the cashier, identity information at the verification step before a withdrawal, and it records the play and transaction history that drives VIP levels, tournament ranking and the leaderboard. Each is used for the operation it appears in: access, payment matching, verification and reward calculation. What this page does not state is anything about the handling behind those points — retention periods, storage locations, transfers, processors, deletion timelines, security standards or compliance status. Those are not published on this website, and an unanswered question is left unanswered rather than filled with a standard paragraph.
18+ only · Australia · Read with Terms & Conditions and the Disclaimer · This page is not legal advice
How this page was prepared: TAXIS33 operates this website. The collection points below are described from what the current platform visibly asks for or displays — including registration and login, the cashier, withdrawal verification and the visible reward and leaderboard systems — and were re-checked; last reviewed 12 September 2026. A visible field or platform output can show that information is requested or used at that point; it does not establish how that information is stored, retained, disclosed, transferred or deleted afterwards. This page therefore does not state those handling practices unless TAXIS33 publishes them. This page is not legal advice and makes no statement about compliance with any privacy regime.
On this page — TAXIS33 Privacy Policy
- What this page covers, and on what basis
- Information the platform visibly asks for
- What each collection point is used for
- What this page does not state
- Third-party channels and destinations
- What you control, and what to keep private
- Privacy questions and correction requests
- Independent privacy information in Australia
- FAQ
What This Page Covers, and on What Basis
This page describes the points at which the TAXIS33 platform visibly asks for or records information, and the operation each point serves. It does not describe what happens to that information afterwards, because that is not something a website interface can demonstrate and this website does not publish it.
| What this page states | The collection points that are visible on the current platform, and the operational purpose each one plainly serves. |
|---|---|
| How that is established | By what the platform asks for at registration, at login, in the cashier, at the verification step before a withdrawal, and by the play and transaction history the reward systems visibly use. |
| What this page does not state | Retention, storage, transfer, disclosure, processors, deletion, security standards, cookie inventory and compliance status — see the boundary section. |
| Why it is written this way | A visible field proves information is requested at that point. It does not prove how that information is stored, kept, shared or deleted. Writing the second thing from the first would be an assumption presented as a policy. |
| If you need information that is not published here | You can ask through TAXIS33 live chat whether the platform can clarify it. This page does not assume that support has information which TAXIS33 has not published. If additional privacy information is formally published, this page should be updated and re-dated. |
Information the Platform Visibly Asks For
Five points, in the order a player meets them. Each is described only as far as the platform makes it visible.
| Point | What is visibly involved | Where it appears |
|---|---|---|
| Registration | The account details you provide when creating an account. Published TAXIS33 rules require registration information to be accurate, and the registered details are later relevant to withdrawal verification. This establishes their operational use; it does not establish how long those details are stored or how they are handled afterwards. | Register |
| Login | The credentials you created at registration, entered on the official website. | Login |
| Cashier — deposits | The cashier uses transaction information associated with the deposit route you choose. Depending on the visible route, this can include a PayID or bank destination, a transaction amount and reference, or a USDT-TRC20 transfer destination. Card and mobile-wallet routes are available through the cashier, but this page does not state what card or wallet information TAXIS33 itself receives or retains because that handling is not published. The published deposit guidance also requires the paying account information to remain consistent with the registered TAXIS33 account where that rule applies. | Payment Methods |
| Withdrawal verification | Identity verification is required before a withdrawal is processed, on every payout route, and the registered details are checked against the payout account. The platform does not publish which documents or checks are used, and this page does not list any. | Withdrawal |
| Play and transaction records | Deposit totals, play activity and results are recorded and used by the reward systems: VIP levels are set by total deposits, the Top 50 Deposit Tournament ranks by total accumulated deposits in the monthly cycle, and the live leaderboard displays game, bet, win and payout ratio against a masked player identifier. | VIP · Leader · Leaderboard |
Support conversations are a sixth point in practice: what you send to live chat is what support receives. Send your username and the transaction details it needs — never your password, a wallet seed phrase or a one-time security code, and never in a public channel.
What the Visible Collection Points Are Used For
The purposes below are limited to functions that can be seen from the current TAXIS33 account, payment, withdrawal and reward flows. No additional marketing, profiling, analytics, disclosure or secondary use is stated here because those practices are not published.
- Account access. Registration details and login credentials are used in creating and accessing the TAXIS33 account.
- Deposit matching. Published deposit guidance uses the transaction amount, current destination or route information and any required reference so the deposit can correspond with the cashier entry created for it.
- Withdrawal verification. Identity verification is required before a withdrawal is processed, and the registered details are checked against the payout information used in that process.
- Reward and ranking functions. Deposit totals are visibly relevant to VIP progression and the Top 50 Deposit Tournament, while the Leaderboard displays game, bet, win and payout-ratio information against a masked player identifier.
- Support. Information you choose to provide through TAXIS33 live chat can be used to investigate or answer the support question you submit. Do not send a password, wallet seed phrase or one-time security code.
These observable purposes do not establish what TAXIS33 does with the same information outside the visible function, how long it is retained, whether another service processes it, or where it is stored. Those questions remain within the unpublished-handling boundary below.
What This Page Does Not State
This is the most important section on the page. Each item below is a question a privacy policy is normally expected to answer, and each is left unanswered here because this website does not publish the answer. A standard paragraph in place of any of them would read as a policy and function as an assumption.
- No retention period. How long information is kept is not published, and no period is stated.
- No deletion timeline or erasure process. No commitment about deletion on request or on account closure is published.
- No storage location. Where information is stored, and whether it is stored in Australia or elsewhere, is not published.
- No cross-border transfer or disclosure statement. No transfer, disclosure or overseas-recipient position is stated.
- No processor or third-party sharing list. Which service providers may handle information on the platform’s behalf is not published, and no list is invented here.
- No security standard. No encryption standard, certification, audit or security claim is stated.
- No cookie or tracking inventory. No cookie list, analytics inventory or consent mechanism is described.
- No data protection officer or dedicated privacy contact is published; privacy questions go through the ordinary support route below.
- No compliance claim. This website makes no statement that the platform is subject to, or compliant with, the Australian Privacy Principles, the Privacy Act, the GDPR or any other privacy regime, and nothing on this page should be read as such a statement.
- No formal access or correction procedure is published. TAXIS33 publishes live chat and Contact Us as general support routes, but this page does not describe them as a statutory privacy-rights process or promise a particular access, correction or deletion outcome.
Stating these as unknowns is a deliberate choice. If the platform publishes any of them, this page is updated and re-dated rather than assumed.
Third-Party Channels and Destinations
TAXIS33 links to or uses several third-party services, but this Privacy Policy does not describe how those organisations handle information inside their own services. Before submitting personal or account information outside taxis33.org, check the destination and its own privacy information.
- Telegram. TAXIS33 publishes an official Telegram channel and some current promotional instructions may direct players there. Telegram is a separate third-party platform. Do not post TAXIS33 passwords, verification codes, payment credentials or sensitive account information in a public-facing Telegram space.
- Facebook. The TAXIS33 Facebook presence is hosted by Meta. Activity and information submitted there sit outside this website and are subject to the third-party service's own privacy information.
- Google Play. The Android app is distributed through Google Play. The TAXIS33 App page routes users to the current distribution channel, but this policy does not describe Google's own collection or handling practices.
- Banks, card services, wallets and crypto services. Payment activity can also involve the financial or wallet service chosen by the user. TAXIS33 does not use this page to describe those providers' independent privacy or record-keeping practices.
- Partner brand websites. The destinations referenced from the BFM Partnership and SPEEDAU Partnership pages are separate websites. Information entered on those destinations falls outside the scope of this TAXIS33 Privacy Policy.
- Independent support services. Services referenced from Responsible Gambling are operated independently. TAXIS33 does not use this page to state whether information is exchanged between those services and TAXIS33 unless such a relationship is specifically published.
What You Control, and What to Keep Private
Several of the most effective privacy controls in an online account sit with you rather than with the platform. These work immediately and do not depend on anything being published.
- Never share your password, a wallet seed phrase or a one-time security code with anyone, through any channel, whoever the message claims to be from.
- Keep account and payment details accurate and consistent. They are compared at the verification step before a payout, and an inaccuracy found there forfeits the amount under the published promotion terms.
- Treat public channels as public. Do not post your username together with transaction details, screenshots showing a PayID or an account number, or anything you would not put on a noticeboard. Account matters belong in live chat.
- Crop before you send. A screenshot for support rarely needs the full cashier screen; crop out payment destinations and identifiers that are not part of the question.
- Manage saved payment details and browser data in your own browser, wallet and device settings; removing stored payment methods also makes funding a deliberate act rather than a one-tap one.
- Check the website before entering TAXIS33 credentials. Use taxis33.org for normal TAXIS33 account access and verify the address before entering a username or password. For current official channels and impersonation guidance, see Contact Us .
Privacy Questions and Correction Requests
TAXIS33 does not currently publish a dedicated privacy email, data protection officer or separate privacy-request channel. Account-specific privacy questions can be raised through TAXIS33 live chat , while questions or corrections about the information published on this page can also be sent through Contact Us .
- For an account question: identify your username and explain the information or issue you are asking about. Never provide your password, wallet seed phrase or one-time security code.
- For registration details: ask support what correction options are available before relying on changed information for a future withdrawal. This page does not claim a formal correction right or procedure that has not been published.
- For a website correction: identify the page and the specific statement that appears outdated or inconsistent.
- No response-time commitment is published. This page therefore does not promise when a privacy question, correction request or account question will be answered.
Independent Privacy Information in Australia
For general information about privacy policies and the Australian Privacy Principles, readers can use guidance published by the Office of the Australian Information Commissioner (OAIC) . That is an independent public source about Australian privacy law and privacy practice; it is not evidence of TAXIS33's regulatory status.
What this external reference does — and does not — establish
- It provides independent general information. The OAIC explains privacy policies, the Australian Privacy Principles and personal-information rights in Australia.
- It does not establish TAXIS33 coverage. Nothing on this page states that TAXIS33 is an APP entity, is regulated by the OAIC, is subject to the Privacy Act, or complies with a particular privacy regime.
- Coverage remains an unpublished legal fact for this website. An authoritative external source can explain the law generally without supplying an operator-specific legal status that TAXIS33 has not published.
The same evidence rule applies throughout TAXIS33: external organisations are cited for what they themselves publish, not as proof of TAXIS33 licensing, legal status, coverage or compliance.
TAXIS33 Privacy Policy — FAQ
The data questions asked most, answered inside the evidence boundary.
What information does TAXIS33 ask for?
Account details at registration, your credentials at login, the payment details you use in the cashier for the route you choose, identity verification information before a withdrawal is processed, and the deposit and play records that drive VIP levels, tournament ranking and the live leaderboard. Each is described on this page only as far as the platform makes it visible.
How long does TAXIS33 keep my information?
No retention period is published on this website, and this page does not state one. The same applies to deletion timelines, storage location and transfers. Ask through TAXIS33 live chat if you need that detail for your account; the page is updated and re-dated if the platform publishes it.
Is TAXIS33 covered by the Australian Privacy Principles or the GDPR?
This website makes no statement that the platform is subject to, or compliant with, the Australian Privacy Principles, the Privacy Act, the GDPR or any other privacy regime, and nothing on this page should be read as such a statement. Where a fact is not published here, this website does not assert it.
Is my play visible to other players?
The TAXIS33 Leaderboard visibly publishes game, bet, win and payout-ratio information against a masked player identifier across its current result views. This page does not state that no other TAXIS33 feature can ever display account-related activity; it records only the public display currently evidenced.
Who do I contact about a privacy question or a correction?
TAXIS33 does not publish a dedicated privacy contact or data protection officer. Account-specific questions can be raised through TAXIS33 live chat, while questions or corrections about this page can also be sent through Contact Us. Include only the information needed to explain the issue and never send your password, wallet seed phrase or one-time security code.
Does joining the Telegram channel share my account details?
This Privacy Policy does not state that joining the TAXIS33 Telegram channel automatically shares TAXIS33 account details with Telegram or with other users, because that data flow is not published here. Telegram is a separate third-party service. Do not post passwords, verification codes, payment credentials or sensitive TAXIS33 account information in public-facing Telegram spaces.