Reference

alam4d Privacy Policy For Your Account

Your alam4d Privacy Policy explains what we collect during phone verification, how we use account and wallet records, and how you can ask for changes.

Phone verificationMobile browser cookiesDANA and QRIS recordsAccount change requests
alam4d alam4d Privacy Policy For Your Account
CONTACT PATHS

Privacy Help For Account And Wallet

A clear support path helps you act on this Privacy Policy without sending sensitive details through an open channel. Start from the account help area, describe the data question, and include only the reference needed to locate your request. We use the same route for access concerns, wallet records, correction requests, and questions about browser activity.

Team online

Account access

Use the account support path when phone verification blocks access or you need to confirm which contact detail is attached to your account. We may ask for a matching account step before discussing personal data.

Wallet records

For DANA, OVO, GoPay, QRIS, or bank-transfer references, send the receipt code through the account help route. We use it to locate the transaction record without requesting your wallet password.

Change request

Ask us to correct an account detail, explain a retained record, or address a cookie concern through the support route shown after login. We will respond using the contact detail linked to your request.

SECURITY PRACTICE

Phone Checks, Cookies And Retention

We handle this policy area through ordinary account controls rather than broad collection. Phone verification helps connect you to the correct account, browser cookies help preserve a sign-in session, and security logs…

Account data

We use the contact details and account identifiers you provide to create access, recover a session, and respond to a Privacy Policy request. Phone verification occurs before account access so we can match the request correctly.

Wallet matching

Payment references from DANA, QRIS, OVO, GoPay, bank transfer, or virtual account activity help us identify a deposit or status question. We limit this use to account servicing, checks, and support handling.

Browser cookies

On a mobile or desktop browser, cookies can keep your session and remember security settings. Clearing cookies may sign you out or require phone verification again; it does not by itself erase account records.

Account security

We use login events, device signals, and verification steps to identify unusual account access. If a sign-in looks unfamiliar, support may ask for account details before discussing wallet or contact records.

Retention questions

We retain records only as long as needed for account servicing, security checks, dispute handling, or applicable legal duties. Ask support which category applies and why a particular record remains available.

Your request

You can request access, correction, or deletion by using the account support route. Include your account contact and the specific record in question; we may verify ownership before making a change.

Privacy Policy Questions For alam4d

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover phone verification, wallet references, browser cookies, correction requests, deletion, and local access wording so you know what to expect before sharing account details.

It covers data linked to account creation, phone verification, login events, browser cookies, wallet references, support requests, and security checks. It also explains access, correction, deletion, and retention requests.

Phone verification helps us connect you to the correct account before access or support action. It reduces mistaken account matches and gives us a practical ownership check when you ask about personal data.

Yes. We may use DANA and QRIS receipt references, along with OVO, GoPay, bank transfer, or virtual account references, to match wallet activity with your account and answer status questions.

Cookies can preserve your sign-in session and selected security settings on mobile or desktop browsers. Clearing them may sign you out or trigger another phone check, while stored account records follow separate retention rules.

Open the account support route, state which contact detail or record needs correction, and provide the account reference requested there. We may verify account ownership before changing personal data.

You can submit a deletion request through account support. We assess the request against active account needs, security checks, disputes, and applicable legal duties, then explain which records can be removed.

Yes. Access and eligibility depend on local law, and our Privacy Policy applies where local law permits. If you need a location-specific answer, contact support without sending wallet passwords or unnecessary documents.