How qqdewi Handles Your Account Data
This privacy policy sets out what we collect when you open an account with qqdewi, why we collect it, and how long it stays on our systems. We've...
Scope, Jurisdiction & Lawful Basis
Our privacy posture follows the rules that apply where local law permits qqdewi to serve you. For Indonesia accounts, the lawful basis for processing is the contract you accept when you register, plus our legitimate interest in keeping the lobby fraud-free. We collect identity fields (name, date of birth, contact), session data (device, IP, lobby actions) and payment references tied to DANA,
OVO, GoPay and QRIS top-ups. We do not sell your personal data. Third-party processors — game studios, KYC vendors, payment rails — receive only the minimum needed to settle a round or a cashout. Retention periods follow the supported regions' financial-record rules, typically five years after your last session, after which we anonymise or delete.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Honest
This policy isn't a one-time legal drop. We review it on a published cadence and document who signed off on each change so you can see the editorial trail behind the words...
Quarterly Review
Our data officer rereads every clause four times a year against the supported regions' rule updates, flagging anything that no longer matches how the lobby actually handles your account fields.
Versioned Changes
Each revision carries a version number and a short change-note at the foot of the page, so you can spot exactly which paragraph moved between the copy you read last and the copy live today.
Named Signoff
A named data protection lead approves every published version. We don't ship anonymous policy edits, which keeps accountability inside qqdewi rather than outsourced to a template vendor.
Vendor Audits
KYC providers, payment processors and game studios touching your data are audited against our data-handling annex. Failed audits trigger contract review before the next renewal cycle closes.
Breach Protocol
If a data incident affects Indonesia accounts, we notify the relevant supervisory contact and reach you by email inside seventy-two hours, with the steps we've taken and what you should check.
Plain-Language Pledge
We test each clause for readability before publishing. If a paragraph needs a lawyer to decode, it gets rewritten until an ordinary account holder can follow what we're doing with their data.
Consistency Across Our Policy Pages
Our privacy policy aligns with the other legal pages on qqdewi so the rules don't contradict each other. Here's how this page slots in alongside the siblings you'll...
What Sits On This Policy Page
To make the policy easy to navigate, we've structured the page around the elements visitors actually scan for. Each block below points to a section you'll...
Data Categories
A clear inventory of the fields we hold: identity, contact, device, session, payment reference and communication history. Each category links to the lawful basis we rely on for collecting it.
Retention Clock
Plain timelines for how long each data category sits on our systems, with the trigger event that starts the clock — usually your last session or the closing of an open ticket.
Your Rights Panel
A summary of the access, correction, deletion, portability and objection rights you can exercise as an Indonesia account holder, plus the form fields we need to verify the request.
Third-Party Map
A named list of the processors that touch your data, what they receive and which country their servers sit in, refreshed whenever a vendor contract changes.
Change Log
The version history block at the foot of the page showing every edit we've made, the date it went live and a one-line note explaining what shifted.
Contact Block
The direct routes to our privacy desk — email, in-lobby chat, postal — repeated at the bottom so you don't have to scroll back up once you've finished reading.