PRIVACY & TERMS.

1. Information collected

Account registration stores your name, username, email, securely hashed password, verification state and tester application details. Bug reports store the name, email, selected system, written report, optional YouTube link and optional screenshot you provide. The portal also stores event and abuse-prevention records. Community contributions may include an uploaded file, external HTTPS link, public patch description, instructions, and the submitting account ID. Members may optionally upload an avatar and profile biography; website last-seen timestamps are recorded. Private messages store sender, recipient, message text, time and read status.

2. Purposes and access

Your account information is used to review free test access requests, manage authorized downloads and communicate application decisions. Bug reports are reviewed by project administrators. Account email addresses and submitted screenshots are not exposed through the public ticket lookup. Published Community Fixes display the member username, role, avatar and submitted patch details. Website activity appears as last seen unless you hide it in profile preferences; it does not indicate a live L2Server session. Private messages are visible only to their two participants through the website; staff do not receive a general mailbox-reading interface. The server operator can access data stored on the hosting system, so private messages are not end-to-end encrypted.

3. Beta distribution

Creating an account or ordering the free package does not guarantee access. The administrator may approve, reject or revoke access. Files are experimental and should only be tested with backups in an isolated environment. No payment is required.

4. Emails

When email delivery is configured, the portal sends account verification, password recovery and application-decision notifications. It does not send marketing emails. Email delivery relies on the site's configured SMTP or mail provider.

5. Storage and retention

The portal uses an application-specific private JSON store and private screenshot, avatar and community patch folders outside the public web root. Hiding a conversation removes it only from your account view; the other participant retains their copy and the underlying records remain until removed under the operator’s data-retention process. The site operator is responsible for securing, backing up and determining retention periods. Contact the project operator through its official contact channel to request correction, export or deletion of personal information.

6. Cookies and security

Essential session cookies are used for sign-in and form protection. Passwords are hashed; access to external download links is checked on every request. Use HTTPS and a trusted host. These safeguards do not replace ongoing server maintenance and security reviews.

7. Rights and ownership

Only share links and distribute files that you are legally authorized to share. The CLExt portal is an independent experimental project and is not affiliated with NCSOFT. Trademarks belong to their owners.