Reference

2hollis Privacy Policy for India

This page tells you how 2hollis handles the account details you share when you open a profile, send a request, or browse the site.

Account dataCookie choicesUPI, Paytm, PhonePe
2hollis 2hollis Privacy Policy for India
CONTACT ROUTES

How To Reach Us About Privacy

If you want to ask about stored data, correct a detail, or check a deletion request, use the contact route linked to your account.

Email from your account Write to the address on file if you want a copy of your data…
In-account request form Use the form inside your account when you cannot reach email.
Payment trace help If your question touches UPI, Paytm, or PhonePe records, share the reference number and…
ACCOUNT SAFEGUARDS

How We Handle Your Records

We build privacy handling narrow: collect what the account needs, protect it with access control, and remove or mask it when the purpose ends.

Session Logs

Login timestamps, device signals, and IP records help us verify access, trace a disputed action, and protect the account from misuse. We keep them only as long as needed for that purpose.

Cookie State

Cookies store language choice, session state, and form progress. That keeps you from repeating the same steps every time you return. You can clear them in your browser whenever you want.

Payment Trails

When a payment arrives through UPI, Paytm, or PhonePe, we match the reference against your request before we mark it complete in our records. That helps us answer later queries with the correct trail.

Retention Limits

We keep account, support, and payment records only for the time needed for the stated purpose, then delete, mask, or archive them if a legal duty requires longer storage.

Change Requests

If your contact details change, send the update from the account route and we will check what can be corrected. Some fields may stay fixed where local law or audit rules require it.

Third-Party Sharing

We share data with payment partners, service providers, or authorities only when needed to run the account, answer a request, or meet a legal duty. Their use stays limited to that task.

Privacy Questions We Hear Often

These answers cover the requests we get most often about account data, cookies, and record access. If your case needs a correction, copy, or deletion check, send it through the contact route linked to your account so we can match the right record. When a request depends on local law, we explain what can be done and what must stay on file.

We may store the name you use, contact details, login history, device signals, and payment references linked to UPI, Paytm, or PhonePe. That lets us run the account, answer requests, and match records correctly.

Cookies remember your session, language choice, and page progress, so you do not need to repeat the same steps. You can clear or block them in your browser, though some functions may then ask you to sign in again.

Yes. Send the request from the contact route on file, tell us what you want copied or changed, and we will verify the account before making any update that local law allows.

We keep records only while they are needed for the stated purpose, or for any retention duty that applies. After that, we delete, mask, or archive the record based on its type.

Only staff who need it, service providers helping us run the account, payment partners handling the trail, and authorities when a legal duty requires disclosure. We do not share more than the task needs.

If local law does not allow a feature, access change, or record request, we will not offer it there. The same rule applies to your privacy choices and any account action tied to the region.