LEGAL REFERENCE

How galan4d Handles Your Account Data

This is the galan4d privacy policy, written in plain language so you know exactly what we keep on file when you open an account with us. We cover...

Plain-language policyAccount-data focusUpdated regularlyIndonesia-awareReader-first wording
galan4d How galan4d Handles Your Account Data

Our Privacy Posture and Your Rights

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

HELP CHANNELS

Reach Us About Your Privacy

If anything in this policy is unclear, or you want to act on a privacy right, our team is reachable through three direct channels — pick whichever suits how you prefer to...

Privacy Inbox Email our dedicated privacy desk with your account reference and the question you'd like answered. We aim for a same-day acknowledgement and a full reply within five working days for Indonesia-based requests.
In-App Chat Open the chat bubble inside your galan4d account and pick the privacy topic. The agent routes your case directly to the data team without a public ticket trail, keeping your details off shared logs.
Written Request Prefer paper? Post a signed letter to our registered correspondence address listed in the footer. We treat written requests with the same priority as digital ones and confirm receipt by email.
EDITORIAL CLARITY

Editorial Trust Behind This Policy

This policy is reviewed by people, not just templates. Here's who looks over the wording before it reaches you and how we keep it accurate over time.

Legal Review

Our legal counsel checks every clause against current Indonesian data rules and the licences we operate under, flagging anything that needs softer wording or a clearer reader explanation.

Compliance Sign-Off

The compliance lead signs each version, confirming the policy matches what our internal systems actually do with your account data — no aspirational language, only what we can demonstrate.

Plain-Language Edit

A copy editor rewrites legal phrasing into the second-person voice you're reading now, because a policy you can't follow is a policy that doesn't really protect you.

Security Audit

Our security team validates the storage, encryption and access claims in this document quarterly, so the protections described here line up with the controls running on our servers.

Version History

Every revision is dated and archived. If you need to see the policy that applied when you first opened your account, we can produce that exact version on request.

Reader Feedback

When you tell us a paragraph is confusing, we log it and rewrite. Several sections of this page exist in their current form because of questions sent through our chat.

PLATFORM COMPARISON

How This Page Lines Up With Our Other Policies

Our privacy policy sits in a small family of legal pages. Here's how it stays consistent with the others so you don't get conflicting answers.

01

Terms of Service

Defines the agreement; this policy fills in the data half. Both use the same definitions for account, lobby and session so language stays aligned.

02

Cookie Notice

Covers browser-side tracking specifically. This policy points to it rather than duplicating, keeping cookie detail in one authoritative place.

03

AML Policy

Explains identity verification rules. We reference it when describing why we hold documents, so the reasons match across both pages.

04

Complaints Policy

Sets the route for disputes. Privacy escalations follow the same timing windows you'll see described there for fairness.

05

Marketing Preferences

Lists how you opt in or out of contact. This policy describes what we do with the preference; that page is where you change it.

06

Account Closure

Explains the deletion path step by step. We summarise it here and link out, so the procedure has one canonical home.

07

Security Statement

Describes the technical controls. Our policy summarises outcomes for the reader; the security statement is where engineers go for specifics.

PLATFORM SNAPSHOT

What You'll Notice On This Page

A few design choices shape how this policy reads. They're meant to make the page genuinely usable, not to bury the important parts.

Section Anchors Each heading has its own anchor so you can link...
Last-Updated Stamp The footer of the policy carries the date of the...
Plain Headings Headings describe what's in the section, not legal jargon. If...
Reader Voice We address you directly throughout. There's no third-person 'the user'...
Cross-Links Where another policy is more authoritative, we link rather than...
Version Archive Older editions remain reachable from the footer. If a clause...

Questions About This Privacy Policy

We keep your registration details, verification documents, lobby activity logs and payment references tied to your account. Anything outside that list isn't stored, and we review the list yearly to remove fields we no longer genuinely need.

Yes. Open a privacy request through chat or email and we'll confirm your identity, then erase what local law allows us to remove. Some records, like AML files, must be retained for the period regulators specify.

No. Your account data isn't sold or passed to advertising networks. We only share with payment processors, regulators or auditors when a specific legal or operational reason requires it, and we log every such transfer internally.

Your record sits on encrypted storage with role-based access. Staff need a documented reason to open your file, and every access is logged. Our security team reviews these controls quarterly against the claims made in this policy.

Active records are moved to a restricted archive once you close your galan4d account. We keep only what regulators in supported Indonesia regions oblige us to retain, then delete the remainder once that window expires.

Sign in and edit your profile fields directly, or message support for items locked after verification. We'll correct the record and confirm the change by email so you have a written trail of the update.

It will, as laws and our systems evolve. Material changes are announced inside your account before they take effect, and the version archive in the footer lets you compare old and new wording side by side.