Reference

Privacy Policy for Your rumputoto Account

Our Privacy Policy explains how we collect, use and protect the details you provide when opening a rumputoto account.

Clear data choicesPhone verificationWallet privacy

See How Your Data Moves

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

This Privacy Policy sets out the practical data path behind your account. We receive details such as your phone number, verification status, login events, device information and payment references when you create or use an account. A DANA, OVO, GoPay or QRIS transaction may give us

1
a reference, amount, status and time, while your bank transfer or virtual account record may identify the payment route without giving us your wallet password. We use these details to provide account access, check payment status, protect the account from misuse and answer support requests. We
2
do not ask for your wallet PIN through support. Access to our services depends on local law, and we apply this policy where local law permits. The page explains retention, cookies, security steps, requests for correction and the route for privacy questions.

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

HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps when a privacy question sits beside a login or wallet issue. We ask you to contact us from the account-linked route whenever possible, because that lets us check identity without exposing account details in an open message. Include the subject of your request, the phone number linked to the account and any relevant payment reference. We use the same care for requests from Semarang, Makassar and other Indonesian locations where local law permits.

Team online

Account-linked request

Use the support route connected to your rumputoto account for a data-access, correction or deletion request. We may ask for phone verification before discussing personal details, so your request stays connected to the right account.

Payment reference

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the payment reference rather than a wallet PIN. This gives us a practical way to locate the record while keeping secret credentials private.

Login privacy check

If a login issue involves an unfamiliar device, tell us when you noticed it and which device path you used. We can use the account record and verification status to direct the privacy request without asking for your password.

DATA HANDLING DETAILS

Know What We Keep And Why

We keep this policy close to the account flow because privacy choices make more sense beside real actions.

Account records

We may hold your phone number, account identifier, verification result, login events and selected account actions. These records support access checks and help us respond when you ask what data is linked to your rumputoto account.

Device signals

Your browser or mobile device can provide session, language, operating-system and security signals. We use these details to recognise an active account path and flag unusual access; they are not a request for your device password.

Cookies

Necessary cookies can keep a verified session open and remember security settings. Where optional cookies are used, your browser controls and any available consent setting provide a way to manage them without changing the wording of this policy.

Wallet references

Payment handling can store a provider reference, route, value, status and timestamp for DANA, OVO, GoPay or QRIS. We do not need your wallet PIN, one-time code or banking password to match that transaction record.

Account security

Phone verification is an account step before access, and we may compare sign-in details with earlier device signals. Never send a password, wallet PIN or one-time code to support; privacy checks use safer account-linked details.

Retention and changes

We retain personal data only for account operation, dispute handling, security checks or legal duties that apply. Ask us to correct, access or remove eligible data through support, and we will explain any lawful reason a record must remain.

Privacy Policy Questions Before Account Access

These answers focus on the questions we expect before you open an account or connect a local wallet. They explain what the Privacy Policy means for your phone, device, payment reference and support request, without asking you to share secret credentials. If your situation is unusual, contact us through the account-linked route and mention the specific part of the policy you want us to clarify.

The Privacy Policy covers account details, phone verification, login activity, device signals, cookies, support messages and payment references. It explains why we use those records, how we protect them, how long we may retain them and how you can request access or correction.

No. Our Privacy Policy distinguishes a transaction reference from a secret credential. We may receive route, status, value and time for DANA, OVO, GoPay or QRIS, but you should never send a wallet PIN, password or one-time code to us.

Phone verification connects an account request with the phone number you provide and helps us respond to account privacy requests. It can also support unusual-login checks. We use the verification result for account security, not as permission to request your private wallet credentials.

Use the account-linked support route and state that you are making a Privacy Policy data request. Include your account phone number and the type of record you want to access. We may verify your identity before releasing personal data connected with the account.

Yes, you can ask us to correct inaccurate account details or remove eligible personal data through support. We first confirm the request and explain the outcome. Some records may remain where needed for security, payment disputes or duties required by local law.

Necessary cookies can maintain your verified session and security settings on a browser or mobile device. Your browser can restrict cookies, although some account functions may then need another login. The Privacy Policy explains the purpose of any optional cookie setting shown to you.

We use this Privacy Policy for Indonesian account activity, including access from Semarang or Makassar, where local law permits. Eligibility and access depends on local law. If a local rule affects your request, support will explain the applicable limit rather than asking for unnecessary data.

Privacy Policy for Your rumputoto Account

Get Clear Answers About Your Data

Account-linked request

Payment reference

Login privacy check

Know What We Keep And Why

Account records

Device signals

Cookies

Wallet references

Account security

Retention and changes

Privacy Policy Questions Before Account Access

01 What does the rumputoto Privacy Policy cover?

02 Does rumputoto store my DANA, OVO, GoPay or QRIS PIN?

03 Why does rumputoto use phone verification?

04 How can I request my data from rumputoto?

05 Can I ask rumputoto to correct or remove data?

06 How do cookies affect my rumputoto account?

07 Does this Privacy Policy apply throughout Indonesia?

Related Pages