Sports / Live
Your information — from the details you enter at registration to the wallet transactions you make via OVO, GoPay, or DANA — is handled under this Privacy Policy. We set out here exactly what we collect, how we use it, and what choices you have.
This Privacy Policy applies to all data you share with majapait4d when you create an account, access the lobby, or connect a payment method such as OVO, GoPay, or DANA. We collect registration details — your name, contact address, and account credentials — along with transaction records generated when your wallet processes a deposit or withdrawal. Session data, including device type and browser behaviour, is logged to keep your account consistent across Android and iOS. We do not sell your personal data to third parties, and we do not share it with external organisations except where required to process a payment through a verified local rail, fulfil a legal request, or protect account security. Data you provide during account verification is retained for as long as your account remains active and for a defined period afterwards, as required by applicable rules in eligible regions. Where we use cookies or similar tracking on our platform, the purpose is functional — keeping you logged in, remembering your lobby position — not advertising profiling. You may withdraw consent for non-essential data uses at any time by contacting our support team. Availability of this service depends on local law and is accessible only where local regulations permit.
Wallet transaction records tied to your OVO deposits are logged for account reconciliation and are not shared beyond what payment processing requires.
GoPay payment data is handled under the same retention rules as all wallet transactions — accessible to you through your account history page.
DANA transfers appear in your transaction log. You can review the full record after login without contacting support for standard queries.
Login credentials are stored in hashed form. We do not have access to your plain-text password, and neither does our support team.
Not every part of your experience with majapait4d falls under the same data rules. This section draws a clear line between what this policy covers and what sits outside it, so you know exactly where our obligations begin and end.
Your registration data, login sessions, and account settings are fully within scope. We control and are responsible for how this data is stored and used on our platform.
Deposits and withdrawals processed via OVO, GoPay, or DANA generate records we hold. The payment provider's own privacy terms also apply to the portion of the transaction they handle.
Your in-session activity — which games you open, how long a session runs — is logged for account security and functional purposes. This data is not used for targeted advertising.
Links to external sites or third-party tools not operated by us fall outside this policy. We have no control over how those services handle your data once you leave our platform.
You have concrete options for reviewing, correcting, and querying the data we hold on your account. These are not abstract rights — each one has a clear path you can follow right now. Start with your account dashboard after login: the transaction history shows every wallet entry, and the profile section lets you update contact details directly without needing to reach support. For anything that cannot be changed from inside the account — such as a correction to identity information submitted during verification — submit a request through our support channel and include the account email you registered with. If you want to know what data we hold beyond what is visible in the dashboard, that query goes to the same support route. Requests are reviewed in the order they arrive. Where local law in your eligible region grants additional rights over your personal data, those rights apply on top of the steps described here.
Log in and open the transaction history tab. Every OVO, GoPay, and DANA entry is listed there with date and amount — no support request needed for standard account queries.
Update your email, contact number, or notification preferences directly from the profile section in your account dashboard.
For data held outside the dashboard view, contact support with your registered email and a description of what you need. We will confirm receipt and respond through the same channel.
Where applicable under local law in your region, you can request correction or deletion of specific data. Submit this through our support email route for processing.
Privacy queries have a dedicated path. Use the channels below to reach our team — include your registered account email in every message so we can match the request to your record.
Send your privacy or data request to our support email address listed in the Contact section of your account dashboard. Include your account email for faster matching.
The live chat option is available from the account dashboard after login. Use it for questions about what data is visible in your account or how to update profile details.
Most data actions — viewing transaction records, updating contact details — are handled directly inside your account without needing to contact us. Start there before submitting a formal request.
Our data handling practices are built around four areas: what we store, how long we keep it, how it is protected, and how you can request changes. Account credentials are hashed at storage — no plain-text password is held or readable by our team. Session tokens expire after inactivity to reduce exposure if a device is left unattended. Retention periods follow the requirements of applicable rules in the eligible regions where this service operates.
We use functional cookies to keep your session active and remember your lobby position. Non-essential cookies require your consent, which you can withdraw via the cookie settings accessible from the account area.
Credentials are stored in hashed form. Session tokens are tied to your login event and expire on inactivity. You can end all active sessions from your account security settings.
Transaction records and account data are kept for as long as your account is active and for a defined period after closure, as required in eligible regions. The current retention period is shown in your account settings.
To correct data we hold, or to ask what specific records we retain, contact our support team via email or live chat. Every request is logged and handled through the same account-matched process.
These are the questions about data handling that come up most often. If your question is not here, use the live chat or email route in the support section above.
We collect the details you enter at registration — name, contact email, and login credentials — along with transaction records generated when you use OVO, GoPay, or DANA. Session data such as device type is also logged for account security purposes.
Transaction records and account details visible in your dashboard are available immediately after login. For data held outside that view, submit a request to our support team with your registered email and we will confirm what records are linked to your account.
We share data only where necessary — with payment providers like OVO, GoPay, or DANA to process a transaction, or where required by applicable law. We do not sell personal data to marketing companies or external organisations for profiling purposes.
Contact details and notification preferences can be updated directly from the profile section of your account dashboard. For identity information submitted during verification, contact support with your account email and the specific correction needed.
Account and transaction data is retained for a defined period after account closure as required in your eligible region. The current retention period applicable to your account is shown in the account settings section after login.
Non-essential cookies can be managed from the cookie settings in your account area. For other non-essential data uses, contact our support team via email or live chat — include your registered account email and specify which consent you want to withdraw.