APEX88 Privacy Policy

Information Handled

apex88-official.com is designed as a static informational website. The repository contains public page content, design assets, configuration, and source-controlled records. It does not include a registration form, login form, support form, payment form, identity-upload form, newsletter field, or comment system. The APEX88 Website Terms explain the corresponding site-use boundaries.

The website therefore does not ask a visitor to submit an APEX88 username, password, SMS code, identity document, bank detail, wallet credential, account number, or support message. Do not send that information to this site through an address or channel that is not expressly published and verified.

Account information entered after following an external button is handled by the destination, not by this repository. Registration, login, promotions, games, payments, identity checks, and live-platform support are separate activities governed by the APEX88 account service’s privacy information and terms.

The repository does not include a customer database or server-side account application. A future feature that collects personal information would require a documented purpose, data fields, legal basis where applicable, security controls, retention approach, contact route, and a new privacy review before release.

Technical Logs

The static files themselves do not create an application-level visitor profile. However, the eventual production host, content-delivery network, domain provider, or security service may generate essential access and security logs when delivering the website.

Such logs can include an IP address, request time, requested path, response status, user-agent information, referrer, and technical security signals. The exact fields, location, access controls, and retention depend on the host and services selected for launch.

No host is named in this policy because the production provider has not yet been confirmed. Before publication, the owner must identify the host, review its default logging and security behaviour, document any material processing, and update this page. The policy must not imply that essential infrastructure logs are absent if the selected host creates them.

Operational logs should be limited to what is needed to deliver, secure, diagnose, and maintain the site. Access should be restricted. A precise retention period will be published only after the selected provider’s controls and operational need are confirmed.

Cookies and Analytics

Analytics and cookie-dependent features are disabled at launch. The site does not include an analytics tag, advertising pixel, session replay, behavioural profile, personalization system, account session, or marketing-consent banner in the approved build.

The static site does not intentionally set a first-party analytics or advertising cookie. The final host may still use essential technical mechanisms for security, traffic management, or abuse prevention. Those mechanisms must be assessed when hosting is selected and described here if they affect visitors.

No analytics claim should be changed merely by adding a script. Before introducing measurement or marketing technology, document the provider, data collected, purpose, configuration, retention, transfers, user controls, and any consent requirement. Update and reapprove this page before enabling it in production.

External sites may use their own cookies or similar technologies after a visitor leaves apex88-official.com. Their controls and notices apply there. This website does not treat an external site’s settings as its own.

Referral Parameters

The approved registration URL contains affiliateCode=lpclub01. This query parameter is sent to www.apex88.fun when a visitor deliberately selects the Register action. It identifies the referral associated with that link.

The parameter is visible in the destination URL and may be processed by the APEX88 account service under its own privacy and account terms. apex88-official.com does not need to store a copy in a local user profile because this site has no account system.

Other internal navigation links use clean canonical paths. The build does not add hidden personal identifiers to category, policy, login, app, promotion, or support URLs. If future campaign parameters are introduced, their purpose and handling require review.

A visitor can inspect the external destination before continuing. Removing or changing a referral parameter may affect attribution on the APEX88 account service, but it does not change the informational content on this site.

External Sites

External actions can lead to the APEX88 account service, Malaysian public authorities, or independent gambling-harm, health, crisis, and financial-support organizations. A disclosure identifies when a commercial action leaves this website.

The destination controls what it collects, why it uses the information, how long it keeps it, and which rights or controls are available. Review the destination’s current privacy information before submitting personal data.

Check the hostname after navigation. A familiar name, logo, or page style does not prove that a destination is the one described. If a redirect ends on an unexpected hostname, do not enter credentials or sensitive information.

Independent support resources are included because of their services. Their listing does not imply that they share data with APEX88 or endorse this website. Telephone calls are handled by the chosen telephone service and the receiving organization, not by this static site.

Retention

The approved repository does not store visitor submissions because it has no submission feature. It also does not create a site-level analytics profile. Source notes and editorial check dates describe public facts and do not contain visitor accounts.

Essential host or security logs may have provider-defined or owner-configured retention. A specific period is not stated until the production host is selected and the relevant controls are confirmed. Before launch, choose the shortest period consistent with security, diagnosis, operational needs, and applicable obligations.

If a privacy-request channel later receives correspondence, its storage and retention will depend on the verified channel and the nature of the request. That process must be documented before the channel is published. Do not send identity documents to an unverified address.

Backups and deployment records may retain older static files. They should not contain account credentials or form submissions because the site does not collect them. Any future collection feature would require a separate retention schedule.

Privacy Requests

A working privacy-request route is a required launch input and has not yet been approved. No email address, telephone number, office, data-controller name, or response schedule is invented in this draft.

Before publication, the owner must identify the party responsible for this informational website, provide a monitored contact route, explain the information needed to handle a request, and confirm how requests are authenticated, stored, answered, and retained. This page must then be updated and reapproved.

Until that route exists, do not send sensitive personal information to an address found on another website or to a person claiming to represent apex88-official.com. Live-platform account and transaction questions belong to a support route verified from the APEX88 account service, when available.

The absence of a contact in this launch-stage draft is not intended to limit any right available under applicable law. It records an unresolved operational dependency so the website cannot be published with a fictional contact or incorrect controller description.