Reference

memara4d Privacy Policy for Your Account

memara4d Privacy Policy sets out how we collect, use, store and protect details linked to your account, including phone verification and wallet status for DANA, OVO, GoPay and…

Clear data useCookie choicesAccount access rightsContact steps
memara4d memara4d Privacy Policy for Your Account
HELP ROUTES

Contact Us About Privacy Questions

A direct support route helps you raise a privacy question without placing sensitive details in a public message. Start from your account support link, include the registered phone number only when requested, and describe whether your question concerns login records, cookies, a payment receipt or a correction. We use the same account path for follow-up so your request stays connected to the right record.

Team online

Account support link

Use the support link after account access to ask what personal details we hold or to request a correction. We may verify your registered phone before discussing account-specific records.

Receipt and wallet query

For DANA, OVO, GoPay or QRIS references, include the relevant receipt number rather than a wallet password. This lets us match the request while limiting unnecessary payment details.

Device access question

If a phone or desktop browser shows an unfamiliar login, tell us the device path and approximate time through support. We can then check access records and guide the next account step.

DATA CONTROLS

Protect Your memara4d Privacy Choices

Privacy depends on practical controls, not broad promises. We separate account access checks from wallet references, explain why cookies are used and keep requests tied to the account route that created them.

Data we collect

We may record your phone contact, account activity, device type, browser events, support messages and payment references. We collect these categories when they help provide access, investigate account security or answer a request.

Cookie settings

Cookies can keep your session active and help us recognise account access on a phone or desktop browser. You can adjust browser cookie controls, though some account functions may then require another login.

Account protection

Phone verification helps connect an access request to the correct account. Never send a wallet password or one-time code in support messages; we use account checks instead when a privacy request needs confirmation.

Storage period

We retain account and transaction records only for the period needed for service operation, security checks, dispute handling or legal duties. You can ask support which retention reason applies to a particular record.

Your requests

You can ask for a copy of personal details, correction of an error, clarification of use or deletion where applicable. We may confirm account ownership before acting so another person cannot change your record.

Policy changes

When this Privacy Policy changes, we place the updated wording on this page and revise its date or notice where needed. Checking this page before opening an account keeps your consent choices current.

Ask About the Privacy Policy

These answers address the privacy searches we hear most often before account access. They cover the data connected with local wallets, device records, cookie choices, account requests and the limits that apply when access depends on local law.

It covers account details, phone verification, device and browser records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the registered phone number to create an account link, complete phone verification and protect privacy requests. We may ask you to confirm it before discussing account-specific records.

Yes. The policy explains that wallet or QRIS references may be used to match a receipt, check transaction status and resolve an account question without requesting your wallet password.

Open the account support link and ask for a copy of your personal details. Include enough account context for us to locate the record, and complete an ownership check if requested.

You can request a correction or ask about deletion through support. We assess the request against account security, transaction records and legal duties before confirming which action can be taken.

Cookies can maintain a session and recognise a device path. Browser controls let you change cookie settings, but refusing some cookies may require repeated login or affect account access.

Account access and eligibility depend on local law. If you are in Indonesia, we apply the policy to the service where local law permits and explain any request limits through support.