Reference

Open g15 legal terms for India

We keep the legal side clear: how you use your account, how we handle data, and how you send formal requests are all set out here on g15.

Local lawData handlingRequest routes
g15 Open g15 legal terms for India
REQUEST ROUTES

Browse contact paths for legal requests

If you need help with a consent change, record request, or access question, contact us from the account area so we can match the message to the right record.

Account email Send the message from the email linked to your account so we can verify it without extra back-and-forth. Include the request date and the exact change you want, and we will route it to the right team.
In-account form Use the form inside your account when you want a correction, deletion request, or a copy of stored records. It helps us log the request in the right place and keep a clear trail.
Formal notice For matters that need a signed notice, use the mailing path listed in your account footer. We compare it with the account record before we process any change or reply.
DATA HANDLING

Switch on data handling and records

We keep this area focused on how we store, use, and update your legal records. Cookies help us remember session state and request flow, while account security checks reduce the chance of…

Data use

We use only the details needed to run your account, check payments, and handle notices. That includes contact data, transaction logs, and request history. We do not treat anything outside the account record as a source for changes.

Cookie settings

Cookies keep you signed in, preserve the language you chose, and remember whether a form is half-finished. They also help us detect repeated logins from the same device, which supports account protection.

Security checks

If a request changes email, name, or withdrawal routing, we ask for a fresh check from the account holder. That extra step helps stop unauthorised edits and keeps the record aligned with the person who controls it.

Retention

We keep legal and payment records for the period needed to settle disputes, confirm transfers, and meet regional retention rules. After that, we remove or mask details that no longer need to remain visible.

Change requests

You can ask for a copy, correction, or deletion of stored details through the contact path in your account. We confirm identity first, then act only on items that the law allows us to change.

Contact trail

Every notice is logged with a time stamp and the account linked to it. That trail lets our support team show what was requested, when it arrived, and how the reply was sent.

Open legal answers for common requests

These questions cover the practical parts of our legal handling: what we collect, how long we keep it, and how you ask for a change. If something in your region changes, the version inside your account is the one we follow for that area. For anything tied to identity or payment records, we may ask for a fresh check before we act.

It sets out how we handle account use, data, notices, and region-based access. It is the page to check when you want the terms that shape your account record and request process.

Yes. Access depends on local law and is available where local law permits. If a region has different rules, the terms shown in your account area for that region are the ones we follow.

We keep the details needed to run the account, verify payments, handle requests, and maintain a record trail. That usually includes contact details, transaction logs, and the history of changes you ask for.

Yes. Send the request through the contact path in your account and include enough detail for us to identify the record. We confirm the sender first, then change or remove only what the law allows.

Cookies help the site remember your session, language choice, and form progress. They also support account security by spotting repeated sign-ins and keeping the request path stable while you move around the page.

We keep records for as long as we need them to manage the account, settle disputes, and meet regional retention rules. After that period, we remove or mask data that no longer needs to stay visible.