Reference

Open g402 Privacy Policy for your account

This page explains how g402 collects, uses, stores and shares the details linked to your account, device and support requests from the start.

Data accessCookiesRetentionCorrections
g402 Open g402 Privacy Policy for your account
CONTACT ROUTES

Switch to privacy support routes

When your request is about privacy, we keep the path simple so you do not have to repeat the same details in different places.

Privacy Inbox Send a request from the email linked to your account and say what you want to see, change or remove. We use it to match the right record, confirm your identity, and avoid sharing details with the wrong person.
In-Account Form Use the form inside your account if you prefer written requests. It keeps the case in one place, lets us verify your identity, and helps us answer with the same contact trail when the request is closed.
Chat Desk If you need a quick hand, open chat and mention that your message is about privacy. We will point you to the right team, keep the thread attached to the request, and tell you if we need any extra detail.
RECORD CARE

Explore how we handle records

We write this policy to match the way the site actually works, not to fill space. That means clear purpose limits, account checks before any change, and a defined path for access…

Data Capture

We collect the details you type, the device and browser signals you send, and the transaction traces needed to run the account, answer support, and spot unusual access. We keep the scope tight and purpose-based, not open-ended.

Cookie Use

Cookies help us keep you signed in, remember form entries, and see whether pages load as expected. You can clear them in your browser, but some pages may ask you to verify again after that, which is normal.

Account Safety

Keep your password private and tell us quickly if you see a login you do not recognise. We may pause activity while we check device history, recent changes, and any request that looks out of place or inconsistent.

Retention Window

We keep account and transaction records for as long as needed for service, dispute handling, tax duties, and legal duties. After that, we archive or remove them under our retention rules, depending on the record type and the reason it was stored.

Request Handling

When you ask for a copy, correction, or removal, we verify the account first and then route the request to the right handler. Some records may stay back if a law or security need requires them, and we will say why.

Contact Route

For privacy matters, use the address or in-account form and include enough detail to identify the record you want changed. We reply through the same route unless you ask for another one, so you can keep one clear thread.

Open privacy answers for your account

These answers cover the questions we hear most often about data use, access, correction, cookies, retention and contact routes. If your request depends on a local rule or a record we must keep, we will tell you what applies and why. For anything else, use the same channel you used to reach us and we will continue from there without making you repeat the full story.

We keep the details you enter, device and browser signals, support messages, and transaction traces connected to your account. That lets us run the service, answer your requests, and spot access that does not fit your normal pattern.

Yes. After we verify the account, we can share a copy of the records linked to you, unless a local rule or a security duty requires us to hold back part of it. We will explain the reason.

Cookies keep you signed in, save form state, and help pages load in the same way on your next visit. Clearing them in the browser is fine, though some parts of the site may ask for verification again.

We keep account and transaction records for as long as we need them for service, dispute handling, tax duties, and legal duties. After that period, we archive or remove them under the retention rules for that record type.

Yes. If a contact detail, profile field, or record tied to your account needs an update, send the change through the support route and we will verify it before editing what we are allowed to edit.

Use the privacy inbox, the in-account form, or chat. Add enough detail to identify the record you mean, and we will answer through the same route unless you ask for a different contact method.

Access and data handling depend on local law, and the page applies only where local law permits. If the rules change, we follow the current rule set and update this page when it is needed.