Privacy and account control
Map Where Zone Account Data Is Used
Registration, payments, gameplay and support create different data records. Identify the purpose and vendor before making a correction, access or deletion request.
Review the current Zone account routeList the data categories
Separate profile identifiers, device and login records, payment details, game history, support messages and marketing choices. A request for one category may not return the others.
Record which data is shown directly in account settings and which requires a formal request.
- Profile
- Security logs
- Payments
- Gameplay and support
Identify service providers
The privacy notice may describe payment processors, analytics, hosting and customer-support vendors. Save the current notice and note which provider appears in the specific transaction or message.
Do not assume every vendor can decide an account dispute. Ask Zone which party controls the record and which is only processing it.
Make a precise request
State the account identifier, requested data category, date range and preferred format. For a correction, identify the inaccurate field and provide the minimum evidence required.
A deletion request may be limited by transaction, security or legal retention obligations. Ask which records are retained, for what reason and until when.
- Account ID
- Category
- Date range
- Requested action
Secure the response
Use the verified privacy or support channel and confirm identity through the provided secure flow. Do not send passwords or full card details in an ordinary message.
Archive the request, acknowledgement, response date and any refusal or retention explanation.
Zone account questions
Does closing an account instantly erase every transaction record?
Not always. Operators and processors may retain records for stated security or legal reasons.
What makes an access request easier to answer?
Specify the account, data category, date range and desired format.
Check the current rule
Last reviewed: 10 August 2026