Reference

Privacy Policy for Your sejitu Account

Our Privacy Policy explains what account, device and payment details we collect when you use sejitu, why we use them and how you can ask about your data.

Account dataDevice choicesWallet recordsYour requests
sejitu Privacy Policy for Your sejitu Account
ASK ABOUT DATA

Privacy Policy Help Beside Account Support

A clear contact route helps when you need to ask about the Privacy Policy, an account record or a wallet status check. Sign in first when you can, then include the phone number attached to your account and a short description of the request. If login is stalled, share only the minimum details needed for us to locate the account safely. Our support path can connect a privacy question with the relevant cashier or verification record without requesting your password.

Team online

Privacy request

Ask us to explain the account data linked to your sejitu profile, including the reason it was collected and the account step where it was used. We will use the details you provide to locate the correct record.

Wallet record

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time rather than sending a password or full wallet credentials. This gives us a focused path to check status and protect private details.

Access issue

If phone verification or login blocks your request, tell us which device path you used and what message appeared. We can separate an account-access problem from a Privacy Policy request before checking the relevant record.

DATA CONTROL

Inside sejitu Privacy Policy Controls

We keep the Privacy Policy practical by connecting each data use to a visible account action: access, verification, payment status or support.

Data handling

We use account details to create and maintain your profile, connect phone verification to the correct login and answer requests about access. Payment references help us trace DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookies

Essential cookies can keep your session and selected account path working across a mobile browser. We describe their role in the Privacy Policy so you can understand which browser records support login and which choices you can adjust.

Account security

Phone verification, session checks and limited support questions help us distinguish your account from another account. Never send your password in a request. We may pause a data change until we can confirm the requester.

Retention

We keep records for the period needed to operate the account, trace a wallet or bank transaction, resolve a dispute and meet a valid legal requirement. When a record is no longer needed, our handling follows the policy purpose.

Change request

You can ask us to correct incomplete account details or explain how a record is used. Include the phone number on the account and the requested change; we may ask for another account check before acting.

Policy contact

Questions about this Privacy Policy can follow the account support route. Tell us whether your request concerns access, correction, deletion, cookies or payment records, and we will direct it to the relevant handling path.

Privacy Policy Questions About sejitu

These Privacy Policy answers cover the account and device questions you are most likely to have before opening or using sejitu. Each answer stays focused on data access, payment records, cookies, verification and your route for requesting a change where local law permits.

The Privacy Policy covers data collected through account creation, phone verification, login, mobile browsing, wallet activity and support requests. It explains why we use each category, how records are protected and how you can ask about access, correction or deletion where applicable.

Phone verification helps connect account access to the correct person and reduces the chance of an unrelated request changing your details. We may use the verified number when checking login issues, payment status or a Privacy Policy request, but we do not need your password.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes. These records help us trace your request and resolve a mismatch without asking for complete wallet credentials.

When you access the account from a phone or desktop browser, we may receive technical details such as device type, browser session and security events. The Privacy Policy explains how these details support login continuity, fraud checks and troubleshooting without requiring access to unrelated device content.

Essential cookies can retain a session or remember an account path so you do not repeat the same login step on mobile. The Privacy Policy explains their purpose and your browser controls. Disabling them may affect account access or the way a request is completed.

Use the account support route and state whether you want access, correction, deletion or an explanation of use. Add the phone number linked to your account and the relevant record, such as a QRIS reference. We may verify your identity before making a change.

Yes. Account access and eligibility depend on local law, and our Privacy Policy is applied where local law permits. If you ask about a data right or payment record, we assess the request under the rules that apply to your location and account.