App / Casino
567db built this policy so you know exactly what information we hold, why we hold it, and what you can do about it. Access to our platform and its features depends on your local law and eligible regions.
When you open an account with us, we collect the information needed to run that account — your registration details, login activity, transaction records from payment methods such as Rocket and Upay, and how you navigate the platform from your device. We use this data to operate your account correctly, process wallet activity, and respond when you contact support. We do not sell your personal information to third parties for their own marketing use. Data shared with payment processors — including mobile wallet services — is limited to what those processors need to complete a transaction. We retain account records for as long as your account is active and for a period afterward as required by the obligations that apply to us in the regions where we operate. If you close your account, we will tell you what we keep and for how long. Your data is stored on secured infrastructure; access within our team is role-restricted to staff whose work requires it. Any change to this policy will be reflected in an updated version here, and continued use of your account after a change constitutes acknowledgement of the revised terms.
Transaction data passed to Rocket is limited to what the payment process requires. We do not store your full wallet credentials on our platform.
When you use Upay, the transfer record is held in your account wallet history. You can review that history from the transactions section after signing in.
Registration details, login timestamps and support conversations are retained under this policy. You can request a summary of what we hold by contacting our support team.
We collect standard device and browser signals to keep your session secure and to show the platform correctly on your screen. This is not linked to third-party advertising.
This policy applies to your use of 567db — the account you hold, the sessions you start and the transactions you make here. It does not govern what third-party payment processors, studios or external services do with information once it leaves our platform. Read each third-party provider's own terms for those details. Availability of any feature described here depends on your local law and the eligible regions we serve.
The account registration process, login activity and the personal details you submit when opening or updating your account fall fully within this policy.
Wallet deposits and withdrawals processed through Rocket or Upay are covered on our side. The payment provider's own privacy terms apply to what happens within their network.
Pages, game titles and promotional notices published on this platform are governed by our terms of use. This privacy policy specifically covers personal data, not content rules.
Links to external services, studio platforms or payment gateways leaving this site are outside our policy scope. We do not control and are not responsible for how those services handle your data.
You have real, usable choices about the data we hold. The most direct route is your signed-in account page — from there you can review the personal details on file and update anything that has changed, such as a new phone number or a corrected name spelling. If something looks wrong and you cannot edit it from the account page, our support team can make the correction after verifying your identity. You can also ask us what data we hold by raising a written request through the support channel; we will respond with a clear account of the records tied to your profile. Deleting your account is handled through the same support route — tell us you want to close the account and we will walk you through what gets removed, what gets retained and for how long. None of these steps require a phone call; our chat and email routes handle them without you needing to visit anywhere in person.
Sign in and open the account details section to see the information we hold. Most fields are visible there without needing to contact us.
Edit directly from the account page where fields allow it. For fields that cannot be self-edited, raise a correction request through support and we will action it after identity confirmation.
Send a written request via our support channel. We will reply with a structured account of the personal data linked to your profile — no form required, just a message.
Contact support to start the account closure process. We will confirm what data is deleted immediately and what is retained under our legal obligations.
Every question about your personal data — what we hold, how it is used, or how to correct it — can be raised through the support routes published on the site. There is no separate privacy hotline; the same channels that handle account help also handle data questions. Use the route that suits you and include your registered account details so we can locate your records without delay.
Open the chat widget on any page while signed in. Describe your data question and our team will either answer directly or escalate to the relevant team member.
Send your question to the support email address listed in the contact section of the site. Include your account username so we can find your records and respond accurately.
The help and support section of your signed-in account lists the current contact options. This is the place to check if you are unsure which route to use for a data request.
Our approach to data handling is straightforward: collect what the account needs, restrict who can access it, and keep it only for as long as the account and our obligations require. Cookies on the platform are used for session management and to keep the interface working correctly on your device — not for cross-site advertising profiles. Account security is layered: your password is stored in a hashed format and login activity is logged so unusual access patterns can be flagged. When you transact through Rocket or Upay, the data exchange with those processors is limited to what the payment step requires. We review our data practices periodically; if the policy changes in a way that affects your rights, the updated version will appear on this page.
Cookies here serve session management and correct page rendering on your device. You can manage cookie preferences through your browser settings without losing account access.
Passwords are hashed before storage. Login timestamps are kept so that if you ever flag an access concern, we have a record to investigate with you.
We keep your data while your account is active and for a further period tied to our operational obligations. Account closure starts the removal process; support will clarify exact timelines.
When this policy is revised, the updated version replaces this page. Continuing to use your account after the update is published signals that you have read the revised terms.
These are the questions we hear most often about how 567db handles personal data. If yours is not here, the support routes in the section above are the right next step.
We collect the details you enter during registration — name, contact information and the credentials used to secure your account. We also log device and session data to keep your account working securely. Nothing beyond what the account process requires is collected at registration.
Transaction data passed to Rocket or Upay covers only what the payment step needs. We record the transaction outcome in your account wallet history, but we do not store your full wallet credentials. The payment processor's own privacy terms govern what happens on their side of the transfer.
Yes. Sign in and open your account details page for the information stored there. For a broader summary of everything we hold, send a written request through live chat or email support — include your username and we will compile the relevant records for you.
For fields you can edit yourself, the account details section is the direct route. For details that cannot be self-edited — such as a name correction — raise the request through support after signing in. We will confirm your identity and make the change on our end.
Data is shared only to the extent the service requires it. Game studios receive session data needed to run a game; payment processors receive the data needed for a transaction. We do not sell your personal information to third parties for their own commercial use.
Contact support to start the closure process. Some data is deleted immediately; other records are retained for a further period to meet our operational obligations. Support will confirm the specific categories and timeframes that apply to your account before closure is finalised.