Reference

India Privacy Policy At zee5

We keep this page focused on how we handle your account data, cookies, and support records in plain terms.

Account dataCookiesSupport recordsLocal law
zee5 India Privacy Policy At zee5
REQUEST PATHS

Privacy Policy Contact Paths

If you want a copy of the data we hold, a correction, or help reading a privacy term, start with one of the paths below.

Email support Send your request by email if you want a written trail.
Live chat Use chat when you need a quick privacy check on cookies, login access, or…
Secure form Use the form if you want to ask for access, correction, closure, or deletion.
CARE CONTROLS

Data, Cookies, And Access Controls

We keep privacy handling practical. Account data is used for access, payment matching, service replies, and records we may need to keep under local law.

Data collection

We collect the details you enter at sign-up, plus device and session signals, so we can create access, keep the account working, and answer requests without asking you to repeat the same facts.

Cookie use

Cookies remember sign-in state, page language, and the path you took through the page. That lets us keep forms stable and reduce repeated logins when you move between sessions on the same device.

Account security

We use password checks, session controls, and device history to spot unusual access. When we need to confirm an action, we may ask you to verify the request through the contact point on file.

Payment records

UPI, Paytm, PhonePe, and Google Pay references are stored only to match the transfer to your account, confirm status, and handle disputes. We keep the reference trail rather than full card or wallet details where possible.

Retention

We keep records for as long as the account is active or as long as a legal or dispute reason remains. After that, we remove, mask, or archive the data in line with the request and the duty involved.

Your requests

You can ask for access, correction, closure, or deletion through support. We will check what local law permits, confirm the account, and reply through the same channel so you can track the result.

Privacy Policy Questions For You

These questions cover the way we handle account data, cookies, payment references, and request handling. If you need a correction or a copy of your data, use the contact paths here and we will check the record tied to your account. Where local law permits, you can also ask for closure or deletion, and we will answer through the same channel you used.

We collect the details you submit for access, contact, and account use, plus device and session signals that help keep sign-in working. We do not ask for more than we need to run the account and answer requests.

Device and session data help us spot unusual sign-ins, keep forms from resetting, and match support requests to the right account. They also help us understand whether a session ended normally or was interrupted.

When you use UPI, Paytm, PhonePe, or Google Pay, we store the reference details needed to match the payment to your account and answer disputes. We keep the trail, not extra payment fields, where possible.

Yes. Send the request through email, chat, or the form with the account details you used. Where local law permits, we can share a copy, correct a field, or close the account after checks.

Cookies mainly remember session state, language choice, and the last page path so the site works without repeated logins. They are not meant to hold your full account file or payment record.

We keep data only while the account is active or while a legal, security, or dispute reason remains. After that period, we remove, mask, or archive the record according to the duty involved.

Only staff and service providers who need the data for hosting, support, verification, or payment matching can access it. They are limited to the task at hand and should not use it for anything else.