Reference

Open dpbooss Privacy Policy

This page explains how we use account details, session logs, and payment traces on dpbooss.

Account detailsCookie usePayment tracesLocal law
dpbooss Open dpbooss Privacy Policy
REQUEST ROUTES

Open Contact Paths For Requests

For access, correction, or a deletion request where local law allows, reach us through the channels below.

Email request Send your registered email, phone number, and the exact change you want. That lets us locate the right record faster and reply with the next step for access, correction, or a deletion request where law permits.
In-app chat Use chat from your account if you want a quicker route for cookie changes, login concerns, or a copy request. We will ask for a short verification step before we handle the record.
Web form Use the form when you need a written trail for your request. Add your account ID, the date range you mean, and the reason for the change so we can process it without delays.
DATA GUARDS

Switch On Data Safeguards

Our handling keeps account records, payment traces, and support logs in separate buckets so requests can be checked cleanly.

Data handling

We limit access to staff who need the record for support, payment checks, or legal handling. That reduces unnecessary exposure and keeps the path from account creation to request handling clear.

Cookie use

Cookies remember your session, language choice, and sign-in state. They also help us spot repeated failed logins and unusual device shifts, so we can ask for extra verification before a request is processed.

Account security

When you change your password or sign in from a new device, we may log that event and compare it with past access. If something looks unusual, we can pause the session and ask you to confirm it.

Retention period

We keep records only for the period needed for service, fraud checks, disputes, and legal duties. After that window ends, eligible records are removed or masked according to the rules that apply to that record type.

Request path

To ask for access, correction, or a change to consent settings, send a clear request with your registered details. We use those details to verify the account and match the record to the right team.

Local law

If a request touches age rules, tax records, or payment checks, the local law in your region decides what we can share or change. Where law permits, we will explain the next step plainly.

Open Privacy Questions Here

These answers explain how privacy requests work on dpbooss, what we keep, and when local law changes the result. If your request concerns access, correction, deletion, or a consent change, use the contact paths above and include enough account detail so we can verify the record and reply clearly.

We keep the details you submit for account setup, plus device and session logs that help with sign-in, fraud checks, and support. We use only what we need for service, security, and legal duties.

Cookies help us keep you signed in, remember language choices, and track whether a page or form is loading properly. They also help us spot repeated failed logins, so we can add another check if needed.

Yes. When you use UPI, Paytm, or PhonePe, we may keep the reference code, amount, time, and result of the transfer. That record helps with reconciliation, disputes, refunds where allowed, and audit duties.

We keep records only as long as they are needed for service, dispute handling, fraud checks, tax duties, or other legal duties. After that, eligible records are removed or masked under the rule that applies.

Yes. Send a clear request with your registered details and tell us what you want changed. We use that to locate the record, verify the account, and respond with the next step.

If a request touches local law, payment checks, or a legal hold, we may not be able to change every record. We will still explain what can be altered and what must remain.

Use email, in-app chat, or the web form, and include enough account detail for us to verify you. If you are asking about access, correction, or deletion, say that plainly in the first line.