Privacy Policy

BLUE33 is the website’s brand. The registered legal entity responsible for personal information, its business address, and country/state of establishment require owner confirmation. Privacy inquiries can be directed to contact@blue33.io.

This policy covers information processed in connection with visiting the BLUE33 website and contacting BLUE33. It does not cover independent third-party websites, wallets, networks, or trading platforms reached through external links.

Website delivery and security services may process technical request information, such as IP address, request date and time, requested URL, browser or device type, operating system, referring page, and error or security logs. The actual fields retained by each service must be confirmed; this draft does not claim every listed field is stored by BLUE33.

If you email contact@blue33.io, the receiving email service processes your email address, message content, attachments, and associated message metadata. BLUE33 may use the information you voluntarily provide to respond and maintain correspondence. Clicking the email link opens your email application; the website itself does not submit a contact form.

The current public website does not offer account registration, public sign-in, wallet connection, payment processing, or forms requesting personal information. BLUE33 does not request wallet private keys or recovery phrases. Do not send sensitive financial credentials or unnecessary personal information in an inquiry.

Depending on the information actually processed, purposes include delivering webpages and artwork, maintaining service availability, diagnosing errors, detecting misuse, responding to inquiries, managing legal requests, and complying with applicable obligations.

Any use for audience analytics, advertising, profiling, or additional purposes must be identified and disclosed before it begins. This draft does not represent that a particular analytics or marketing program is running.

Where laws such as the GDPR or UK GDPR apply, each processing purpose must have a valid legal basis. Subject to review, limited website operation and security may rely on legitimate interests, correspondence may rely on legitimate interests or steps requested by you before a contract, and required records may rely on legal obligations.

Consent will be sought where required, including for non-essential cookies or other consent-dependent processing. Where consent is used, you may withdraw it without affecting earlier lawful processing. The actual legal bases and legitimate-interest assessments require confirmation before finalization.

No custom advertising or analytics integration has been added as part of the current design. Sport selection is held in page memory and is not saved by BLUE33 in cookies or local storage. Hosting and delivery providers may independently use cookies, request logs, or similar technologies; their deployed behavior has not yet been fully audited.

A complete cookie inventory must be added after owner confirmation, identifying provider, purpose, duration, and whether each technology is essential. The absence of a custom integration does not establish that the delivered site uses no tracking technologies.

You can manage cookies using your browser settings, though blocking essential technologies may affect functionality. Where required, non-essential technologies must remain inactive until valid consent, and visitors must be able to withdraw or change that consent. A consent-management mechanism is not claimed as currently available.

Providers used to deliver the site, serve artwork and fonts, maintain security, and receive email may process technical or correspondence information on BLUE33’s behalf or under their own service terms. The site loads web fonts through Google Fonts; your browser’s requests to that service can disclose your IP address and request metadata. The full provider list, roles, and processing locations need confirmation.

Personal information may also need to be disclosed to comply with law or valid legal process, protect rights and security, or obtain professional legal assistance. Any disclosure must be limited to an appropriate purpose and lawful basis.

The operator must confirm whether any practice constitutes a sale, sharing for cross-context behavioral advertising, or targeted advertising under applicable law. This draft does not make an unverified “we never sell data” assurance. If such processing is introduced or confirmed, applicable disclosures and opt-out controls must be provided before it operates.

Planned token links may take you to Pump.fun or other independent trading services. When you visit an external service, that service may collect information directly from you under its own terms and privacy policy. BLUE33 does not control its collection, cookies, wallets, or transactions. Review its policy before providing information.

The planned token model uses the Solana blockchain. Transactions submitted through external platforms may publish wallet addresses, transaction amounts, and other records on a public blockchain. Public blockchain records may be permanent and cannot generally be edited or deleted by BLUE33. A wallet address may become identifiable when linked with other information.

No wallet connection, transaction execution, or blockchain verification is currently provided by BLUE33. If future integrations process wallet information or transaction data on the website, this policy must be updated to describe the actual processing before those features become available.

Information should be retained only as long as needed for its identified purpose, applicable legal duties, dispute resolution, and legitimate security needs. Technical logs, inquiries, backups, and legal records may require different retention periods.

Owner confirmation required: the actual log retention, email retention, backup-deletion schedule, and any legally mandated periods have not been supplied. This draft does not promise a specific deletion deadline. The final policy must state verified periods or meaningful criteria and account for service-provider retention.

When information is no longer needed, it should be deleted or anonymized under the confirmed retention practices, subject to legal holds or other lawful requirements. BLUE33 cannot delete independently maintained public blockchain records.

Security measures should be appropriate to the information and risks, including protection of website delivery, access to correspondence, and service-provider accounts. The exact technical and organizational measures, access controls, and incident procedures require confirmation; this draft does not certify a security audit or guarantee encryption of every stored record.

No internet service, email system, or electronic storage method is completely secure. Avoid sending wallet credentials or sensitive information by email. If a personal-data incident occurs, the operator must assess and provide any notices required by applicable law.

Hosting, font delivery, and email services may process information outside your country. The countries involved and any applicable transfer safeguards have not been confirmed.

Where required by law, international transfers must use an appropriate legal mechanism, such as an adequacy decision or approved contractual safeguards, together with any necessary additional measures. The final policy must identify applicable safeguards and how to request relevant information; it does not claim that a specific mechanism is already in place.

Your rights depend on your location, the applicable law, and the information processed. They may include the rights listed below, subject to lawful exceptions. No right to delete public blockchain records controlled by others is promised.

• Access to personal information and information about its processing.
• Correction of inaccurate information and deletion where legally available.
• Restriction of processing, objection, and portability where applicable.
• Withdrawal of consent for consent-based processing.
• Opting out of sale, certain sharing, targeted advertising, or qualifying profiling if those activities occur and the law provides that right.

Send privacy requests to contact@blue33.io with enough information to describe your request. We may need proportionate information to verify your identity or authority; do not send private keys, passwords, or excessive identification documents. Applicable response deadlines and appeal procedures must be confirmed and followed.

Where applicable, you may complain to your local data-protection authority. Residents of jurisdictions that provide appeal rights may challenge a denied request through contact@blue33.io; the final process must comply with local law. You should not be unlawfully discriminated against for exercising protected privacy rights.

BLUE33 is not directed to children, and speculative cryptocurrency activity is not intended for children. The applicable minimum age and geographic participation restrictions must be confirmed with counsel before launches. External trading platforms impose their own eligibility rules.

If you believe a child has provided personal information to BLUE33, contact contact@blue33.io so the matter can be reviewed and appropriate action taken under applicable law. This draft does not assert an unverified age-verification system.

Future administrative access, sports-data services, analytics, or launch integrations may introduce new processing. Before those features go live, the operator must update disclosures, assess providers and security, and obtain consent where required. Their inclusion as planned features does not mean they are active now.

The final policy will show an effective date and updated date. Material changes will be communicated as required by law. This page remains a review draft until the owner confirms actual processing practices and qualified counsel approves it.

For questions about personal information, cookies, retention, or your rights, email contact@blue33.io. Please identify your concern without sending unnecessary sensitive information.

Owner confirmation required: add the responsible operator’s registered name and mailing address, confirm the monitored privacy contact, and specify any required representative or data-protection officer details. No such appointment is assumed in this draft.