Reference

Privacy Policy for your 1miba account

Your account data, UPI, Paytm and PhonePe records, cookie choices, and privacy requests are handled under this Privacy Policy.

Account data clarityUPI record handlingCookie choice detailsPrivacy contact paths
1miba Privacy Policy for your 1miba account
HELP CHANNELS

Three ways to reach privacy support

Privacy requests need a clear route, so we keep them separate from ordinary account chat where possible. You can ask about correction, access, deletion, consent choices, cookies, or payment record handling.

Email privacy desk Send privacy questions to the email shown in your account area with your registered mobile number masked where possible. We use email for access copies, correction requests, deletion questions, and longer replies that need a written trail.
Live chat privacy routing Open live chat and ask for privacy support if you need help finding the right contact path. Chat can confirm the request type, but sensitive account changes may move to email after identity checks.
Account security check If you think your account data, login, or wallet record has been exposed, contact support from your account area. We check recent access, device changes, payment activity, and privacy settings before suggesting the next step.
DATA CARE

Six privacy controls we maintain

We treat privacy work as part of account operation, not an afterthought. That means payment records, support chats, cookies, device signals, and lobby activity each have a reason for being collected.

Account data use

We use your name, mobile number, email, login records, and account choices to maintain access, answer support queries, and protect your wallet. We avoid asking for extra personal data unless a check requires it.

Payment record handling

UPI, Paytm, PhonePe, and Google Pay records are used to match deposits, verify withdrawals, handle disputes, and meet audit duties. We do not display full payment identifiers in ordinary support replies.

Cookie choices

Cookies help keep you signed in, remember language choices, detect unusual sessions, and measure page errors. You can clear browser cookies, though some account safety checks may ask you to verify again.

Security logging

We record device type, IP range, session time, and failed login attempts to spot account misuse. These logs help us protect your wallet and investigate privacy concerns without relying on guesswork.

Retention periods

We keep data only for account operation, payment checks, dispute handling, legal duties, and security needs. When a record is no longer required, we remove it or reduce it so it no longer identifies you.

Change requests

You can ask us to correct, access, or delete eligible account data. Some payment and security records may need to remain for lawful checks, and we will explain that limit in our reply.

Privacy Policy questions answered

These answers explain common privacy requests in plain language. They cover what we collect, how payment records are handled, when cookies matter, and how you can contact us. For account-specific action, we may ask you to verify control of the account first.

It covers data linked to your account, including contact details, login records, device signals, payment references, support messages, cookie choices, and activity needed to operate your wallet and account safety checks.

We share data only where needed for payment processing, fraud checks, technical hosting, support tools, audits, or legal duties. We require service partners to handle the data for the stated purpose only.

Payment records are matched to your wallet, checked for disputes, and restricted to staff or partners who need them. Full identifiers are not used in routine replies, and access is logged for security.

Yes, you can ask for access through the privacy contact path in your account area. We may verify your identity first, then send eligible data in a format that can be read clearly.

You can request deletion of eligible data, and we will confirm what can be removed. Some records may need to stay for payment disputes, fraud checks, audit duties, or legal requirements.

Cookies keep sessions working, remember choices, detect errors, and support account security checks. If you clear cookies, you may need to sign in again or complete an extra verification step.

Yes. Account access, data handling, and eligibility depend on local law and are available where local law permits. If a local rule limits a request, we explain the reason when replying.