App / Live
Your relationship with gebiar4d is governed by clear terms — covering what we collect, how your account data is handled, and the rights available to you. Access to this platform depends on local law and is available where eligible regions permit.
When you open an account with gebiar4d, you enter into an agreement that covers how your personal data is stored, how wallet transactions through OVO and GoPay are processed, and the conditions under which your account remains active. We collect only what is needed to operate your account — login credentials, wallet identifiers, and session activity. We do not sell this data to third parties or use it for purposes outside account management and service improvement. Your information is retained for the period your account remains open and for a reasonable period afterward as required by applicable policy. Any change to these terms will be communicated through your registered account contact, and you will have the opportunity to review the updated terms before they take effect. Access to gebiar4d and the enforceability of these terms depend on the laws of your jurisdiction. If any term conflicts with local law in your eligible region, the locally compliant version applies. Questions about specific terms can be raised through the support path described further down this page.
Transactions processed through OVO are subject to OVO's own service terms in addition to gebiar4d's policy. We record the transaction reference, not your full OVO credentials.
GoPay payments follow the same handling: gebiar4d stores the transaction result and your account balance update, not payment instrument details beyond what GoPay passes to us.
DANA deposits are logged in your account wallet history. The amount added is visible in your account dashboard after login; disputes on specific amounts are handled through support.
We retain account activity records for the duration your account is active. After closure, we keep the minimum required by applicable regional policy before deletion is carried out.
This policy applies to your direct relationship with gebiar4d — your account, the data you provide us, and the transactions you initiate through supported payment methods. It does not govern the internal policies of third-party payment providers, the rules of game studios such as Pragmatic Play or Habanero, or the laws of jurisdictions outside your eligible region. Knowing the boundary helps you direct questions to the right place.
Login credentials, session data, and account settings fall fully within this policy. We manage how this data is stored and who can access it on your behalf.
OVO, GoPay, and DANA transactions initiated from your account are covered to the point they leave our system. Once the transfer reaches the payment provider, their own terms govern completion.
Game titles from studios like Pragmatic Play, Microgaming, and Spadegaming are provided under separate licensing terms between gebiar4d and those studios. This policy covers your access to content, not studio terms.
External links, partner services, and payment processors operate under their own privacy and service policies. gebiar4d is not responsible for data handling on those platforms once you leave our environment.
You have concrete actions available to you at any time. You can review your account activity — including wallet deposits via OVO, GoPay, and DANA — directly in your account dashboard after login. If any recorded detail looks incorrect, you can raise a correction request through our support channel. We will review the record against our system log and respond with the outcome. Requests to update contact details follow the verification steps shown inside your account settings page; follow the fields and confirmation instructions displayed there. If you want to understand how a specific piece of your data is used, raise the question in writing through the support path and we will respond with a clear, specific answer. Response times depend on the nature of the request and current support load, but every written request receives a written response.
Open your account dashboard and check the transaction history section. All wallet activity — OVO, GoPay, DANA — is listed with date, amount, and reference number.
Go to account settings and follow the verification steps shown on screen to update contact information or wallet identifiers. The form shows which fields require re-verification.
Submit a written question through the support channel with the subject line referencing this policy. We will respond in writing with a direct answer specific to your account.
If you want a record of what data we hold on your account, contact support with your account ID. We will produce a summary of stored fields and their purpose.
Policy questions, account correction requests, and data inquiries all have a direct path. Use the channel that matches how urgent the issue is — live chat for time-sensitive account access questions, email for written policy requests that need a documented response.
Open the chat icon from any page after login. Live chat handles account access issues, wallet discrepancies with OVO or GoPay, and general policy questions quickly.
Send policy or data requests by email for a documented response. Include your account ID and a clear description of what you are asking so we can respond to the right record.
The help section inside your account dashboard covers the most common policy questions with step-by-step paths. Check there first for account settings, wallet terms, and correction steps.
Responsible data handling is part of every account interaction on gebiar4d. Here is how we approach the areas that matter most to you as an account holder.
We use session cookies to keep you logged in and to remember your wallet preferences between visits. You can review cookie settings in your browser. We do not use tracking cookies to build profiles for third-party advertisers.
Account access is protected by the credentials and verification steps you set during registration. Any change to login details requires confirmation through the method on file. If you notice unexpected access, contact support immediately via live chat.
Active accounts retain data for the life of the account. After a written closure request is confirmed, we keep only the minimum required under applicable regional policy and then remove the rest. The timeline is shown in your closure confirmation.
All data-related requests — corrections, deletions, or information requests — go through the support channel. We log every request and respond in writing so you have a record of what was asked and what action was taken.
These are the questions we see most often from account holders in Indonesia regarding data, rights, and how this policy works in practice.
Yes, but only to the part of the transaction that happens inside gebiar4d — the instruction you send, the balance update in your account, and the record we store. Once the transfer reaches OVO or GoPay, their own service terms apply to the payment processing side.
Log in and open your account dashboard. Your transaction history, wallet records, and account details are all visible there. For a full written summary of stored fields, contact support with your account ID and we will produce one.
Yes. Go to account settings and follow the verification steps shown on screen, or contact support in writing with the correct detail and your account ID. We check the record and confirm the outcome in writing.
After your closure request is confirmed, we retain only the minimum data required under applicable regional policy for the period specified in your closure confirmation. After that period, the remaining data is removed from active storage.
Access to gebiar4d depends on local law and is available only where eligible regions permit. If your region does not permit access, the terms that apply to you are those of your local jurisdiction. We recommend checking whether access is permitted before opening an account.
We send notification of any material change to your registered account contact before the update takes effect. The updated terms are posted on this page with the effective date. You can review them and contact support if you have questions about what changed.