Reference

Your Privacy Terms at dafabc

This page sets out what we collect, why we use it, and how you can ask for changes on your account.

Data useCookiesRequestsIndia

What We Collect And Why

dafabc Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

We collect only the details that help us run your account, process supported payments, and answer privacy requests. That can include the contact fields you submit, basic device and session data, and wallet records linked to UPI, Paytm, PhonePe or Google Pay when you choose those

1
routes. We use cookies to keep sign-in stable, remember your choices, and spot unusual access. When we work with service providers, they receive only the data needed for the task and must handle it under our instructions. We keep records for as long as we need
2
them for account handling, dispute checks, tax duties, fraud checks, and other legal needs. If you ask for access, correction, or deletion, we will handle the request after verifying your account and after checking what local law allows in your region.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

REQUEST ROUTES

Where To Send Privacy Requests

If you want to ask about a privacy matter, use the contact path that matches your request.

HANDLING CONTROLS

How We Protect Your Data

This page is built around clear handling: we record what you submit, limit who can see it, and keep requests tied to the account that sent them.

Data we keep

We keep the contact and account details you provide, plus the minimum device and session records needed to run sign-in, support requests and payment checks. We do not keep more than the task needs.

Cookie use

Cookies remember your session, language, and privacy choices so you do not have to reset them every visit. We also use them to spot unusual access and reduce repeated logins.

Security checks

We protect account changes with verification steps before any sensitive update goes through. That includes password resets, withdrawal-related identity checks, and requests to change contact details or payment records.

Retention limits

We keep records only for the period needed for account support, dispute handling, tax duties, anti-fraud checks, and other lawful duties. After that, we remove or anonymise them where possible.

Sharing rules

When we work with payment, hosting or verification providers, they receive only the data needed for the task. We do not share anything just for convenience, and we keep contract limits in place.

Your request path

You can ask to see, correct, or remove details linked to your account. Send the request through support, we confirm it belongs to you, and then we act as local law allows.

Common Privacy Questions, Answered

These answers cover the main privacy requests: what we collect, how cookies work, who may receive the data, and how long we keep it. If you send a correction or removal request, we first confirm the account and then check the local legal position before we make any change. Payment-linked requests may need the matching trail from UPI, Paytm, PhonePe or Google Pay.

We keep the contact details, account data, device signals and session records you share when you open or use the account. If you use UPI, Paytm, PhonePe or Google Pay, we may also keep the payment trail needed for checks.

Cookies help us keep you signed in, remember privacy choices, and keep the page working the way you left it. They also help us spot repeated failed logins or unusual access from the same device.

Yes. Send the request through support, prove the account belongs to you, and tell us what you want changed. We handle the request within the limits of local law and our retention duties.

We keep records for account handling, dispute checks, tax duties, fraud checks and similar legal needs. When the reason ends, we remove or anonymise the data where our systems and local law allow it.

Only the teams and providers that need the data to run payments, hosting, verification or support may receive it. We do not pass it around casually, and every recipient is expected to follow our instructions.

Access depends on local law. If the service is not allowed in your region, we do not extend it there; if it is allowed, the same privacy terms apply to your account.

Your Privacy Terms at dafabc

Where To Send Privacy Requests

How We Protect Your Data

Data we keep

Cookie use

Security checks

Retention limits

Sharing rules

Your request path

Common Privacy Questions, Answered

01 What details do you collect from me?

02 Why do you use cookies on my device?

03 Can I ask for a copy or correction of my data?

04 How long do you keep my records?

05 Who can receive my details?

06 What if I am outside India?

Related Pages