Slots / Mobile
gtgt99 collects only the account and transaction data needed to operate your wallet, process payments through Rocket and Upay, and respond to your support requests. This policy maps exactly what we collect, why we hold it, and what choices you have — so you can decide with full visibility, not guesswork.
When you open an account with us, we collect the information you provide during registration — your name, contact details and the payment identifiers connected to your Rocket or Upay wallet. Beyond registration, we record session activity such as login timestamps, device type and the pages you visit inside your account. This data lets us verify your identity before processing a withdrawal, flag unusual account behaviour and deliver support when you raise a query through our contact route. We also collect technical signals — browser type, IP address and cookie identifiers — to keep your session stable across devices and to measure how our pages perform. None of this technical data is sold to third-party advertisers. Where a payment flows through a local rail such as Rocket or Upay, the payment provider receives only what it needs to complete that transaction; we do not share your full account profile with them. Data we collect is stored for as long as your account remains active and for a retention period after closure that satisfies the obligations we operate under in the regions where this service is available. Availability and the applicable data rules depend on your local law and the eligible regions covered by this policy. If you have questions about a specific data point held on your record, the support contact route in this page is the right place to start.
Not every part of your experience falls inside this policy in the same way. Some areas — like third-party payment processors or external links — operate under their own separate terms. Knowing what is inside and outside scope helps you understand exactly where our obligations begin and end, and where you should look for the relevant rules when they sit elsewhere.
All data collected when you log in, update your profile or change your account settings falls directly under this policy. That includes the device identifiers and session tokens generated during your visit. We control how this data is stored and for how long.
When you initiate a deposit or withdrawal through Rocket or Upay, the payment leg of that transaction is handled by the respective payment provider under their own privacy terms. We receive a record of the outcome; we do not process the payment data ourselves end to end.
Activity logs from your game sessions — which categories you opened, how long a session lasted — are held under this policy. We use these logs for account security and to respond to support queries. We do not share individual game logs with studios or third parties.
Any external site linked from our pages, including payment provider portals, operates under its own privacy rules. We do not control those policies and cannot speak to how third parties handle the data you give them directly. Always check the relevant policy at the point of handoff.
Your account record is not a closed file. Several actions are available to you at any point, and you do not need to wait for a specific trigger to use them. Reviewing what we hold, correcting inaccurate details and raising a question about how a particular data point was created are all straightforward steps. The process runs through your account settings page or through the support contact route described later in this policy — there is no separate form or waiting period before you can start. Eligibility for certain rights may depend on your local law and the eligible regions covered by this policy. Where a right is available to you, we aim to acknowledge your request within a reasonable period and to complete any correction or deletion that falls within scope. If a request cannot be completed — for example, because a retention obligation applies — we will tell you why and point you to the relevant part of this policy that explains the reason.
Open the account settings section after logging in to see the profile data we hold. You can check which contact details, wallet identifiers and device records are linked to your account at any time without contacting support first.
If a name, contact number or linked wallet identifier is wrong, update it directly in your account settings. Where a field is locked for security reasons, raise a correction request through the support contact route and we will guide you through the verification step.
If you want to understand why a specific data point was collected or how long it will be retained, send a written query to our policy contact address. Include your account identifier so we can locate the relevant record and respond with precision.
Closing your account ends active data collection. Some records are retained for the period required by the obligations we operate under; we will confirm what stays and for how long when you submit a closure request through the support route.
If this policy raises a question you cannot resolve through your account settings, three contact paths are published on the site. Each one routes to the same policy team, so pick the channel that suits how you are browsing at the time. We do not publish contact hours we cannot verify, and we do not promise a turnaround time we have not confirmed — but the routes below are live and monitored.
The live chat widget is visible in the footer of every page when you are logged in. Open it, select the privacy or data query category, and describe your question. This is the fastest route for straightforward corrections or scope questions.
For written privacy requests — data review, correction or closure — use the email address listed on the Contact page. Include your registered account identifier in the subject line so the request is routed to the policy team without delay.
The Help Centre, accessible from the account menu, contains published articles on data handling, cookie settings and session controls. Check there first; if the article does not answer your question, it links directly to the live chat and email routes above.
Account security and data handling sit at the centre of how gtgt99 operates its policy. Every access request to your account record is logged, and unusual patterns — multiple login attempts from an unfamiliar device, for instance — trigger an account alert rather than silent processing. Cookie settings can be adjusted through the preference panel in your browser or through the cookie notice that appears on first visit; withdrawing consent for non-essential cookies does not affect your ability to log in or complete a transaction.
We use essential cookies to keep your session active and non-essential cookies to understand how pages are used. You can adjust non-essential cookie consent at any time through the preference panel without affecting your account login or wallet access.
Login events, device changes and failed authentication attempts are all logged against your account. If a signal falls outside your normal pattern, we flag the event in your account activity record so you can review it directly without waiting for a support response.
Active account data is held while your account is open. After closure, we retain the records required by the obligations applicable to the eligible regions where this service operates. The retention period and what is kept are confirmed when a closure request is processed.
When this policy is updated, we publish a notice inside your account dashboard and update the version date at the top of this page. Continued use of the account after that notice constitutes acknowledgement of the revised terms, so check the dashboard periodically.
The questions below cover what real account holders ask when they read through this policy for the first time. If your question is not here, the support contact routes in the section above will get you to the right team.
We collect the name, contact details and payment identifiers you provide during registration — including wallet references for Rocket or Upay. We also log device type, session timestamps and browser signals each time you access the account. No data beyond what is needed for account operation and payment processing is collected.
When a transaction is processed through Rocket or Upay, the payment provider receives only the identifiers needed to complete that specific payment. We do not hand over your full account profile. Each provider operates under its own privacy terms, which apply to the data they handle on their side of the transaction.
Log in and open the account settings page — your profile data, linked wallet identifiers and device records are listed there. For a more detailed breakdown of session logs or historical records, send a written request to the email address on our Contact page and include your account identifier.
You can request account closure and data deletion through the support contact route. Some records must be retained for the period required by the obligations applicable to eligible regions; we will confirm exactly what is kept and for how long when your request is processed. Availability of full deletion depends on your local law.
We use essential cookies to maintain your login session and non-essential cookies to understand page performance. Non-essential cookies can be switched off through the preference panel in your browser or via the cookie notice on first visit. Turning off non-essential cookies does not prevent you from logging in or completing wallet transactions.
When we update this policy, a notice appears inside your account dashboard and the version date at the top of this page is updated. Check the dashboard periodically, especially after any communication from our team pointing to a policy revision. The current version is always the one published at this URL.