Same account language
We use the same account terms across privacy, support, and profile areas. That consistency helps you connect a policy sentence with the field or setting you see on screen.
LEGAL REFERENCE
Privacy First Account Flow
wangi 4d puts account privacy beside the lobby from the first tap: clear data choices, secure sign-in handling, and local context for Indonesia before you open an account...
Privacy-first account setupIndonesia contextClear data choicesSecure sign-in flow
How Our Privacy Policy Works
This Privacy Policy applies when you access wangi4d.vip, open your account, contact us, or use our account tools in supported regions. We collect the details you provide, account activity records, device and browser signals, security logs, and transaction references needed to run your account. We use that data to verify access, maintain sessions, answer privacy requests, prevent misuse, personalise lawful account messages,
and meet compliance duties where local law permits. We do not sell your personal details. We may share limited data with hosting, security, analytics, identity, and payment-support partners only when they help us operate the service under agreed controls. You can ask us to access, correct, or delete eligible data, subject to retention duties tied to security, disputes, and legal records.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY VISITORS TRUST US
How We Keep Policy Clear
Our privacy page is written to explain what happens to your data without pushing you through legal noise. We check the wording against the actual account flow, support...
Plain wording
We avoid dense legal phrasing where a direct sentence works better. The aim is that you can see what we...
Account-flow checks
Policy wording is compared with the account journey, including sign-in, profile fields, verification steps, support contacts, and session handling. This...
Data minimisation
We focus on data that supports access, safety, service delivery, compliance, and account communication. If a detail is not needed...
Access controls
Internal access to personal data is limited by role and need. Support, security, and operations teams receive different permissions so...
Partner checks
Service partners are assessed for their role, data scope, and security duties. We share only what is needed for hosting...
Indonesia context
We write with Indonesia account journeys in mind, including mobile access, local e-wallet references, and QRIS-related support records, while applying...
BENCHMARKED
Consistent Policy Across Brand Pages
Privacy details should stay consistent wherever you read them on our brand pages. We align the same definitions for account data, device data, support records, cookies, partner access, and your privacy choices...
Same data categories
Personal details, device signals, session logs, support messages, and transaction references are described consistently across related pages. This reduces confusion when you compare privacy wording with account tools.
Same request handling
Access, correction, deletion, and consent requests follow the same verification approach across our privacy contact paths. We check ownership first, then explain what action is possible.
Same retention framing
Retention wording stays aligned across policy and support replies. Some records may remain for security, dispute handling, compliance, or fraud-prevention reasons even after other account details change.
Same cookie approach
Cookie language is kept close to the way our site uses browser storage for sessions, preferences, security, and analytics. We avoid making cookie choices sound broader than they are.
Same partner scope
Partner descriptions stay focused on hosting, security, analytics, support, identity, and transaction reference duties. We do not describe partner sharing as unlimited or unrelated to service operation.
Same update path
When privacy wording changes, related support scripts and account-page explanations should be adjusted too. This helps you receive the same answer whether you read or contact us.
SERVICE CONTEXT
Privacy Layout Brand Highlights
This privacy page is arranged for quick reading without turning the policy into a broad platform pitch. The layout shows what data we collect, why we use it, who may process it, how long...
01
Short privacy summary
The opening area gives you the privacy position first, before longer legal detail. It keeps account data, security use, local context, and your choices visible from the start.
02
Purpose-led sections
Each section connects a data category with a reason, such as account access, support, safety, compliance, or communication. This helps you judge whether a request makes sense.
03
Visible contact routes
Privacy contact paths are separated from general service copy, so you can find where to ask about access, correction, deletion, consent, or retention without searching through unrelated content.
04
Choice reminders
We repeat your available choices near the areas where they matter. That includes profile edits, communication settings, cookie preferences, and formal privacy requests through support channels.
05
Security context
Security details explain why some logs, device records, and account events may be kept. The wording connects retention with protection, dispute handling, and compliance instead of vague storage claims.
06
Update visibility
Policy updates are intended to be clear in wording and placement. When we adjust privacy practices, we aim to make the new effect understandable before you continue using the account.
Privacy Policy Questions Answered
We collect details you submit during account setup and support contact, plus device signals, session logs, and transaction references. The exact data depends on your account actions and available services in supported regions.
We use account data to create and secure access, maintain sessions, respond to support, manage lawful communications, prevent misuse, and meet compliance duties. We do not use it for purposes unrelated to our service.
No. We do not sell your personal details. Limited data may be shared with partners that help with hosting, security, analytics, support, identity checks, or transaction reference handling under service-related controls.
Contact us through privacy chat or email with the field you believe is wrong. We may verify your account first, then correct eligible details or explain why a record must remain unchanged.
Retention depends on the record type. Some profile or contact data may be updated sooner, while security logs, dispute records, and compliance material may stay longer where local law permits.
Cookies and similar storage help us manage sessions, remember preferences, support security, and understand site performance. You can adjust browser settings, though some account functions may not work properly without essential storage.