LEGAL REFERENCE

Privacy Policy For Your exa303 Account

exa303 keeps your account data flow clear before you open the lobby: we explain what we collect, why we need it, and how your choices are handled. Open...

Indonesia-readyAccount data clarityQRIS contextPolicy-first layout

Tour the Lobby Read FAQ

How We Handle Your Privacy

This Privacy Policy explains how exa303 collects, uses, stores, shares, and protects data connected with your account, sign-in activity, lobby access, support requests, device signals, and transaction references where local law permits. We use data to run your account, confirm activity, respond to your requests, protect the service from misuse, meet compliance duties in supported regions, and keep records tied to DANA,

OVO, GoPay, and QRIS references when they appear in your account flow. We do not sell your personal data. Limited sharing may happen with service partners, verification partners, analytics tools, payment processors, legal advisers, or authorities when required by law. By opening or using your account, you acknowledge this policy and the way we process your data for the purposes stated here.

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

24/7 SUPPORT

Privacy Contact Paths We Maintain

You can contact us about privacy matters without searching through the lobby. We separate access requests, correction requests, and security questions so your message reaches the right desk faster. Include your account name, contact email, and a clear privacy topic so we can verify the request before discussing data.

Team online

Privacy Request Desk

Use this path when you want to ask what account data we hold, request a copy, or raise a privacy concern. We verify your identity first, then respond through your registered contact route.

Correction And Update Channel

Contact this channel when profile details, contact data, or account records appear outdated. We may ask for supporting proof before changing stored data, because privacy accuracy protects both your access and our records.

Security Escalation Line

Use this route if you think your account, device, or transaction reference has been exposed. We prioritise security-linked privacy reports and may pause sensitive actions while we check the account trail.

EDITORIAL CLARITY

Policy Checks Behind This Page

We keep this Privacy Policy tied to real account handling, not vague promises. Our legal, compliance, product, and support teams align the wording with the data we actually...

Legal Scope Check

We map each privacy statement against the account journey, supported regions, and service partners involved. That keeps the policy connected...

Data Flow Mapping

We trace data from registration, sign-in, lobby activity, support chats, and transaction references. This helps us explain why each category...

Plain English Editing

We write privacy wording in direct en-ID English so you can understand it without legal training. Short labels, clear purposes...

Support Feedback Loop

Questions sent to our support desk help us improve this page. If several account holders ask the same privacy question...

Partner Data Checks

Where partners help with hosting, verification, analytics, or transaction processing, we assess what data they receive and why. We aim...

Change Log Discipline

When we update this policy, we keep the reason connected to product, legal, or operational change. The effective date helps...

How This Policy Fits Nearby Pages

This page covers privacy only, while other legal pages handle account rules, cookies, promotions, or service terms. We keep those pages aligned so your data rights do not...

Terms Of Use

Our Terms explain account access, acceptable activity, and service boundaries. This Privacy Policy explains the data side of those actions, including records we keep when you sign in or request support.

Cookie Page

The cookie page deals with browser storage, device signals, and measurement tools. This Privacy Policy connects those signals to broader account data use, retention, and your available choices.

Promotion Rules

Promotion pages may ask us to record eligibility, opt-ins, and account status. This policy explains how those records are stored and why we keep them separate from ordinary support messages.

Account Verification Text

Verification wording explains what we may request to confirm identity or eligibility. This policy explains why verification data is processed, who may access it, and how long it may be retained.

Security Page

Security content explains safeguards such as monitoring, access controls, and alerts. This policy explains how those safeguards use data to protect your account and detect activity that needs attention.

Support Terms

Support terms explain how we communicate with you through chat, email, or other contact paths. This policy explains how those conversation records are stored and used to resolve privacy-linked requests.

Regional Access Text

Regional wording explains where access may be available, subject to local law. This policy explains how location signals and compliance records may be used when we manage supported regions.

AT A GLANCE

Privacy Layout Highlights You Can Scan

We designed this Privacy Policy so you can find the data topic you need without reading every legal line first. The layout groups account data, sharing, retention, rights, contact paths, and updates into clear...

Account Data Categories We show the main categories we may collect, such as profile details, sign-in records, device signals, support messages, and transaction references. Clear categories help you understand what sits behind your account.

Purpose-First Wording Each data category is tied to a purpose, such as account operation, support, security, compliance, or service improvement. We avoid collecting data unless it supports a stated account need.

Sharing Boundaries We explain when data may be shared with partners, processors, advisers, or authorities. The wording is framed around necessity, legal duty, and service operation rather than broad or undefined access.

Retention Signals Retention wording explains that data is kept only as long as needed for account, legal, dispute, security, or operational reasons. Different record types may follow different retention periods.

Your Request Options The page makes access, correction, deletion, and objection requests easier to identify. We also explain that identity checks may be required before we act on sensitive privacy requests.

Update Visibility When policy wording changes, the page is meant to make the update visible through clear dating and section structure. That helps you decide whether any new wording affects your account choices.

Privacy Policy Questions From Your Account

We may collect profile details, contact data, sign-in records, device signals, support messages, transaction references, and compliance records. The exact data depends on how you use your account and which features are available in supported regions.

We use account data to create and manage access, keep the service secure, answer your requests, process transaction references, meet legal duties, prevent misuse, and improve the account flow you see after signing in.

When these rails appear in your account flow, we may store related references such as timestamps, status records, or processor responses. We use those records for reconciliation, support, security checks, and compliance where local law permits.

Yes. Send a privacy request through the contact path listed on this page. We may verify your identity before releasing data, especially if the request involves account history, transaction references, or security-sensitive records.

You can ask us to correct inaccurate profile or contact details. Some records, such as security logs or transaction references, may need to remain unchanged for legal, dispute, or audit reasons.

We keep data for as long as needed to operate your account, meet legal duties, resolve disputes, protect the service, and maintain security records. Retention periods can vary by data type and supported region.