Reference

Legal terms for Indian access

This page explains how freebitco handles legal access, data use, request records and account notices for India.

India accessData useCookie checksRequest changes
freebitco Legal terms for Indian access
CONTACT PATHS

How to reach us on legal

If you need a copy of stored data, a correction or a formal reply to a notice, use the contact path tied to your account.

Email request Write from the email on file, state the exact change you want and attach any proof that matches your profile. We use that record to verify the request and reply with the next step.
Support form Use the form when you want a dated ticket number. It keeps your message attached to the right account and helps us separate data, access and correction requests from routine support mail.
Postal notice If a notice must be signed or sent by post, include your account identifier and the action you want. We handle it as a formal request and answer through the same channel or by email.
RECORD CARE

How we handle records

We keep legal records only for as long as needed to answer requests, meet the duties that apply where you live or resolve a dispute.

Data use

We use account details to confirm identity, answer legal requests and keep a clean record of what changed. Those details are not used for unrelated messages or copied into new files without a reason.

Cookies

Cookies store sign-in state, language and the route of a request. You can clear them in your browser, though that may make you sign in again before we can process a new request.

Account security

Before we alter protected details, we may ask for a fresh email check, matching device data or another proof step. That check helps stop someone else from changing your record.

Retention

Request logs, change history and consent records stay only for the period needed by law or to settle a dispute. After that, we remove or archive them under our record schedule.

Change requests

Tell us the exact field, the new value and the reason for the change. Clear requests move faster because we can compare them with the record and avoid back-and-forth.

Contact path

For anything tied to your legal record, write from the email on file so we can match the request to your account and reply in one thread.

Common questions about legal access

This section answers the requests we see most often from India accounts: how to ask for your data, how to correct a detail, what happens if local law changes and which contact path we use. If you send a request, we may need to verify the account first so we do not change the wrong record. Keep your message short, specific and tied to one request.

Write from the email on file, say you want a copy of your stored data and include your account name. We verify the request first, then send the record or explain any legal restriction that applies.

Yes. Send the exact field, the correct value and one line on why it needs changing. If we can match the request to your account, we update the record and confirm what changed.

Tell us through the in-account contact route and add another proof of control we can compare with the profile. If we still cannot match it, we may have to decline the request for safety.

We keep them only as long as needed to answer the request, meet duties that apply in your area or resolve disputes. After that, we remove or archive them according to the record schedule.

No. Cookies help with sign-in state and request routing. They do not cancel your rights, and you can clear them in your browser, though the site may ask you to sign in again.

Use the contact path listed on this page and send the notice from the email linked to your account. If the message needs formal handling, add your account identifier and the exact request.

If local law changes, we follow the new rule for the affected region and update the wording here. Until then, the current text applies only where local law permits access.