Reference

Legal terms for your d8bqm account

We keep the rules for access, data use, request handling and account changes in one place, so you can check what applies before you open anything or ask…

Local lawData useAccess rulesRequest changes
d8bqm Legal terms for your d8bqm account
CONTACT PATHS

Where to send legal requests

Use the route that fits your request. Written requests help us handle access, correction, deletion and complaint records in one queue, while account-area forms let us tie the message to the right…

Email Write to us when you want the legal team to check an access, correction or deletion request. Include the account contact you use on d8bqm and the rule or record you want us to handle.
In-account form Use the form in your account area if you need us to update a detail, confirm a record, or explain a policy change tied to your profile. It gives us the context faster than a plain message.
Postal route If you need a signed letter trail, send the request by post using the address shown on your account page. We keep it for disputes, audit checks and any mandatory record-keeping period.
DATA AND ACCESS

How we handle data and access

We keep the legal side of the account tidy by limiting who can see your data and by logging changes that affect access.

Data use

We use the details you submit to run your account, check requests and keep legal records tied to access or…

Cookies

Cookies help us remember your session, keep forms from resetting and spot repeated sign-in attempts.

Account security

Use a password you do not reuse elsewhere and keep your phone secure if you rely on one-time codes.

Record keeping

We keep request records only for as long as the law, dispute handling or audit work requires.

Change requests

If you want to correct, erase or export a detail, send the exact field and the updated value.

Contact route

For any legal query, use the channel in your account page first.

Questions on rights and access

These answers explain how legal requests work on our side, what we may need from you and when local law changes the result. If your case is unusual, send the exact record, date or page so we can check the rule that applies before we reply.

Indian law applies first, and any narrower state rule or court direction can sit above it. If a feature is not allowed where you are, we keep it unavailable rather than push you toward a route that conflicts with the rule set.

Yes. Send the exact detail you want to see, correct or erase, and we will check whether we can act on it. Some records must stay for tax, dispute or fraud-control reasons, so the result can vary by request.

Tell us the field, the old value and the new value. Clear requests move faster, and we may ask for proof if the change could affect access, payments or another legally sensitive record.

Cookies do not change the legal position, but they do help us keep you signed in, remember the form state and spot repeated sign-in attempts. You can clear them in your browser if you want.

We update the affected text or feature when the legal position changes, then apply the stricter rule until the page is refreshed. That keeps access aligned with the latest requirement without guessing.

Use the channel listed in your account area and include the page, record or date that matters to you. That lets us route the request quickly and reply with the right person or next step.

Yes, where local law allows. We may need to confirm your identity first, then we send the file or explain why a record must stay private, restricted or partially redacted.