Reference

What this policy covers

This page explains how we collect and use account data, cookie signals and payment references so you know what stays on record.

Account dataCookie signalsPayment recordsLocal law

Explore Lobby Read FAQ

How data is handled in India

madurday Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our policy covers the details you give us, the records created when you open or use an account, and the device data needed to keep sessions stable. That can include your name, contact details, login timestamps, cookie identifiers and payment references linked to UPI, Paytm, PhonePe

1
or Google Pay. We use that data to verify access, process deposits and withdrawals, answer support requests, stop misuse, and keep the service in line with duties that apply where local law permits. When we work with service partners, we share only the minimum data needed
2
for payment routing, security checks or message delivery. We do not sell your personal data as a policy choice. If the law in your region gives you access, correction or deletion rights, you can ask through support and we will verify the request before acting. Some
3
records stay longer for tax, audit, dispute or fraud-prevention reasons.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

REQUEST CHANNELS

Where to send privacy requests

If you want to raise a privacy request, start with the contact paths below and include the email or phone number tied to your account.

Privacy email Write to [email protected] when you want access, correction or deletion of account data. We compare the name, phone and recent login record before sharing anything, so your request stays tied to the right account.

In-account form Use the in-account form when your request involves cookies, consent preferences or profile data. That route keeps the request attached to the same account thread and helps us answer with fewer follow-up questions.

Written copy If you need a written copy of the current policy or a dated record for a dispute, ask support for it. We reply in a plain format that you can save with your own records.

STORAGE AND ACCESS

How we protect your records

We keep the policy process practical. Collection is limited to what we need for sign-in, support, security and record-keeping, and sensitive fields are not open to every staff member.

Collected data

We collect the details you type in, login timestamps, browser data and device signals needed to keep the account working. When you use UPI, Paytm, PhonePe or Google Pay, we keep the reference data needed for reconciliation.

Cookie control

Cookies remember language, session state and pages you return to, which helps the site load the right screen after sign-in. You can clear them in your browser, though some pages may ask you to sign in again.

Access control

Only staff who need the data for support, security or record-keeping can reach sensitive fields. We separate permissions so the team that answers a privacy request does not see more than it needs.

Retention rules

We keep personal data only while it is needed for account support, fraud checks, disputes, audit or legal duties. After that, we delete it or mask it, unless a longer hold is required by local law.

Request checks

Before we share, correct or remove data, we confirm that the request comes from the account holder or an authorised contact. That check protects you from accidental disclosure and keeps the record trail clean.

Update route

If we change the policy, we post the updated text and date on the site. For important changes, we also surface the new version inside the account so you can read it before you continue.

Privacy questions you may ask

These questions cover the parts of the policy that matter most when you want to understand data use, cookies, retention and change requests. If your concern is about payment references, device logs or older support threads, we can point you to the exact section and explain why some records must remain for security, tax, audit or dispute handling under local law.

It covers the personal data tied to your account, device, cookies, support messages and payment references. It also explains when we use, share, retain or delete records under local law.

We collect the details you enter, login records, browser and device data, cookie identifiers and transaction references from UPI, Paytm, PhonePe or Google Pay when they are needed for reconciliation or support.

Cookies keep you signed in, remember language choices and help us spot unusual access. You can clear them in your browser, but some parts of the site may ask you to log in again.

We keep records only as long as needed for support, dispute handling, fraud checks, audit or legal duties. After that, we delete them or mask personal details where possible.

Yes. Send a request through support and we will verify your identity before acting. Where local law allows, you can ask for access, correction, deletion or a copy of specific records.

Only staff and service partners who need the data for operations, verification, support or security can see limited records. We keep access controls in place and do not share more than necessary.

If we change this policy, we post the new version on the site and update the date. For major changes, we may also point you to the revised text inside your account.

What this policy covers

Where to send privacy requests

How we protect your records

Collected data

Cookie control

Access control

Retention rules

Request checks

Update route

Privacy questions you may ask

01 What does this policy cover?

02 What data do you collect?

03 Why do you use cookies?

04 How long do you keep records?

05 Can I ask for changes or deletion?

06 Who can see my data?

07 How will I know about updates?

Related Pages