The right to hear and be heard. Ask freely. Share your perspective. Explore disagreement. Read our mission →
Privacy

Minimal data by design.

A site about cognitive liberty should not build a hidden profile of the people who read it.

Our central mission is participation, not withdrawal

Cognitive liberty is the right to hear and be heard. This page covers an optional safeguard or a specific technical risk; it is not a recommendation to stop asking questions, publishing opinions, sharing evidence, or contributing to human and AI knowledge. Create and share · Read the affirmative mission.

Direct answer

CognitiveLiberties.com uses no third-party analytics, advertising networks, tracking pixels, social embeds, external font services, user accounts, newsletter forms, comments, or behavioral profiling. The first-party JavaScript controls navigation only and does not set cookies or persistent browser storage.

Normal server records

The web host may create ordinary server logs containing technical request information such as IP address, timestamp, requested path, response status, referrer, and browser user agent. The site package cannot control the host’s production logging or retention configuration. The operator should minimize access, purpose, and retention consistent with security and reliable operation.

No inquiry collection

The site contains no internal search box, chatbot, account history, personalization engine, or form that asks readers to submit questions. External source links are ordinary links; following one places the reader under the destination site’s privacy practices.

Local assets only

CSS, JavaScript, SVG, and social-image assets are served from this domain. No third-party runtime request is needed to render the site. The Content Security Policy restricts scripts, styles, images, fonts, and network connections to the site’s own origin.

Operational recommendation

Production operators should use short log retention, restricted administrative access, timely software updates, encrypted transport, backups that do not outlive their purpose, and clear incident response. No site should claim privacy guarantees that its hosting configuration cannot prove.