Reference

Open Privacy Policy for India

This page explains how chumba collects, uses, shares, and keeps data when you open an account, sign in, move through the site, or contact support.

Data useCookie choicesAccess requestsIndia law
chumba Open Privacy Policy for India
CONTACT ROUTES

Open privacy contact paths with ease

If you want us to access, correct, or close data tied to your account, use the contact path inside your account first. That route helps us match the request to the right record and avoid delays. If you cannot sign in, send the same request from the email on file and include your username so we can locate it. We answer only after we verify the request.

Team online

Account email

Send privacy requests from the email linked to your account. We use that address to match your profile, verify the request, and reply with the next step on access, correction, or deletion where allowed.

Account form

Use the account form for changes to contact details, cookie choices, or data questions. Add your username and the phone or email on file so we can check the request without delay.

Secure message

Write from the message area if you cannot reach email. That path keeps the request attached to your account record and helps us track the history of each change from start to finish.

HANDLING RULES

Switch on data handling and security

We treat privacy work as part of account maintenance, not a side task. That means we limit collection to service needs, keep cookies tied to function, protect sign-in…

Data minimisation

We collect only the details needed to open and maintain your account, process payments, answer support questions, and reduce fraud.

Cookie control

Cookies help us keep you signed in, remember language choices, and measure whether pages load correctly.

Sign-in security

We use device checks, session time-outs, and login alerts to reduce unauthorised access.

Retention windows

We keep account records only for as long as we need them for service, dispute handling, legal duties, and fraud…

Shared services

Some records move to service providers that help with hosting, identity checks, messaging, and payment processing.

Your requests

You can ask to see, correct, or close parts of your record, and you can ask us to explain a…

Open common privacy questions here

These questions cover what we collect, how long we keep it, how cookies work, and where to send a request if you want a copy or correction. If a local rule changes what we can do, that rule comes first. The answers below stay focused on account data, request handling, and the limits that apply in India for your use.

It covers data we collect when you open an account, sign in, move through the site, or contact support. It also explains sharing, retention, cookies, security checks, and the choices you can make from your account area.

We may collect your name, contact details, login details, device signals, support messages, and payment trails linked to your account. We use them to run the service, verify changes, and stop misuse.

Yes, we use cookies and similar tools for sign-in, language settings, and page performance. You can clear them in your browser, but some account features may need them to work as intended.

Only staff and service partners who need the data for hosting, support, verification, or payment handling can see it. We limit access by role and keep logs so we can check unusual use.

Use the contact path linked to your account and tell us what you want changed. If the request touches sensitive fields, we may ask for extra proof before we update the record.

We keep records for the period needed to run your account, meet legal duties, settle disputes, and prevent misuse. After that period, we delete or anonymise the data in line with local law.

If local law limits access in your region, we follow that rule and only offer the service where local law permits. If a request cannot be completed, we explain the reason in plain terms.