Reference

Privacy Policy for your d5600 account

This page explains what we collect, why we use it, how long we keep it, and how you can ask for access, correction or deletion where local law…

Access rightsCookie useData retentionLocal law
d5600 Privacy Policy for your d5600 account
CONTACT ROUTES

How to reach us on policy matters

If you want to ask how we use data, request a correction, or raise a concern about cookies, you can contact us through the app chat…

In-app chat Send a message from your account area when you want a quick check on…
Email request Use the address shown in your account area for written requests about access, deletion…
Help form Our web form is useful when you want to attach a screenshot, note a…
SAFE HANDLING

How we handle privacy data

We store only the details needed to keep your account running, verify actions, and meet legal duties. Access is limited by role, and sensitive changes need extra checks.

Collection limits

We collect account, device, and session details only when they help us verify you, process actions, or reply to a request. We do not gather extra fields just to fill a database.

Cookie control

Cookies remember login state, page settings, and form progress. They also help us spot broken flows and reduce repeated checks, while keeping the data tied to your session rather than to public browsing history.

Account security

When a sensitive change is requested, we ask for a fresh verification step before updating the profile. That protects your account from edits made by someone who does not belong to it.

Payment records

If you move money through UPI, Paytm, PhonePe, or Google Pay, we keep the payment reference and status needed for reconciliation and support. We do not rely on those records for anything outside that purpose.

Retention rules

We keep records for the period needed for service, dispute handling, and legal duties, then remove or archive them. Where law asks for longer retention, we follow that rule and nothing more.

Your requests

You can ask for access, correction, or deletion of records tied to your account by using the contact paths on this page. We may ask for verification before making a change to protect the profile.

Privacy questions you may ask us

These questions cover the parts of our policy that matter most when you want to know what we store, why we store it, and how you can ask for changes to your account. If you are checking from India, the same terms apply wherever local law permits access. Keep this page handy when you want a quick answer before you contact us.

We may collect your name, mobile number, device details, session logs, payment references, and the messages you send us. We use those records to verify your account, keep access working, and handle requests tied to your profile.

Cookies help us remember your login state, language choice, and form progress. They also help us spot broken pages and repeated sign-in failures, so the site can keep the session linked to your browser.

Yes, where local law permits. Send a request through the contact path on this page and we will check the records linked to your account, then share what we can after verification.

We keep records only for the period needed to run the service, answer disputes, and meet legal duties. After that, we remove them or store them in a limited archive if the law asks us to keep them longer.

We may share only the data needed with service providers that help us host the site, deliver messages, or process payment checks. They do not get more than they need, and they cannot use it for unrelated purposes.

Use the contact route on this page and tell us which record needs to change. We may ask for verification before updating it, then we will correct the field and note the change in our internal logs.

Inactive records are still kept for the period required by law or dispute handling. Once that period ends, we remove or archive them so they are no longer used for account operations.