Privacy Policy

01. Scope of Collected Telemetry

Our platforms perform direct server-side analytics gathering only to guarantee correct layout deployment. During Discord OAuth2 authorization loops, we extract and cache only minimal data objects consisting of your public Discord user string, avatar hash, and user-id sequence. We do not inspect personal contact vectors or maintain structural databases of your local browsing routines.

02. Server Diagnostics & External Lookups

Mainframe analytics utilize structural external connections to resolve DNS lists, WHOIS ownership states, and SSL parameters. This processing occurs dynamically and is saved locally within configuration caches. We do not store or capture internal payload logs or private data keys of inspected target servers. IP addresses connecting to custom bios are mapped directly to check unique view telemetry numbers and stored as a hash to maintain unique-visit status safely.

03. Cookie Policy & Tracking Technologies

Our nodes are strictly tracking-cookie free. We maintain state validations using localized memory hashes inside local storage parameters (such as sessionStorage markers for Age-Gate choices) or verified session cookies. We explicitly do not trade, sell, or deploy cross-site marketing trackers, marketing pixels, or third-party profiling stacks.

04. Data Retention & Purge Demands

According to global protection guidelines (including GDPR and CCPA compliance rules), you maintain total governance over your cached parameters. Deleting your Linky directory configuration using the "Wipe" button immediately executes a full, automated physical purge of all active web configs, custom WebP resources, and telemetry parameters from our system directories. If you require manual server log purges, contact system administration teams.