LEGAL REFERENCE

How We Handle Your Account Data

This is the aksestoto privacy policy — a straight read on what we collect when you open an account, why we keep it, and how long it stays...

Plain-English PolicyIndonesia-FocusedAccount Data OnlyUpdated RegularlyReader-First
aksestoto How We Handle Your Account Data

Privacy Posture and Jurisdiction Notes

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

24/7 SUPPORT

Privacy Contact Paths

Reach our privacy desk through any of the channels below. Each one routes to the same policy team — pick whichever fits your day.

Privacy Inbox Email our policy desk directly for data access, correction or deletion requests. We log every privacy ticket and respond inside the window Indonesian data norms set, with a written confirmation once your case closes.
In-App Chat Open the chat bubble after signing in and ask for the privacy team. The agent escalates your request to a policy reviewer rather than a general support handler, keeping your data conversation off the standard queue.
Written Notice Send a formal letter for matters that need a paper trail, such as deletion under Indonesian law. We accept signed notices at our registered address and reply through the same channel within the legal response window.
WHY THIS PLATFORM

How We Review This Policy

Our policy text is reviewed against current Indonesian data rules and our internal data-handling map. Here's what sits behind every line.

Legal Review

Our counsel reads each clause against Indonesian data protection rules before publication. Any wording change is logged with a date stamp so you can see what shifted between versions when you revisit this page.

Data Map Audit

We keep an internal map of every field we collect and where it travels. The privacy team checks the map quarterly and updates this policy when a new processor or storage region is added to the flow.

Editorial Plain-English

A non-legal editor rewrites dense clauses into readable English for our Indonesia audience. The aim is that you finish this page understanding what's collected, not parsing footnotes from a corporate template.

Version History

Every published edit carries a revision date at the foot of the policy. Older versions stay archived so you can compare what your account agreed to when you first opened it against what applies today.

Processor Vetting

Third-party processors who touch account data — payment routers, KYC checkers, hosting partners — are vetted for Indonesian compliance before they enter our chain. We list categories of processor inside this policy.

User Rights Channel

Access, correction, deletion and objection rights are handled by a named privacy reviewer rather than a ticket bot. That reviewer signs off your case and logs the outcome against your account record.

Consistency Across Our Policy Pages

This privacy policy sits beside our terms, cookie notice and account rules. Each one keeps the same posture so nothing contradicts.

Tone
Plain-English brand voice across every legal page, not boilerplate copy lifted from a template generator.
Jurisdiction
All policies reference Indonesian law and supported regions identically — no page widens access claims beyond the others.
Data Definitions
Account data, device data and transaction data carry the same definitions on the privacy, cookie and terms pages.
Retention Windows
Retention periods quoted here match the windows shown on our terms page, so your record lifetime reads the same in both places.
Contact Routes
Privacy inbox, in-app chat and written notice channels are listed identically across legal pages for one consistent path.
Revision Dates
Every legal page shows a revision date in the same footer position, letting you confirm the version you're reading at a glance.
User Rights
Access, correction and deletion rights are described in matching language on the privacy policy and the account terms.
AT A GLANCE

What This Policy Page Shows You

These are the visible elements we've built into the policy layout itself — the cues that help you read, navigate and act on the text.

Anchor Index A jump menu sits at the top of the policy...
Revision Stamp The footer of this policy carries the last-edited date and...
Plain-Word Glossary Terms like processor, controller and retention window are linked to...
Rights Action Box A boxed callout near the rights section shows the exact...
Processor List A category-level list shows the kinds of partner who touch...
Print-Ready Layout The policy renders cleanly when printed or saved to PDF...

Privacy Policy Questions

We collect identity details, your contact channel, a device fingerprint and the wallet reference you pick at checkout. Each field is tied to a stated purpose inside this policy, and nothing extra is captured silently in the background of the lobby.

Retention follows the periods Indonesian rules require for financial and account records. Once that window closes we either purge the record or anonymise it so it can't be tied back to you, and the schedule is logged inside our internal data map.

Yes. Send a deletion request through the privacy inbox, the in-app chat or a written notice. A named reviewer handles the case, confirms which records can lawfully be removed, and writes back to you with the outcome inside the response window.

Only vetted processors in categories like payment routing, KYC and hosting touch your data, and only for the task they're contracted to perform. We don't sell account data, and processors are bound to Indonesian compliance terms before they enter our chain.

Data sits with hosting partners in regions we've vetted for Indonesian compliance. The processor list inside this policy shows the categories of partner involved, and any change to storage region triggers a revision stamp on this page so you can see the move.

Each edit carries a revision date in the footer and a short note on what shifted. Material changes that affect your account rights are flagged at sign-in so you read the update before you next open the lobby.

Use the privacy inbox for email, the in-app chat for a logged conversation, or a written letter for matters needing a paper trail. All three routes reach the same policy team, not the general support queue, and every ticket is logged.