This page explains what data is logged when someone visits the Unex site, opens protected routes, or downloads a file. The policy is written to match the actual analytics and admin tools currently running on the site.
When the site is opened through its main entry point, a visit event can be logged. When a file is served through the download route, a download event can be logged. These records help track delivery health, identify broken flows, and understand traffic sources at a basic operational level.
The site may resolve approximate country, region, city, and provider data from a visitor IP address using standard IP geo lookup services. This information is approximate and is used for traffic overview, abuse detection, and owner-only analytics.
Referrer and user-agent values may be recorded to show where traffic came from and which browser families are being used. This helps with debugging, compatibility review, and measuring which channels are actually sending traffic to the site.
The private admin area uses a session cookie to keep the owner authenticated after a successful gate and login flow. That cookie is used only for session continuity, hidden route access, and basic admin protection. It is not intended for advertising.
Unex does not publish private log records publicly. Traffic may, however, be processed by infrastructure providers such as the hosting environment, content delivery edge, or standard DNS and security vendors required to operate the site. Data may also be disclosed where required by law or to protect the service from abuse.
Activity logs are stored in a rolling local window for recent operational visibility rather than indefinite public history. If exports are generated from the private admin panel, those exported copies are handled by the owner separately from the rolling site storage.
This privacy policy may be updated as the site stack, analytics model, or support process changes. The version published on the site is the current controlling version.
