Reference

How we handle your data

We keep account details, login records, device signals and cookie settings in one place so you can see how your profile is handled.

Account recordsCookie settingsUPI recordsLocal law
metabets How we handle your data
REQUEST PATHS

Simple ways to reach us

If you want a copy of your stored details, a correction, or a deletion request, start from the help form inside your account or send a message from the email linked to…

Help form Send your access, correction, or deletion request from the form in your account. We use the details there to find your records and confirm the right person is asking.
Email desk If you prefer email, write from the address linked to your account. That helps us verify identity before we share stored data or make a change, and it gives you a written trail.
Follow-up message When a request needs more checks, we reply inside the account inbox with the next step and the fields we need to complete the action. We keep the thread on file.
DATA CARE

How we protect your records

We handle privacy by limiting collection to what your account needs, logging access to sensitive records, and using cookies only for session control, language choice and error checks.

Collection

We collect only what your account needs: name, contact route, login history, device signals and payment references linked to UPI, Paytm or PhonePe. That helps us run the account, answer requests and check misuse.

Cookies

Some cookies keep you signed in and remember the last screen you used; others help us spot broken pages or repeated failed logins. You can change browser settings, though some parts may not load the same way.

Security

We ask for identity checks before profile changes or wallet requests, and we store sensitive records with access controls. If a login looks unusual, we can pause the session and ask you to confirm.

Retention

We keep records only as long as needed for account use, dispute handling, fraud checks, tax or legal duty. After that period, we delete or anonymise them in line with our internal schedule.

Requests

You can ask for a copy, correction, restriction or deletion by sending a message through support. We may need a verification step so we do not hand records to the wrong person.

Changes

If we change this page, we update the date here and apply the new text from that point forward, unless a law or active account matter needs the older terms to stay on file.

Questions about your privacy rights

These answers cover the requests we see most often: what we keep, why we keep it, who can see it, and how you can ask us to update it. If your question is about a record that links to UPI, Paytm or PhonePe, we will check the account first and then handle it under the same policy rules.

We collect the details needed to set up and run your account, such as your name, contact route, login logs, device signals and any support message you send. We keep only what we need for the stated purpose.

Cookies help us keep you signed in, remember session choices and spot broken pages or repeated failed logins. Some are required for the page to work, while others help us measure technical errors and fix them.

Yes. Where local law permits, you can ask for a copy, correction or deletion after we verify the request. Send it through your account help form or the email linked to your profile.

We keep records only as long as needed for account use, dispute handling, fraud checks, tax duties or other legal duties. After that, we delete or anonymise them according to our internal schedule.

Payment references tied to UPI, Paytm or PhonePe stay with the account record so we can match incoming and outgoing wallet entries and answer later questions. We do not publish those details and we keep them only as needed.

Only staff with a clear task and the right access can open your records. We log that access, keep it limited by role and review unusual activity so the same record is not used without a reason.

If we change the page, we replace the text here and mark the update date. When a legal rule needs a different approach, that rule applies first and we note the change in the account thread if needed.