Reference

Privacy Policy for gama567 in India

This page explains how we collect, use, share, and keep your data when you open an account, log in, or send a support request at gama567.

IndiaData useCookiesAccount security
gama567 Privacy Policy for gama567 in India
REQUEST PATHS

Where to send policy requests

If you want a copy of your record, a correction, or a question about how your data is used, send it through the same channel you use for account help.

Account form Use the form inside your account for correction, export, or deletion requests. We match it to your profile before making any change so the request stays attached to the right record.
Privacy email Send a clear message if you need a policy question answered in writing. Include the mobile number or email on the account so we can locate the record quickly.
Live chat Chat works well when you want a fast route for a privacy question. We can log the request there, check the details, and move it to the right team.
SECURITY CONTROLS

Cookies, access and retention controls

We treat privacy controls as part of account care, not a side note. Cookies keep you signed in and help us remember language or page settings; security logs help us spot suspicious…

Data we collect

We collect the account details you enter, the device and session signals needed to keep access secure, and the payment reference used for verification. We do not ask for extra data unless a request or law requires it.

Cookie use

Cookies remember your session, language choices, and page settings, and they help us spot repeated failed logins. You can clear them in your browser, though some pages may ask you to sign in again.

Login security

Use a strong password and keep one-time codes private. If we see unusual activity, we may ask you to confirm the login before the session continues, which helps stop account misuse.

Data sharing

We share only the minimum data needed with hosting, support, payment, or verification partners. They handle it under contract and may use it only for the task we sent it for.

Retention

Record keeping follows the purpose of the data. We retain logs and transaction references for support, dispute handling, fraud checks, and legal duty, then remove or anonymise them when they are no longer needed.

Change requests

You can ask for correction, export, or deletion where local law permits. We may ask for proof so we do not change the wrong account, and we confirm the result once the request closes.

Questions about this policy

These questions cover how the policy applies to your account, what we keep, and how you can ask for changes. If a request depends on local law, we will say so before we act. The aim is simple: you should know what we collect, why we keep it, and how to contact us when something needs updating.

It covers the data linked to your account, device, session, and support requests. It also explains when we share records with service partners, when we keep them, and how you can ask for changes where local law permits.

We keep the details you enter for account use, the security logs created when you sign in, and the payment references that help us verify a transaction. We avoid collecting extra data unless we need it for a clear purpose.

Cookies help us remember your login, page settings, and language choice, and they help us spot repeated failed sign-ins. If you clear them, some settings may reset and you may need to sign in again.

Yes, where local law permits. Send the request through the contact path on this page, tell us what needs changing, and we will verify it before updating, exporting, or removing the record.

Only staff and service partners who need it for hosting, support, verification, or payment handling can access the minimum necessary data. They are bound to use it for that task only.

We use access controls, session checks, and internal logging to reduce misuse. We also limit retention to the period needed for the stated purpose, then remove or anonymise the record.