Reference

hotel4d Privacy Policy for Your Account

The hotel4d Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, use DANA or QRIS, and contact our support…

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How DANA and QRIS Appear in Our Policy

hotel4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details needed to create and protect your account, including your contact details, verification records, sign-in events, device information and support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we keep the transaction reference and status

1
needed to match your wallet activity with your account; we do not treat a payment reference as permission to access unrelated wallet content. We use these records to check deposits, investigate a missing receipt and verify a withdrawal request. Cookie data helps us keep a session
2
active and understand which policy page was opened. Access to hotel4d services and any data request depends on local law. We may update this page when our handling steps change, and the latest page will explain the applicable process.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where to Ask About Privacy Policy

A clear contact path helps when your account details or wallet record needs attention. Use the support chat on our site for a question about the Privacy Policy, or send a request through the account contact form when you need a written trail. Include the email or phone linked to your account, but do not send a password, one-time code or full wallet credentials.

Team online

Policy questions

Open site support chat and ask about collection, cookies, account access or a Privacy Policy section; we can point you to the relevant handling step.

Data request

Use the account contact form to request a copy, correction or deletion assessment. Add your registered contact detail so we can match the request safely.

Wallet record

For a DANA, OVO, GoPay or QRIS query, include the transaction reference and date. We use those details to locate the account record without requesting your wallet password.

HANDLING PRACTICES

How We Handle Account Privacy

We keep the policy practical by connecting each privacy point to an account action you can recognise.

Data collection

We collect account details, verification data, device signals, session events and support messages when those records help provide access, protect the account or answer a request.

Cookie controls

Cookies can keep your sign-in session working and record basic page activity. Your browser settings can restrict cookies, though some account and policy functions may then behave differently.

Account protection

We use sign-in events, device checks and phone verification before account access where needed. Never share your password or one-time code through chat, email or a wallet message.

Retention periods

We retain account, payment and support records only as long as needed for the stated service, security checks, dispute handling or legal duties that apply to the request.

Correction requests

If your phone, email or account detail is wrong, contact us with the registered detail and the correction needed. We may ask for an account step to confirm ownership.

Deletion assessment

You can ask whether account data may be removed. We assess the request against open transactions, security needs and applicable law, then explain which records can or cannot change.

Privacy Policy Answers for hotel4d

These Privacy Policy answers cover the searches we hear most often before account creation or a wallet transaction. They explain the records connected with hotel4d access, what you can request, and how to contact us without exposing sensitive credentials.

It covers account and contact details, phone verification, device and sign-in events, cookies, support messages, payment references and requests to access, correct or remove personal data.

We keep the transaction reference, amount status and related account link needed to match a deposit, check a receipt or investigate a wallet issue. We do not request your wallet password.

Yes. Cookies may keep your session active and help us understand policy-page activity on a phone or desktop. Browser controls can restrict them, but sign-in functions may then change.

Send a request through the account contact form with your registered email or phone. We may ask for an account verification step before preparing a response or releasing account records.

You can ask us to correct an inaccurate phone number, email or profile detail. Include the current record and requested change; we may verify ownership before updating the account.

Retention depends on the record and its purpose. We keep details for account operation, security checks, transaction matching, disputes or legal duties only for the period needed.

You may submit a removal request through support. We assess it under local law and may retain records connected with open transactions, security matters or legal duties where required.

hotel4d Privacy Policy for Your Account

Where to Ask About Privacy Policy

Policy questions

Data request

Wallet record

How We Handle Account Privacy

Data collection

Cookie controls

Account protection

Retention periods

Correction requests

Deletion assessment

Privacy Policy Answers for hotel4d

01 What does the hotel4d Privacy Policy cover?

02 Why does hotel4d record DANA or QRIS payment details?

03 Does the Privacy Policy explain cookie use on mobile?

04 How can I request a copy of my hotel4d data?

05 Can I correct my account details under this Privacy Policy?

06 How long does hotel4d keep payment and support records?

07 Can I ask hotel4d to remove my personal data?

Related Pages