Reference

Privacy Policy for Indonesian Accounts

At maranti4d, we spell out what we collect from signup, login, cookies, and payment checks so you can read the rules before you open an account.

Signup dataCookie useDevice logsLocal law
maranti4d Privacy Policy for Indonesian Accounts
REQUEST CHANNELS

Where To Send Privacy Requests

If you want a copy, a correction, or a closure request, start with the contact path below and include the email or phone tied to your account. Live chat and WhatsApp handle privacy questions from 08:00-22:00 WIB, and email is better when you want a written trail. We check ownership before any change and we keep the conversation tied to your request number.

Team online

Live chat

Use live chat when you need a quick answer about cookies, device logs, or what happens after signup. We keep the channel open 08:00-22:00 WIB and link your question to the account email or phone.

WhatsApp

Send WhatsApp if you want to ask for a copy, correction, or closure request from your phone. Share the account email or registered number so we can match the right record before any action is taken.

Email

Email works well when you want the request in writing. We reply within one business day, verify ownership first, and then confirm the next step for data changes, retention questions, or stored cookie records.

DATA HANDLING

How We Handle Your Data

This policy is built around the records we actually need to run an account: signup details, login activity, device data, and payment references.

Signup data

We keep the name, phone, email, and date stamps you submit when opening an account, because those fields are the anchor for every privacy request and for later proof of ownership.

Cookie use

Cookies remember login state, device choice, and language so you do not have to repeat the same steps on mobile and desktop. You can clear them in browser settings, but that can end your session.

Payment references

When you use DANA, OVO, GoPay, or QRIS, we store the transaction reference and timing only to match the record and answer disputes. We do not keep full wallet details in the open profile.

Device security

We log browser type, IP range, and last login to spot suspicious access. If the device changes suddenly, we may ask for a fresh code before you can edit account details or request a copy.

Retention

Active accounts stay in our records while they remain open. After closure, we retain only the minimum needed for audit, dispute handling, or local-law retention, and remove it when that period ends.

Your requests

You can ask to read, correct, or close your record by sending the email or phone tied to the account. We confirm ownership, note the request time, and answer through the same channel.

Common Privacy Questions for Your Account

These are the questions we hear most when you want to know how the policy works before you finish signup. We keep the answers short on purpose: what we collect, why we use it, how long we keep it, and what happens when you ask for a change. If local law limits a request, we say so directly and tell you which part we can complete.

It covers the data we collect from signup, login, cookies, device logs, and payment references, plus how we store and use it. When local law limits a request, we explain the limit and the next step.

We ask for name, phone, email, and the device details needed to verify the account. If you use DANA, OVO, GoPay, or QRIS, we also keep the transaction reference tied to that action.

Cookies keep your session alive, remember language, and reduce repeated login steps when you switch devices. You can clear them in browser settings, but that may end the current session and require a new login.

Send the request through live chat, WhatsApp, or email with the account email or phone. We verify ownership first, then share the record or update the field you asked about once the match is confirmed.

We keep active account records while the account stays open. After closure, we retain only the minimum needed for audit, dispute handling, or local-law retention, and remove it when that period ends.

Only staff who need the record for account checks, payment matching, support, or storage upkeep can access it. When a service partner must handle a limited part of the record, we keep the sharing narrow.