Privacy, without the fine-print maze.

Overview

Leunsel operates this website and is responsible for the application-level information described here. We use a limited amount of technical information to deliver pages, understand broad usage, maintain reliability, and protect the service from automated abuse and attacks.

We do not sell personal information and do not use the public website's traffic records for advertising profiles.

Information processed automatically

When a public page is requested, the website may temporarily record:

• the requesting IP address and a protected technical identifier derived from it;
• the time of the request and the page path, without query parameters;
• the response status;
• the referring website's hostname, without its path or query parameters;
• a broad browser and device category and whether the request appears automated.

The full browser user-agent string is evaluated only to create those broad categories and is not retained in the traffic database. Loopback traffic, including the IPv4 loopback range and ::1, is not recorded. Direct file downloads are excluded from the application's traffic analytics.

For the password-protected archive, failed sign-in attempts may temporarily create a one-way protected identifier derived from the requesting IP address. The submitted password is checked against a stored password hash and is never written to the traffic or security database.

When you submit a table update request, the optional information you enter is sent to Leunsel through Discord. The website also creates a one-way protected identifier from your IP address to enforce the limit of one request per table and calendar day. The IP address itself and your optional message are not written to the update-request rate-limit file.

How the information is used

Technical records are used only where reasonably necessary to:

• provide, troubleshoot and improve the website;
• measure page-level traffic in aggregate;
• detect bots, excessive request rates, misuse and security incidents;
• apply temporary or, in serious cases, longer security blocks;
• protect the website, its infrastructure and its visitors.

We rely on the need to operate and secure the service and on our legitimate interest in understanding its broad performance. Where local law requires another basis, we will use that basis or request permission before introducing the relevant processing.

Retention and aggregation

Normal identifiable page-request records are scheduled for automatic deletion after seven days and are removed during subsequent storage maintenance. The exact period may be shorter. Security records connected to a specific incident are normally scheduled for deletion after 30 days, while an active block identifier may remain until the block expires. A longer block is retained only when repeated or serious abuse makes it necessary.

Table update-request identifiers are separated into daily records, used only to enforce that day's limit, and scheduled for automatic deletion after eight days. These records contain neither the submitted message nor a directly stored IP address.

Before request records expire, page views are added to daily statistics. These aggregates contain no IP address, protected IP identifier, full user agent or individual browsing timeline and may be retained for longer-term comparisons.

Hosting and service providers

Website infrastructure and hosting providers may process network information needed to deliver and protect the service. The site also loads presentation resources such as fonts, style sheets or scripts from third-party content-delivery providers, including Google Fonts, jsDelivr and cdnjs. Those providers receive the technical information required to answer a browser request and handle it under their own terms and privacy notices.

Security notifications concerning attempts to access restricted administration tools may be delivered through Discord and can include the requesting IP address, request path and the outcome of the attempt. These notifications are used only to investigate and respond to administrative security events.

Table update requests are delivered through Discord and include the table, its public tracker details and any optional information you submit. The visitor IP address and protected rate-limit identifier are not included in the Discord message.

Links to services such as Discord and Patreon take you to independent websites. Their privacy practices apply after you follow those links.

Your choices and privacy rights

Depending on the law that applies to you, you may be entitled to request access, correction, deletion or restriction of identifiable information, or to object to certain processing. Because normal request records are short-lived, they may already have been deleted when a request is received.

You can also limit referrer information through your browser settings and avoid following external service links. Blocking essential network information entirely may prevent the website from responding to your request.

Security

Traffic records are stored in restricted server-side storage and are available only through authenticated administration tools. We use access controls, limited retention and data minimisation to reduce risk. No online system can be guaranteed completely secure, but we review these safeguards as the service changes.

Contact and changes

For a privacy question or request, contact Leunsel through the official Discord community or Patreon page. Please do not post an IP address or other private information in a public channel; request a private contact route first.

This notice may be updated when the website, its providers or its practices change. Material changes will be reflected by the updated date at the top of this page.