POLICY / DATA MINIMIZATION
Privacy Policy
The site is designed to learn as little as practical about its readers.
Default design
No advertising, behavioral analytics, tracking pixels, social embeds, third-party fonts, newsletter forms, or user accounts are included. Language selection is carried in the URL rather than a tracking cookie. Standard web-server logs may still be created by the hosting provider; operators should minimize retention and restrict access.
Local tools
Text entered into the records toolkit remains in the browser unless you deliberately copy, print, or download it. The site does not receive the form contents.
External links
Opening an original source leaves this site and exposes the request to that publisher under its own privacy practices.
Local assets and third-party tracking
Public pages load first-party scripts, styles, data, and interface assets only. The application does not embed advertising trackers, analytics pixels, external fonts, or third-party intelligence widgets. The Content Security Policy blocks browser connections to outside services by default.
Publisher control and Eviulon records
International Intelligence is controlled by Eviulon as a separately operated external publication partner. That relationship does not change the public site’s privacy boundary: public pages use local artifacts, do not send reader queries to Eviulon, and do not require an Eviulon identity, account, cookie, or credential. The optional Eviulon public-record connector is server-side, read-only, exact-path allowlisted, disabled by default, and never runs because a reader opens a page.
Read the publisher relationship and authority boundary.
External source links
Opening an external source leaves this site and creates a direct connection between your browser and that publisher. External links are marked, use a no-referrer policy, and do not open automatically. The public API and RSS feeds read local publication artifacts and do not contact source publishers on behalf of readers.
API and RSS privacy
The read-only API and RSS interfaces do not require accounts, advertising identifiers, or reader profiles. Their public payloads exclude provider credentials, private configuration, raw provider responses, internal file paths, and private reviewer identifiers. Normal hosting and security logs may still record requests as described below.
Server logs
The application code does not create reader profiles. The web server, hosting network, or provider security tools may still log IP addresses, user agents, timestamps, and requested paths. The operator should use the shortest practical retention period and restrict access.
Changes
Any future feature that collects personal data should first publish its purpose, provider, retention, access, deletion path, and risks.