Rujukan Laman

Open jangkar55 with clear privacy terms

Open your account with a clear Privacy Policy: we explain what account, device, cookie and payment-check data we collect before you enter the lobby.

Account dataCookie choicesPayment checksPrivacy requests
jangkar55 Open jangkar55 with clear privacy terms
CONTACT PATHS

Check privacy help channels

Privacy questions should not feel buried in general support. We keep contact paths simple so you can ask what data we hold, report a wrong detail, or request cookie changes linked to your device. Before we change account records, we may ask you to confirm ownership with login details, payment references, or a one-time code so your privacy request is handled by the right person.

Team online

Live chat

Use live chat for quick privacy questions about account records, cookie settings, or recent support messages. We may move complex requests to email when documents or written confirmation are needed.

Email privacy desk

Send email when you want a written record of your request, such as data correction, removal of eligible records, or a copy of account details we can lawfully share with you.

Account centre

Check your account centre for profile details, login activity and communication settings. Some changes can be made by you, while sensitive edits may require support checks first.

DATA HANDLING

Browse our data handling practices

Our policy is written around the way your account actually works: registration data, device logs, wallet records, live chat transcripts, and cookie settings all have different purposes and retention periods.

Account records

We use your account details to create access, confirm identity, manage wallet activity, and contact you about service matters. You can ask us to correct eligible fields when a detail is wrong.

Cookie controls

Cookies help remember your session, language choice, device state and security checks. You can manage browser settings, though certain cookies are needed to keep login and payment screens working safely.

Security logs

Login time, device type, IP data and failed access attempts help us detect unusual account activity. These logs are viewed only when needed for security, support checks or legal duties.

Payment references

Touch 'n Go, GrabPay, Boost dan FPX records are used to match wallet entries, check pending transfers and answer account disputes. We do not ask for banking passwords through our channels.

Retention periods

Some records are kept while your account stays active, while payment and legal records may need a longer period. When data is no longer needed, we remove or anonymise it where allowed.

Change requests

When you ask to view, correct or remove eligible data, we confirm account ownership first. This helps prevent another person from changing your records or seeing private account details.

Ask about your privacy rights

These answers focus only on our Privacy Policy and the rights tied to your account data. If your question involves account access, payment records, cookies, or a request to change stored details, use the contact path listed above so we can match your request with the correct account. We ask for proof only when needed to prevent another person from changing your data.

It covers details you give during account creation, login records, device data, cookie choices, payment references, live chat transcripts, and privacy request history. We collect only what helps us run accounts, payments, security, support, and legal duties.

We keep payment references so we can match wallet activity, handle failed transfers, check withdrawal requests, and answer privacy questions tied to Touch 'n Go, GrabPay, Boost dan FPX. We never ask for banking passwords.

Yes. You can ask us to correct eligible account details when they are wrong or outdated. For sensitive fields, we may ask for login proof or a payment reference before making changes.

Cookies help keep your session active, remember basic choices and support security checks. You can adjust browser settings, but some cookies are needed for login, wallet pages and account protection to work.

Retention depends on the data type and the reason it was collected. Account records, support chats, payment references and legal records may follow different periods before removal or anonymisation is allowed.

Only staff or service partners with a work reason can access personal data. Access is limited by role, and sensitive requests are checked so your account details are not shared wrongly.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy requests are also handled in line with the legal duties that apply to your account.