Reference

What this policy covers

p4r sets out how we collect account details, device data, payment references and support requests before you open an account.

Account dataCookie useLocal lawSupport requests
p4r What this policy covers
CONTACT ROUTES

How to reach our policy team

If you want to ask what we hold, change contact details, or challenge a record, use the paths below.

Email support Send your privacy request to our support mailbox with the account email, a clear…
Account form If you can sign in, use the form in the account area to ask…
Written notice You can also send a written notice through the address listed on the site…
CONTROL AND RETENTION

How we handle your data

We keep privacy handling narrow: only the details needed to run your account, answer support queries and meet legal duties.

Data we keep

We store the account email, phone number, device type, browser signals, login history and payment references needed to match deposits or withdrawals. We do not ask for extra fields unless a support case or legal duty needs them.

Cookie use

Cookies remember sign-in state, language choice and whether a form was already sent. They also help us spot repeated errors and block tampered sessions. You can clear them in your browser, though some settings may reset.

Account checks

We use password checks, session timeouts and step-up verification when a request looks unusual. If you change phone or email details, we ask for proof before updating the profile tied to your account.

Retention windows

We keep records only as long as needed for account service, dispute handling, audit needs or legal duty. Payment references may stay longer than chat logs because they are needed to match a transaction later.

Your change request

If you want access, correction or deletion, send the request from the registered email or from the account area. We check identity first, then confirm what can be changed and what must stay on file.

How to reach us

For any privacy question, contact our support team through email or the form on the site. If a request needs a formal record, we may ask for a written submission before we act.

Common privacy questions answered

These questions cover the parts you usually check first: what we collect, how cookies work, how long records stay on file and how you can ask for a copy or correction. The answers stay within the privacy policy itself, so you can see what applies before you send a request. If a local rule changes what we can do, we follow the law that applies to your account.

We collect the details needed to create and secure the account: email, phone number, device signals, login history and the payment reference tied to a deposit or withdrawal. We avoid asking for extra fields unless support or law needs them.

Cookies keep sign-in state, language choice and form status across pages. They also help us spot repeat errors and stop tampered sessions. If you clear cookies, some saved preferences may reset on the next visit.

Yes. Send the request from your registered email or from the account area, and we will check identity before sharing the record. The exact form of access depends on local law and the data we hold.

Yes, you can ask us to correct contact details or other account fields that are out of date. We check the request against the registered profile first, then update what can be changed and keep the rest on file.

We keep it only as long as needed for account service, support history, payment matching, dispute handling, audit needs or legal duty. Some records may stay longer than chat logs because payment references have to be kept for later checks.

Use the support email, the account form or the written address listed on the site. We may ask for identity proof before any change, and we reply in plain English tied to the request you sent.