Reference

sekaitoto Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open an account, verify your phone and use DANA or QRIS, plus how we protect and retain those records.

Account dataWallet recordsCookie choicesContact requests
sekaitoto sekaitoto Privacy Policy for Your Account Data
CONTACT ROUTES

Get Privacy Help Near Your Account

A privacy question should reach the team that can match it to your account record. We keep the support path close to sign-in and wallet status, so you can describe a data concern without sending payment details through an unrelated channel. Include your registered contact and the affected account step, but do not share your password or one-time verification code.

Team online

Account support

Use the support path shown after sign-in for a privacy request. Tell us whether it concerns phone verification, login history, DANA, OVO, GoPay or QRIS records so we can locate the right case.

Payment record query

If a receipt or wallet status appears incorrect, provide the transaction reference and payment rail name. We use that reference to check the record without asking you to reveal your wallet password.

Access concern

If you suspect another device reached your account, contact support through the account route and describe the device path. We can review sign-in signals and explain the next verification step.

HANDLING DETAILS

What We Do With Your Personal Data

Clear handling rules matter when your account connects identity, device and payment records. Our approach separates service operation from unnecessary disclosure: we use account data for access, security…

Account details

We collect details needed to create and maintain your account, including contact data and phone verification status.

Cookies and devices

Cookies and device signals can help keep a session connected, remember selected settings and flag unusual sign-in behaviour.

Security checks

Phone verification, login events and device signals support account protection.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match receipts, status checks and account activity.

Retention period

We retain different records for different periods, based on their purpose, account activity, security needs and applicable requirements.

Changes and requests

To ask for correction, access or another privacy action, contact support through your account route with the relevant detail.

Privacy Policy Questions About sekaitoto

These answers address the questions we hear most often about account data, cookies, payment references and requests. If your situation is not covered, use the account support route and include enough context for us to locate the relevant record.

It covers data collected during account opening, phone verification, sign-in, wallet activity, device use and support contact. It also explains cookies, security checks, retention and how to request access or correction.

Phone verification helps connect access to the correct account and supports security checks when a sign-in or wallet action appears unusual. We use the status for account handling rather than asking for your wallet password.

Yes. The Privacy Policy covers transaction references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, allowing support to investigate a receipt without exposing private wallet credentials.

Contact us through the support path available in your account and identify the record you want to access or correct. We may verify your identity before responding or changing account information.

Cookies may keep your session connected, remember selected settings and help identify unusual sign-in behaviour. Browser controls let you manage them, but blocking certain cookies can affect the account access path.

Retention depends on the type of record, its operational purpose, security needs and applicable requirements. Account, payment and security records can therefore have different periods before deletion or restriction is considered.

Yes. Use the account support route from your mobile browser, describe the affected sign-in, device or payment reference, and avoid sharing passwords or one-time verification codes. Access remains where local law permits.