Reference

dfabet legal terms for India

We keep our legal terms, data use, cookie rules, and account-request steps in one place before you open an account.

Clear termsLocal-law checksData and cookiesAccount requests
dfabet dfabet legal terms for India
CONTACT PATHS

How to reach us on policy matters

For legal queries, use the contact route tied to your account so we can match your message with the right record.

Registered email Send requests from the email linked to your account when you need a record copy, a correction, or a question about stored data. We use that match to confirm identity before we act.
In-account chat Use chat for time-sensitive policy questions, access checks, or a change request. The team can see your account context faster there, which reduces back-and-forth and keeps the thread in one place.
Document desk If a verification step is needed, we may ask for a clear document scan or a fresh selfie match through the secure upload path. We only use it for the request you raised.
DATA AND ACCESS

How we handle legal requests

We keep legal requests tied to the account that raised them, because that is the safest way to handle data, access, and change requests.

Data use

We use account details, login records, and support history to verify who is asking and why. That helps us answer requests accurately and keep the legal record linked to the right account.

Cookies

Cookies help us remember session state, device checks, and language preferences while you move through the site. They also help us recognise repeated requests and keep the account path secure.

Account security

We compare the request with the registered email, chat thread, or document set before we change anything. If the details do not match, we stop and ask for a cleaner verification path.

Record retention

We keep only the records needed for legal duties, dispute handling, fraud checks, and audit logs. Once a record is no longer needed, we remove or anonymise it under the applicable retention rule.

Change requests

You can ask for a data correction, access copy, or deletion check from the same account path you use to contact us. We verify the request first, then apply the change if the law allows it.

Contact handling

Only the people who need the request for verification, record handling, or legal checks can see it. That keeps your message limited to the right team and avoids sharing beyond the task.

Your questions on access and data

These answers cover the parts of our legal terms that usually matter first: when access is allowed, what data we keep, how cookies work, and how you can send a correction or deletion request from India. If your situation depends on local law, that local rule applies, and the registered account path is the one we use to check it before we act.

You can open an account where local law permits access. If your state or country has a different rule, that rule comes first, and we may stop the process until the account fits the local requirement.

We keep the details needed to verify you, process requests, and maintain records for disputes or audits. That usually includes contact details, login history, and the support thread linked to your account.

Yes, if the change is allowed and we can verify the request from your registered email or in-account chat. We may ask for proof, then update the record and keep a note of the change.

Cookies help the site remember session state, language choice, and security checks. If you block them, some account actions may need extra verification, and a few parts of the site may not load as intended.

The message goes to the team that handles account records, access checks, and policy requests. We limit access to people who need it for the task, and we keep the thread tied to your profile.

You can ask for deletion, and we will check local law, retention duties, and any dispute record we still need. If full deletion is not allowed, we keep only the minimum required for the legal purpose.