Privacy policy | L2.INFO

Service operator: [not specified]
Address: [not specified]
Email: [not specified]
Applicable law: [not specified]
Hosting and data location: [not specified]

01Data controller

Controller: [not specified]. Address: [not specified]. For access, correction, deletion and other privacy requests: [not specified]. Jurisdiction: [not specified]. Hosting and data location: [not specified]. Missing details mean this is a draft, not a completed controller notice.

02Data the service receives

When you browse, the server receives HTTP request information, including an IP address and browser details. The application uses the connection address for rate limiting but does not attach it to submissions. A submission contains a project or channel name, public URL, server settings or platform, contact email and any supplied description. Language, acceptance time and document versions are also recorded. Game account passwords and payment information are not requested. Do not include them in free-text fields.

03Purposes and legal bases

Data is used to operate the directory, review a submission you initiate, contact you about it, prevent abuse and meet legal requirements. The intended basis for submission processing relates to the action you request and performance of the terms; necessary security may rely on legitimate interests where applicable. Before publication, the operator must verify and specify the applicable bases under local law. Where an action needs consent, it must be requested separately; acknowledging this policy does not replace it. This build does not include advertising emails.

04Public data and external sources

A name, link, chronicle, rates, date and description may be shown after permitted publication. Submission email addresses and internal acceptance records are excluded from the public API. Server data is imported in the directory and channel data from supported platform APIs. Public channel names may identify individuals. To request correction, send the operator the URL and relevant issue; handling depends on rights verification and applicable law.

05Storage in your browser

Favorite servers, saved channels, the theme and offline submissions use localStorage. Language is determined by the page URL. These choices do not synchronize with a cloud account. Local data remains until you or the browser clear it; offline submissions can include an email address. The deletion control below clears only L2.INFO local keys, not submissions already sent to the backend. A saved-data export may include contact information, so share it carefully.

06Third-party connections

Twitch, Kick or YouTube receive technical information when their player loads, so an embedded player appears only after “Load player” is pressed. Real stream thumbnails may load from platform domains while browsing the directory. When remote font loading is enabled, the browser contacts Google Fonts with normal network request information; deployment settings can disable this feature. External links lead to sites governed by their own policies. This build contains no advertising analytics and sets no tracking cookies of its own. Hosting settings can introduce other connections, which the operator must disclose before launch.

07Recipients, international transfers and security

Non-public submissions are accessible to authorized moderators and necessary infrastructure providers. The operator must confirm the actual provider list and countries. External platforms may process requests in other countries under their own terms. Before using real personal data, the operator must assess applicable contractual, localization and international transfer requirements. The build restricts moderation with an administrator key, does not expose API secrets and validates input. HTTPS and backups are deployment responsibilities. Absolute security is not promised.

08Retention

Private submissions and terms-acceptance records are removed from the working database after {{retention}} days from creation during the next application cleanup. Cleanup runs at startup and hourly. Public directory records are stored separately and are not automatically deleted with the submission. IP rate-limit counters exist in process memory; expired counters are removed by minute-based cleanup, with a maximum rate window of one hour. Hosting logs, backups and legally required retention must be defined separately before publication; this application does not control them.

09Your rights and requests

Depending on applicable law, you may request information, correction, deletion, restriction, objection, a portable copy or withdrawal of consent for consent-based activities. Withdrawal does not affect earlier lawful processing. Send requests to [not specified] with the minimum details needed to locate the record; do not send identity documents without a justified need. The operator may reasonably verify the requester and must follow applicable deadlines. This does not limit your right to complain to a competent supervisory authority.

10Policy changes

The current version and date appear on this page. Changes to purposes, recipients or technical connections require an updated notice and, where required, separate notification or fresh consent. Analytics, payments, accounts or new vendors require further review; this policy does not automatically cover features that it does not describe.

11Feedback messages

The contact form stores your name, email, subject, message, language, time and the acknowledged privacy-policy version. Only the administrator can access these data, which are used to handle your request. Retention is {{retention}} days. The message is not published in the catalogue and does not subscribe you to marketing.

12Recruitment and the Telegram directory

An approved recruitment post publicly shows the team, server, roles, language, schedule, description and designated Telegram or Discord contact. Moderator email is not published. Channel listings show a name, link, language and description. A management key is issued once; only its hash is stored on the server. Keep the key yourself. Recruitment expires after 30 days. Withdrawal and data requests are available through post management and service contacts. Local drafts are saved in the browser only after an explicit action.

13HOT CHAT and Telegram posts

When enabled, chat integrations process a message timestamp, channel, and pseudonymized message and author identifiers for HOT CHAT. Message text is not stored. Counters remain in process memory for a five-minute window; cleanup runs every five seconds. Only aggregate counts are public. This is not an in-game population measure. An editor selects Telegram posts and stores a public post link with short summaries. No Telegram widget loads: selecting a card opens the original post.