77JL privacy policy guidance
Before providing identity, contact or payment information, read the current operator privacy notice. This page explains the subjects to check without certifying the operator’s data practices, retention periods or security controls.
What should 77JL readers check about privacy?
Six questions to resolve before submitting personal or payment information.
Connection and identity
Confirm the exact address and HTTPS before sending details. Read who is responsible for processing information and how that organisation can be contacted. A secure connection does not establish every internal security measure or guarantee that data cannot be misused.
Use and sharing
Read whether information may be shared, with whom and for what purpose. Do not assume that a service never shares or sells information without a current notice that explains its practices. A payment or identity check can involve another organisation.
Request options
Find how to ask for access, correction, deletion or other applicable privacy choices. Check identity requirements, possible limitations and the response process. No absolute deletion right or fixed response deadline is promised by this guide.
Storage and retention
Look for the storage location, retention criteria and deletion process in the current notice. Ask about information kept after account closure. This page does not confirm a server location, audit schedule or period for any category of records.
Applicable privacy framework
Check which organisation handles the service and which privacy rules it identifies as applicable. This guide does not certify GDPR compliance or give a legal determination. Resolve unclear privacy information through the current verified contact route.
Privacy contact route
Use contact details in the current operator notice or verified account interface. Keep a request reference and avoid including passwords or one-time codes. No dedicated team, email address, hours or response speed is confirmed here.
On this page
- 01 Scope and introduction
- 02 Information categories
- 03 How information may be collected
- 04 Purposes to check
- 05 Sharing and recipients
- 06 Cookies and browser controls
- 07 Retention information
- 08 Privacy requests
- 09 Protecting under-21s
- 10 Third-party services
- 11 Security information
- 12 Notice changes
01 Scope and introduction
This page helps 77JL readers understand the privacy subjects to review before using an account journey. It is guidance about reading the current operator notice, not a substitute for that notice or a declaration of verified processing practices. Identify the organisation responsible for your information and the scope of the service it describes before entering personal details.
Read the current notice alongside eligibility, account and payment terms. Check its effective date, the purposes for collection and the available request route. This guide does not create consent on your behalf, certify legal compliance or claim that merely reading the page means you have agreed to all processing.
For practical account questions, use our account and support FAQs and verify the actual operator contact details before sending a privacy request.
Take time to understand why a detail is needed and whether a choice is available. If the responsible organisation, purpose or submission route is unclear, pause rather than sending identity documents to an unverified recipient. Adults aged 21+ only should consider account participation.
02 Information categories
An account or verification process may request different categories of information. The table identifies examples to look for in the current notice; it does not assert a complete inventory of information collected by 77JL.
| Category to review | Examples to check | Required or optional? |
|---|---|---|
| Identity details | Name, birth date and identification requested for verification | Check current requirements |
| Contact details | Phone number and email address | Check current requirements |
| Payment details | Payment account identifier and transaction references | Check current requirements |
| Device information | IP address, browser and device details | Read current collection notice |
| Activity records | Round, stake and transaction activity | Read current collection notice |
| Preferences | Language, communication and notification choices | Check available choices |
Compare the information requested with the stated purpose. Ask why an unexpected detail is needed and submit sensitive documents only through the verified route. Do not assume every field is compulsory or every collection requires the same form of permission.
03 How information may be collected
Read how each category is obtained and whether it comes directly from you, from your device or from another service. These are collection routes to check, not confirmed processing arrangements.
- Details you submit: look for registration, profile and identity-verification information described in the notice.
- Transaction records: check what payment information is recorded and which provider receives it.
- Device information: read whether technical logs are collected and what they contain.
- Cookies and similar tools: check the purpose, duration and available browser or consent controls.
- Help enquiries: read whether messages or attachments are retained and who can access them.
- Game activity: check which session and round records are kept and why.
Do not assume that every type of processing uses the same permission or that an account notice covers an unrelated third party. Read the current explanation of purpose, authority and choices before deciding to continue.
04 Purposes to check
For every category, the current notice should explain the relevant purpose. Review the following subjects and ask for clarification if the purpose of a requested detail is not apparent:
- Account setup and identity checks — what details are needed and why?
- Payments and offers — what records support transactions and account conditions?
- Service improvement — is activity analysed or used for personalisation?
- Fraud and misuse checks — what information is used and by whom?
- Communications — which messages are essential and which can be declined?
- Required disclosures — what circumstances may lead to sharing with authorities?
- Participation safeguards — how are account breaks or restrictions recorded?
- Technical support — what logs are used to diagnose access problems?
This guide does not confirm advertising, profiling or sale practices. Read the current operator explanation and available opt-out choices rather than relying on a general assurance that information is used only for service delivery.
05 Sharing and recipients
Read which recipients may receive information, their roles and the purposes involved. A current notice should distinguish the responsible organisation from suppliers or services that process data independently.
No promise that information is never shared or sold is made on this page. Confirm the actual practice and any choices in the current operator notice.
Recipient categories to review include:
- Payment services: check the information needed for the chosen transaction and the provider’s own notice.
- Authorities: read the circumstances and basis for any required disclosure.
- Identity-verification services: check who receives documents and how the verification purpose is described.
- Technical suppliers: read whether hosting, support or analytics providers receive information.
Check any cross-border processing, safeguards and restrictions described by the current notice. This page does not identify actual suppliers or certify contracts between 77JL and another organisation.
06 Cookies and browser controls
Cookies and similar storage can support sessions, preferences, analytics or marketing. Review the current site’s cookie information and your browser controls. The categories below explain what to look for, not a verified list of tools deployed by the operator.
- Session tools: check which tools are needed for sign-in or security and what happens if they are blocked.
- Preference tools: look for settings that remember language, display or other choices.
- Analytics tools: read what usage information is collected; do not assume it is anonymous.
- Marketing tools: check whether promotional tracking is used and which choices are available.
Your browser can provide controls for stored site data. Review what deleting or blocking it may change, including sign-in state. Do not interpret a general acknowledgement button as proof that every optional tracking choice has been presented.
07 Retention information
Read the current retention periods or criteria for each category and ask what changes after account closure. No specific period is verified here, and closing an account should not be assumed to erase every record immediately.
| Information category | Retention question |
|---|---|
| Account details | Check the period and closure criteria |
| Payment records | Read the current retention basis |
| Identity documents | Check duration and deletion process |
| Help enquiries | Ask about messages and attachments |
| Session logs | Read log-retention information |
| Communication preferences | Check how withdrawal of a choice is recorded |
Some information may remain subject to a stated retention need after a request or account closure. Read the current explanation, applicable exceptions and deletion or anonymisation process. This guide confirms neither a deadline nor a guaranteed erasure outcome.
08 Privacy requests
Find the request options described in the current notice and the requirements that apply to them. The cards below identify questions to raise; they do not promise an unrestricted right or determine how a request will be handled.
Access request
Ask how to obtain information about the personal details associated with your account.
Correction request
Check how to correct inaccurate or outdated details without creating conflicting records.
Deletion request
Ask what can be removed, what may need to remain and why any exception applies.
Use restrictions
Check whether a particular use can be paused or limited and what the consequence is.
Information copy
Ask whether a copy in a usable format is available and what identification is required.
Communication choices
Find how to change promotional preferences or raise an objection to a stated use.
Prepare your request through the verified route. Read the account and support FAQs for practical checks, then use the contact details in the current operator notice. No response deadline is guaranteed here.
09 Protecting under-21s
This site’s participation guidance is for adults aged 21+ only. Keep devices, payment access and identity documents away from under-21s. Do not submit another person’s details to create or verify an account.
If you believe information relating to an under-21 person has been submitted, stop further use and report the issue through the current verified privacy or account channel. Do not send additional sensitive material to an unverified address.
Ask the current operator how age-related reports are handled and what information is necessary. Begin with the account and support FAQs for contact-verification guidance; this page promises no specific deletion or closure process.
10 Third-party services
A payment, game, verification or analytics service may have its own privacy notice. Identify who controls the destination before following a link or submitting information. A brand reference does not prove a contractual relationship.
- Payment destination: check the provider name, requested data and transaction purpose.
- Game service: read the publisher’s notice if the game sends information to a separate service.
- Verification service: confirm who receives identity documents and why.
- Analytics service: read the stated collection, recipients and available choices.
This guide does not identify current suppliers or confirm their contract terms. Compare the relevant notices and pause if it is unclear which organisation receives your information or how to make a request.
11 Security information
Security should be assessed through current, traceable information rather than broad guarantees. Review what the operator says about the following subjects and protect your own account access as well:
- Connection protection: confirm the exact address and HTTPS; no encryption strength is certified here.
- Account verification: review any additional sign-in protections and recovery options shown.
- System controls: read the current security explanation without assuming a particular firewall.
- Independent assessment: look for a traceable statement covering the actual service if an audit is claimed.
- Activity monitoring: check what is stated about unusual access and how to report it.
- Backup and recovery: read what the notice explains about retained copies and recovery.
For a suspected information-security problem, use the current verified contact route and keep a reference. This page does not promise a breach-notification deadline, outcome or immunity from misuse.
12 Notice changes
Check the effective date and scope when an operator notice changes. Keep a copy of the version relevant to your decision and read any new purposes, recipients, retention terms or choices.
- Check which communication route is used for significant changes.
- Read notices posted in the current account or website interface.
- Compare the stated effective date with the version you previously read.
- Review what action is requested rather than assuming every change has the same effect.
This guidance was reviewed on 2026-10-28. Read the account and support FAQs for practical contact checks before using the current operator request route.
Revisit the actual operator notice before providing new information or using a new service. A review date on this guide does not establish the date of the operator’s policy.
Understand the information request,
then decide whether to continue
Read the current operator privacy notice, identify the recipient and resolve unclear purposes before submitting details. Adults aged 21+ only should consider account participation; no complete data-protection guarantee is made here.
Adults aged 21+ only. Participate responsibly and keep account credentials private.
