Stake Privacy: Account Data and Privacy Settings

Account information depends on the service and action involved. Registration, verification, support and payment operations can require different details. Read the relevant request and supply accurate information in these categories:

• Details you voluntarily include in a message, such as a name or reply address;
• Files attached to a genuine contact request, if that channel supports attachments; do not send identity documents;
• Account or transaction references relevant to a payment or support enquiry;
• The account action, page address or error message involved in the request;
• Technical connection information, such as IP address, browser and requested URL, that hosting systems may receive;
• The contents of correspondence sent through a working contact channel;
• Details needed to investigate an account-security issue or a legitimate legal request.

Use the secure verification area for identity documents rather than a public message or comment. Support enquiries usually need the problem and a reference, not your password or authentication code. Keep payment details accurate and ask which records are required when the account request is unclear.

The applicable privacy notice explains why particular records are used. Account data can relate to access, identity checks, payment processing, support and compliance. Check the stated purpose for the action involved, including:

• Confirming which article or page a request concerns;
• Managing account access and available service functions;
• Investigating link or navigation problems, without processing bets or payments;
• Identifying abuse of a contact channel or unusual technical requests;
• Responding to an account or website-support enquiry;
• Improving readability, accessibility and navigation;
• Providing the notifications or responses associated with your request;
• Assessing reader questions to improve the coverage of a guide;
• Understanding aggregated technical performance where measurement is available;
• Meeting the legal or compliance requirements described in the service policy;
• Responding to a valid request from an authorised authority;
• Handling a legitimate account or transaction dispute;
• Investigating misuse of account or service functions;
• Keeping account details and service information accurate;
• Reviewing correspondence submitted voluntarily for a stated purpose.

Supply the details needed for the request and use the correct response channel. An account reference and a concise description help support identify the issue. If a document is required, follow the secure upload instructions and check the status in your profile.

Keep identity and payment records inside the secure account processes that request them. Before sharing information, check why it is needed, which service receives it and whether the request comes from a verified account or support channel.

Choose communication preferences through the available account controls. Service messages about a transaction or verification request can differ from promotional subscriptions. Read the preference labels and confirmation before changing the channels through which you receive updates.
Use account preferences or support to manage promotional messages. Check the sender and account address before following an unsubscribe or recovery link. Passwords and authentication codes are not needed in a public message about communication preferences.

Open the correct HTTPS address and keep your browser updated. Use a unique password and available authentication controls to protect account access. Send financial or identity records only through the secure process that requests them, and avoid saving sensitive documents on a shared device.
No website can guarantee absolute security. Limit the information you share and contact the actual account provider immediately if login details or payment credentials are exposed.
Public comments and community messages may be visible to other users. Keep identification documents, private account screenshots and another person’s personal information out of public channels. Local notes can be deleted from the browser storage of the device used to save them.

Your browser can store settings or receive cookies from the sites and services you access. Review browser storage and permissions to understand what is present. Functions that may use local settings include:

• Remembering display or language preferences;
• Supporting the operation of a page component;
• Providing technical measurements only where a measurement service is actually enabled;
• Storing a choice made in a visible interface control.

Manage cookies, saved settings and local storage through your browser controls. Clearing storage can remove preferences and locally saved notes, while external destinations may store their own settings. Check the destination’s cookie notice for the categories used by that service.

Following a link can create a new interaction with another service. Different types of recipients or destinations can include:

• The gambling operator reached through a commercial link; its policies cover account activity there;
• Technical or service providers involved in delivering the relevant account function;
• An authorised authority where a disclosure is legally required;
• A successor responsible for the service if its ownership changes, subject to applicable requirements.

Read the account privacy notice for recipient categories, record retention and transfer conditions. Ask the privacy contact about a specific data request rather than sending the same documents to several channels. Relevant account and transaction references help identify the records involved.

The privacy notice can explain international data processing and the safeguards associated with service providers. Read those terms alongside the account’s location and eligibility conditions. For a request concerning a particular transfer or record, use the privacy contact specified by the service.

Rights depend on the law that applies and the information actually held. A request should identify the relevant interaction, without sending unnecessary sensitive records. You may be able to:

• Ask what personal information is associated with your correspondence;
• Request correction of an inaccurate record;
• Ask for deletion where no applicable obligation requires retention;
• Raise an objection or request restriction where the law permits;
• Request a copy in an appropriate format where that right applies;
• Contact the relevant data-protection authority about an unresolved concern.

For a privacy question, open the contact pageto choose the relevant contact route. For Stake account records, use the platform’s privacy or support channel and provide the reference needed to locate the request.

Gambling-related services are intended for adults who meet the applicable age requirements. Keep account access and identity documents away from children. Use device controls when appropriate and contact support if you suspect a minor’s details have been used in an account.

Check the privacy notice currently linked from the service. Updated features or legal requirements can change the information involved or the available controls. Review important changes before submitting a new record or changing an account preference.

For privacy contacts and available support routes, open the contact page . Direct player-account requests to the operator's own privacy channel, and keep the two services separate when describing your issue.