
- Welcome package
- 3 stages
- VIP levels
- 5
- Weekly withdrawal bands
- EUR 2,250–10,000
Across five VIP levels; limits may be adjusted.
- Monthly withdrawal bands
- EUR 9,000–40,000
Across five VIP levels; limits may be adjusted.
Tower privacy and account information
We treat account information as part of the trust placed in Tower. Our privacy guidance explains the role of account and transaction context in service access, payment processing, safer-play procedures and support conversations. Where a payment condition needs a check, we keep the requested information connected to that action.
Our account is personal and non-transferable. We use that account context when explaining personal service access, payment checks and a request a player brings to our team.
Information connected to our service
The information we may need is linked to a specific account action:
- Account details help us keep a Tower account personal and non-transferable.
- Transaction information helps us process deposits and withdrawals and identify a status request.
- Identity, location, and source-of-funds information may be needed before a payment is processed.
- Support information helps our team respond to an account, safer-play or transaction question.
Changes to our notice
A visible update point
We display an update date, so readers can identify the version of our privacy notice. We may revise wording when an account route, payment condition, or safer-play procedure needs a clearer explanation.
Reading revised wording
We encourage a reader to connect a change with the account activity it concerns. Our notice explains our practice in plain language, while account activity remains subject to the relevant service conditions.
Retention in context
| Information type | Service purpose | Retention context |
|---|---|---|
| Account record | Personal service access | Account relationship |
| Transaction record | Payment processing and status | Payment record |
| Verification context | Required payment checks | Relevant check |
| Support message | Handling a player request | Conversation purpose |
We describe retention by purpose because each category serves a different account action. Our team keeps the relationship between the information and the request visible.
Your account-data choices
We provide routes for a data question through our support channels:
- Ask our team about an account or transaction record.
- Explain the purpose of a verification question without publishing private details.
- Request account closure through support when ending the account is appropriate.
We also recognise time-outs and self-exclusion as safer-play tools. Our player can raise a privacy question and a safer-play request separately, allowing each message to stay focused.
How we use information
We use information for personal account access, payment processing or review, support responses and safer-play procedures where needed. Our service right is personal, limited and revocable under the terms. We aim to make the account context understandable before a player needs to prepare a request.
Last updated: 3 November 2026
