Reference

71h Privacy Policy for Your Account

Your account details, wallet choices and device access stay connected to one clear Privacy Policy on 71h.

Account dataWallet recordsDevice choicesYour privacy requests
71h 71h Privacy Policy for Your Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact path helps you act on this Privacy Policy without searching through account screens. Tell us whether your question concerns account access, a wallet reference, a device record or a correction request. Include the email or phone detail linked to your account, but do not send a password or full payment credential. We use the details you provide to locate the request and respond.

Team online

Privacy request

Send a request through our listed support contact and state whether you want access, correction, deletion or an explanation of data connected with your 71h account.

Account matching

We may ask for a phone verification step or another account detail before disclosing records, so a stranger cannot receive information connected with your login.

Wallet question

For a DANA, OVO, GoPay or QRIS reference, share the date and reference available to you; never send your wallet PIN, password or complete credential.

DATA PRACTICE

Six Practical Privacy Controls

We handle privacy as part of the account path, not as a separate promise hidden from the cashier screen.

Collected details

We may receive your name, phone number, login details, verification results, wallet references and device signals when you create an account or use connected account areas.

Use of records

We use account and payment references to complete requested account actions, confirm wallet status, protect sessions and answer questions about activity linked to your account.

Cookies

Necessary cookies keep your session and selected settings available between pages. Browser controls can remove optional cookies, while required settings may be needed for account access.

Account security

Phone verification, login events and device signals help us detect unusual access. We do not ask for your password or wallet PIN when handling a privacy request.

Retention period

We retain records for the stated account purpose, support follow-up, dispute handling or a legal requirement, then remove or separate them when that need ends.

Policy changes

When our data handling changes, we update this Privacy Policy and its effective date. You should check the page before opening an account or changing account details.

Privacy Policy Questions About 71h

These answers address the privacy searches we hear most often from people checking 71h before creating an account. Each answer stays focused on what data we collect, how we use it, how access is confirmed and how you can contact us. If your situation is unusual, use the privacy contact path with the account detail you can safely share.

It covers account details, phone verification, login events, device signals, cookies, wallet references and support records created when you use account areas, where local law permits.

We use your phone number to create and verify the account, connect privacy requests to the correct record and help protect access when a login event appears unusual.

Yes. It includes payment references and wallet status linked with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, but not your wallet PIN or full credential.

Use the listed privacy contact path and ask for account data access. Include the phone or email connected with your account; we may verify ownership before sending records.

Yes. Send a correction request through support and identify the inaccurate field, such as a phone detail or account name. We may complete an account verification step first.

We keep information for the account purpose, support follow-up, dispute handling or a legal requirement. When those needs end, we remove or separate records where permitted.

Use the privacy contact route shown on this page and describe your request plainly. Do not include a password, wallet PIN or complete payment credential in your message.