Reference

manjur4d Privacy Policy for Your Account

Our Privacy Policy explains how manjur4d handles the data connected with your account, device, wallet status and support requests.

Account dataDevice choicesWallet recordsContact requests
manjur4d manjur4d Privacy Policy for Your Account
CONTACT ROUTES

Privacy Questions, Account Help, Clear Contacts

A clear contact route helps you control your data without guessing where to send a request. Sign in first when you can, then use the account support path for privacy questions, phone verification concerns or a receipt connected with DANA, OVO, GoPay or QRIS. If you cannot sign in, include only the minimum account details needed for us to locate the request.

Team online

Account support path

Use the support route attached to your account when you want to ask about stored data, a phone verification record or a transaction reference. We use the account path to reduce mistaken identity.

Payment receipt check

For a DANA, OVO, GoPay or QRIS receipt question, send the reference through account support rather than sharing wallet credentials. We check the payment record against your account before replying.

Sign-in assistance

If login stalls, tell us the device path you used, such as mobile browser or desktop, and the account contact connected with it. Do not send your password or one-time verification code.

DATA PRACTICES

Data Choices Across Your manjur4d Account

We keep this policy practical by linking each data use to an account task you can recognise.

What we collect

We may record your account contact, phone verification result, sign-in time, device type, browser signals, support messages and payment references. We collect these details when they are needed for access, safety or transaction support.

Why we use data

Account and device records help us recognise legitimate sign-ins, while DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us trace payment status.

Cookies and storage

Cookies or similar browser storage can keep a session active, remember a security setting and measure whether an account page loads correctly. You can manage browser storage through your device settings.

Account security

Phone verification, sign-in records and device signals help us detect access that does not match your account pattern. We will not ask for your password or one-time code through support messages.

How long we retain

We retain account, support and payment records only for as long as needed for the stated service, security checks, dispute handling or legal duties. Retention can differ by record type.

Your requested changes

You can ask us to correct inaccurate account data, explain a stored record or remove eligible details. Send the request through account support so we can confirm ownership before changing anything.

Privacy Policy Answers for manjur4d Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a support request is sent. Each answer points back to a practical account step, device setting or payment record, so you know what to prepare and where to ask.

It covers account contacts, phone verification, sign-in activity, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account to the correct contact and helps us identify unusual access. We record its result for account security, and we do not need your one-time code in a support message.

We use DANA and QRIS references to check payment progress and match a receipt with the correct account. We do not need your wallet password, wallet PIN or one-time code.

Yes. Send a request through the account support path asking for a data copy, correction or explanation. We may confirm account ownership before releasing or changing records connected with you.

Use account support to request removal of eligible data and state which record you mean. Some transaction, security or legal records may need to remain for a defined retention period.

Yes. The policy covers mobile browser access as well as desktop access. Browser cookies, device signals and sign-in events may be recorded to keep the account session and security checks working.

Start with the support path attached to your account and describe the privacy concern without sending a password or code. For a wallet issue, include the relevant payment reference, not private wallet credentials.