Reference

Privacy Policy for your 4rabet account

4rabet keeps this Privacy Policy focused on the account data, device signals, cookie choices and payment records linked to UPI, Paytm, PhonePe and Google Pay.

Account dataCookie choicesUPI recordsIndia accessData requests
4rabet Privacy Policy for your 4rabet account
CONTACT ROUTES

Three privacy contact paths at 4rabet

Privacy requests need a clear route, not a vague mailbox. Use the path that matches your need: account chat for quick checks, email for documents, or the account settings area for small edits. We may ask you to confirm account ownership before sharing, changing or deleting data, because privacy support should protect the account as well as answer the request.

Team online

Account chat

Use in-account chat when you need to ask what personal data is linked to your profile, wallet records or device session. We may request a simple ownership check before discussing any account-specific data.

Privacy email

Email the privacy team for export, correction or deletion requests that need a written trail. Include your account name, registered contact detail and the exact data change you want us to check.

Profile settings

Your account settings let you update basic contact details and communication choices without waiting for a support reply. Some fields may be locked while identity, fraud or payment checks are active.

DATA CONTROLS

Six controls behind our privacy work

We handle privacy through everyday account operations: sign-in checks, payment matching, cookie control, access logs, retention checks and support replies.

Account data

We collect details you provide during account creation, sign-in and support contact. That can include your name, contact detail, account ID, language choice and security events tied to your login activity.

Payment records

UPI, Paytm, PhonePe and Google Pay references are stored with wallet activity so deposits, withdrawals and refunds can be matched. We keep only the record needed for reconciliation, disputes and legal checks.

Cookie choices

Cookies help keep you signed in, remember language choices and measure page errors. Where choice is offered, your selection is saved so we do not ask again on every visit.

Security logs

We record device, IP, session and failed-login signals to detect account misuse. These logs help us check suspicious access and confirm whether a privacy request came from the account holder.

Retention checks

Some data can be changed or deleted quickly, while payment, fraud or dispute records may need to stay longer. We explain the reason if a legal duty prevents immediate removal.

Request handling

When you ask for access, correction, export or deletion, we log the request, verify ownership and route it to the right team. We reply with the action taken or the reason for refusal.

Privacy questions before you open an account

These answers explain how the Privacy Policy applies to your account before and after you join. They cover data collection, payment records, cookies, account access and request handling. If your question is account-specific, contact us through chat or email so we can verify ownership and give a reply tied to your records.

We collect data you provide during account creation, sign-in, wallet use and support contact. This may include contact details, account identifiers, payment references, device signals, cookie choices and security logs connected to your activity.

Payment references help us match wallet activity to your account, check failed or delayed transfers, handle refunds and respond to disputes. We keep these records only as needed for reconciliation, security and legal duties.

Yes, you can ask for an export of personal data linked to your account. We will verify ownership first, then provide data that can be shared without exposing security systems or another person’s records.

Use account settings for editable fields, or contact privacy support if the field is locked. We may request proof or an ownership check before changing details tied to payments, identity checks or account security.

You can request deletion through privacy email or account chat. We will remove data where allowed, but some records may remain for payment disputes, fraud checks, tax records or other legal duties.

Cookies support sign-in, language settings, session safety and page performance checks. Where cookie choice is available, we store your selection and apply it on later visits from the same browser when possible.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests can still be made through the contact paths listed in this policy, subject to ownership checks.