Rujukan Laman

Open tgvegas Privacy Policy Before Creating Your Account

Your account record, payment references, device signals and support messages are handled under one clear Privacy Policy, with practical ways for you to ask about access, correction or…

Account recordsCookie choicesRequest routesLocal-law basis
tgvegas Open tgvegas Privacy Policy Before Creating Your Account
PRIVACY HELP DESK

Ask tgvegas About Your Privacy Rights

Need a copy of your account record, a correction or an explanation of a retention period? Contact our support team through the contact form or the support channel shown in your account.

Access requests Ask us to confirm whether we hold your account details and to provide a usable copy. We may verify your identity first so private records are sent to the right person.
Corrections and deletion Tell us which field is inaccurate or ask whether deletion is available. Some records may remain when needed for a dispute, security check or legal duty; we will explain the reason.
Privacy contact Use the contact route listed on your account to ask about cookies, sharing or retention. Add your preferred reply channel, and we will respond after the checks required for your request.
DATA CARE PRACTICES

Explore How Your Privacy Choices Work

Privacy choices work best when you can see the reason behind each step. We separate account data from access signals, limit staff access by role, record key changes and use payment references…

Data we receive

We record details you submit, account activity, device signals, support correspondence and payment references. Each category is described by its source and purpose so you can connect a record to the policy.

Purpose of use

We use account records to provide access, confirm wallet actions, protect sign-in, answer requests and meet legal duties. We do not describe a purpose vaguely; the policy links each use to the type of record involved.

Cookie controls

Cookies and similar signals help keep sessions active, remember selected settings and measure page performance. Your browser controls can limit them, although some account functions may not respond correctly when essential cookies are blocked.

Account security

We protect sign-in with account checks, access controls and monitoring for unusual device or wallet activity. If a message asks for your password or wallet PIN, do not send it; use the account contact route instead.

Retention checks

Retention depends on the record, its purpose, open disputes, security needs and legal duties. When the applicable period ends, we remove, anonymise or restrict the record according to our documented handling process.

Change requests

Send an access, correction, objection or deletion request through support, naming the affected account detail. We may request identity evidence, explain any lawful restriction and tell you how to raise a concern with the relevant authority.

Browse Answers About Your Account Data

These answers cover the requests we receive most often about account data and privacy choices. They explain what may be collected during sign-in, how payment references are treated, why identity checks can occur, how cookies work and where to send a change request. The exact result can depend on your location and the law that applies, so we may ask for extra details before acting. Access is available where local law permits.

We may collect your name, contact details, date-of-birth confirmation, sign-in records, device signals, wallet activity, support messages and withdrawal checks. The exact fields depend on the request you make and the legal duties that apply.

We use it to open and secure your account, confirm wallet actions, detect unusual access, respond to support questions, maintain transaction records and meet legal duties. We seek to use only the details needed for each stated purpose.

Payment services may send a transaction reference, amount, status and time so we can match a wallet action. Do not send us your Touch 'n Go or GrabPay password, wallet PIN or one-time code through support.

Use the account support route and state that you want an access request. Include the contact detail linked to your profile and any record reference. We may verify your identity before sending a copy through a protected channel.

Yes, ask us to correct an inaccurate field or to assess deletion where the law allows. We may retain some records for disputes, security checks or legal duties, and we will explain any restriction in our reply.

Cookies may keep your session open, remember settings and help us measure page performance. You can adjust browser controls or available consent settings; blocking essential cookies may affect sign-in and other account functions.

Retention varies by record type and purpose. We consider security, disputes, support handling and local legal duties, then remove, anonymise or restrict records when the applicable period ends. You can ask support about a particular record.