LEGAL REFERENCE

How pewe128 Handles Your Account Data

This is the pewe128 Privacy Policy page, written in plain language so you know what we store, why we store it, and how long it sits with us...

Plain-English policyIndonesia-aware wordingAccount data onlyUpdated regularlyYour control first
See the Lobby Read FAQ
pewe128 How pewe128 Handles Your Account Data

Our Privacy Posture Across Supported Regions

We collect the minimum needed to run your account: your sign-up details, device fingerprint, session timestamps and the payment reference your wallet provider returns to us. Where local law permits in Indonesia, we retain those records for the period our licensing partners require, then we purge. We never sell your data to third parties, and we share with processors only on a

contractual basis tied to fraud screening, settlement and dispute review. You can ask us to export, correct or delete your record at any time, and we'll action it inside the window our supported regions mandate. This policy sits alongside our Terms and overrides any older privacy notice you may have seen on a cached page.

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

SUPPORT

Privacy Contact Paths That Actually Reach Us

If something about your data feels off, reach our privacy desk directly. We answer in the order requests land and we log every ticket against your account so nothing gets lost between shifts.

Team online

Privacy Inbox

Email our data team straight from your account settings. Attach the reference number you'd like us to look at, and a human responds inside one working day for Indonesia hours.

In-App Chat

Open the chat bubble inside the lobby and ask for the privacy queue. Our agents can pull your record, walk through what's stored, and escalate deletion requests on the same session.

Data Request Form

Use the structured form for exports, corrections or erasure. It routes to our compliance officer, captures consent, and returns a downloadable file or written confirmation within the legal window.

PLATFORM TRUST SIGNALS

How We Keep This Policy Honest

Trust on a privacy page comes from showing our work. Here's who reviews this document, how often, and what changes between versions.

Internal Audit

Our compliance team re-reads this policy every quarter against the controls we actually run. If a clause no longer matches...

Legal Counsel

Indonesian-qualified counsel signs off on every material edit before we push it live, so the language matches the rules our...

Security Team

Encryption keys, access logs and retention timers are owned by a named engineer. That person also reviews this page so...

Processor Register

We keep a public-facing list of the vendors that touch your data: payment rails, KYC partners and analytics. The register...

Change Log

Every edit to this policy carries a date and a one-line summary at the foot of the page, so you...

User Feedback

If you flag confusing wording through the privacy inbox, we rewrite it. Several clauses on this page exist in their...

Consistency Across Our Policy Pages

Our Privacy Policy, Terms, Cookie Notice and KYC pages all draw from the same source document. Here's how the privacy page lines up against its siblings.

Scope
Privacy covers account data. Terms cover conduct. Cookie Notice covers browser storage. KYC covers identity proofs. No overlap, no contradiction.
Tone
All four pages use the same plain-English voice. If a clause reads heavier here than on Terms, flag it — we'll smooth it on the next pass.
Retention
Retention windows quoted here match the windows quoted on KYC. One number, one source, refreshed together when regulation moves.
Contact
The privacy inbox, chat queue and data request form are the same routes referenced on every legal page across pewe128.
Updates
Version dates at the foot of this page match the dates on Terms and Cookie Notice when edits are pushed in the same release.
Jurisdiction
Indonesian wording on this page mirrors the supported-regions language used elsewhere, so you never get conflicting answers about where we operate.
Definitions
Account, session, processor and personal data are defined once in our glossary and reused identically across all four policy pages.

What This Policy Page Actually Shows You

The layout here is built for scanning. These are the elements you'll see as you scroll, each placed so you can find the answer to a...

Section Anchors

Jump links across the top of the page move you straight to retention, sharing, your rights or contact. No long scroll, no hidden tabs, just the heading you need.

Version Stamp

A clear date marker sits at the head and foot of the page so you can confirm which version of the policy applied when you opened or last reviewed your account.

Plain Summaries

Each clause carries a short summary line above the legal wording. Read the summary for the gist, read the clause when you want the precise commitment.

Rights Panel

A dedicated block lists every right you hold over your record — access, correction, erasure, portability — with the route to exercise each one.

Processor List

An inline table names every vendor that touches your data and what they do, refreshed in step with our internal register.

Contact Block

The privacy inbox, chat and form sit together at the foot of the page so the path to a human is never more than one scroll away.

Privacy Questions We Hear Most Often

We collect your sign-up details, a device fingerprint, session timestamps and the reference your wallet returns when you fund the account. That's the working set — anything beyond it is collected only with a clear reason tied to fraud or settlement.

We hold closed-account data for the period our supported-regions licensing requires, then we purge. The exact window is listed in the retention clause above, and it matches the figure quoted on our KYC page word for word.

We share the minimum reference your wallet needs to settle a transaction — DANA, OVO, GoPay or QRIS. They don't receive your full account record, and we don't receive theirs beyond the confirmation token returned to our ledger.

Yes. Use the data request form linked in the contact block. We return a structured export inside the window our supported regions mandate, and we'll walk you through any field that isn't self-explanatory.

Open the in-app chat and ask for the privacy queue, or use the data request form for written-trail edits. Simple corrections happen on the same session; identity-linked fields route through a quick verification step.

Material changes trigger an in-account notice the next time you sign in, plus an email to the address on your record. Minor wording edits show up in the change log at the foot of this page.

Our compliance team re-reads the policy every quarter, legal counsel signs off material edits, and the security engineer who owns retention timers checks that the wording matches the systems. Account-holder feedback feeds the next pass.