Reference

gbo4d Privacy Policy for India

This page explains how we collect, use and store account details, device signals and cookie data when you use gbo4d.

Account detailsCookiesLocal lawSupport contact
gbo4d gbo4d Privacy Policy for India
CONTACT ROUTES

Ways to Reach Our Team

If you want to ask what we hold, correct a detail or object to a record, use the channel that matches your account.

Live chat Use live chat from your account area for privacy questions, a copy of the data we hold, or a correction request. The chat route helps us verify you quickly before we move anything further.
Contact form Send a written request through the form when you want a clear record of your message, dates or attachments. It gives us the context we need to route your privacy request to the right team.
Email desk Use email when your request needs a longer explanation or documents that are easier to attach outside chat. We keep the message thread so you can track the request from start to finish.
DATA HANDLING

How We Protect Account Data

We keep this policy practical: collect only what is needed, limit who can see it, and use logs for fraud checks and dispute handling.

Collection

We collect account details, device type, IP address, login time and transaction references only when they are needed to run your account, check identity and handle support requests tied to the same profile.

Cookies

Cookies help the session remember your preferences, keep you signed in and spot repeated errors. You can clear them in your browser, but some parts of the page may need them to work properly.

Security

We protect access with passwords, OTP checks and session controls where available. Never share your OTP or login codes with anyone, and tell us at once if you see a sign-in you do not recognise.

Retention

We retain records only for the period needed to process requests, resolve disputes, meet audit duties and satisfy local law. After that, we delete or anonymise data that no longer needs to stay linked to you.

Changes

If your email, phone number or name changes, send the request from your registered channel so we can verify you before editing the account record. That protects you from unwanted changes made by someone else.

Requests

For access, correction or deletion requests, write to the privacy path listed here and include enough detail to find your account. We respond through the same channel after checking the identity details.

Privacy Policy Questions and Answers

These questions cover the basics you are most likely to ask before you open your account or send a request. They explain what we collect, how long we keep it, how cookies work and which route to use when you want changes. If a local rule changes what we can do, the local rule applies where it is relevant.

It covers how we collect, use, store and share account details, device signals, cookie data and payment references. It also explains how we handle correction requests, retention and the channels you can use to reach us.

We collect the details needed to create and protect your account: name, phone number, login history, device data and transaction references. We do not ask for more than we need for account operation and support.

Cookies help keep your session stable, remember preferences and identify unusual behaviour. They also reduce repeated logins. You can change browser settings, although some parts of the site may not work the same way.

We keep records only while they are needed for account handling, dispute checks, legal duties and security controls. When those reasons end, we remove or anonymise the data that no longer needs to stay linked to you.

Yes. Send the correction from your registered contact path and include the exact detail you want changed. We may ask for a fresh verification step before we edit the account record.

Use live chat, the contact form or the email path listed in this policy. Give enough detail to identify your account, and we will route the request to the right person for checking and reply.

Yes. When access or eligibility is discussed, it depends on local law and is available where local law permits. If a local rule conflicts with this policy, the local rule takes priority for you.