Reference

Privacy Policy for Indian Accounts

We keep this page focused on the details that matter: what data we collect, how we use it, and when we share it.

Clear use of dataCookie use explainedRequest paths shown
juwaiteer Privacy Policy for Indian Accounts
REQUEST CHANNELS

Where to Send Privacy Requests

If you want to see, correct or remove data, use the contact path inside your account or write to the support address shown on the site.

Account message form Send your request from the contact form in your account so we can match it to the right profile, confirm identity and start the privacy check without delay.
Support email Use the support address shown in your account page for written requests, including access, correction, deletion or a copy of the data linked to your profile and payment logs.
Written request If you prefer a letter, send the details to the privacy team address listed in the footer. We keep the request on file and reply after verification steps.
STORAGE AND ACCESS

Cookies, Retention and Safety

We use session cookies to keep you signed in, remember your language choice and reduce repeat checks on the same device.

Data we collect

We keep only the details needed to run the account, answer your requests and meet legal duties: contact fields, login events, device data and payment references created during UPI, Paytm or PhonePe actions.

How cookies work

Cookies help us remember sign-in state, language choice and form entries. They also let us spot repeated errors or unusual access, so the site can keep working properly on your device.

Why we keep records

Retention covers account administration, support, dispute handling and legal checks. When the retention period ends, we remove, mask or archive the record so it is no longer used for daily operations.

Sharing with processors

We may share limited data with hosting, messaging, storage or payment processors that act for us. They receive only the details needed for their task and must follow our written instructions.

Your change requests

If your name, phone number or other account field changes, send us the new details from the contact route in your account. We verify the request before replacing any record.

Security checks

We review sign-in patterns, device signals and request history to spot misuse or account takeovers. These checks support the privacy policy and help us block access that should not continue.

Common Questions About This Policy

These answers cover the parts people ask about most: what we keep, why we keep it, how you can ask for changes and what happens when local law sets a limit. If something in your record needs correction, deletion or a copy, use the contact path inside your account and we will verify the request before acting. You can also ask about cookies or device logs there.

We collect the details needed to run your account and answer your requests: contact fields, login history, device signals, cookie data and payment references created when you use UPI, Paytm or PhonePe.

Cookies keep the sign-in state stable, remember language choice and reduce repeated checks on the same device. They also help us notice a broken session or a sign-in pattern that needs attention.

We keep records only for the period needed for the account, the request you made, dispute handling or legal duties. After that, we remove, mask or archive the data so it is no longer used day to day.

Yes. Send the new details through the contact route in your account, and we will verify that the request belongs to you before updating the relevant fields.

You can ask us to delete or limit parts of your data where local law allows it. We may still keep a small record if a legal duty or account dispute requires it.

Only staff who need the data for support, account checks or privacy handling can access it, and outside service providers receive just the minimum needed to host, store or send messages for us.

If a rule in your state or region sets a different standard, we follow the local law that applies there. Where local law permits, we show and process the relevant part of the service.