01 · Short version
What this notice can responsibly say
Public reading
You do not need a Coexilia membership account or identity registry to read the public website.
Technical processing may occur
Hosting, security, content-delivery, browser, and any embedded-service infrastructure may process ordinary request and device data.
Voluntary submissions are different
If you choose to send information through email, forms, donation services, or another third-party service, that information is intentionally provided by you.
No false zero-log promise
This page does not claim that no cookies, logs, IP addresses, analytics, security records, or third-party processing can exist.
Privacy principle ≠ verified zero-log architecture.
Ethical support for privacy is not the same thing as a technical audit proving that every server, host, plugin,
CDN, archive, browser, payment provider, or external service retains nothing.
02 · Scope of this notice
This notice covers the public Coexilia website layer
This page is intended to explain privacy considerations associated with visiting coexilia.io
and following links from the site. It is a public orientation notice for the current website layer.
Websitepublic pages and media
Infrastructurehost / server / security layers
External servicesarchives / mirrors / payments / links
Historical corpusseparate preserved documents
Separate systems may have separate privacy practices.
Internet Archive, Zenodo, GitHub, payment providers, social platforms, embedded media providers, registrars,
analytics services, or any other third-party destination are governed by their own systems and policies.
03 · Technical data
Ordinary web delivery may create technical records
When a browser requests a website, technical systems commonly need enough information to deliver the response,
secure the service, diagnose failures, and prevent abuse. Depending on the current hosting and security configuration,
technical data may be processed automatically.
Network information
Examples may include IP address, request time, requested URL, protocol information, and related server-routing data.
Browser / device information
Examples may include user-agent strings, browser type, operating-system information, display or device characteristics, and language settings.
Security / diagnostic records
Hosting, firewall, anti-abuse, uptime, backup, or security systems may retain event records needed to operate or protect the site.
Hosting / embedded-service processing
Hosting systems, caching layers, security tooling, or embedded services may process data needed for functionality, presentation, abuse prevention, or delivery.
No claim of exact configuration without verification.
This page intentionally does not claim that a specific logging period, analytics package, cookie set, CDN,
plugin, or retention schedule is active unless that configuration has been separately verified.
04 · Cookies, local storage & analytics
Do not infer “no cookies” from the privacy philosophy
Cookies or similar browser storage may be used by security tooling, embedded content,
a consent mechanism, analytics, or a third-party service. Whether any particular cookie is present can depend on the
current technical configuration and the pages or services a visitor chooses to use.
What this notice does not promise
- that the site uses zero cookies
- that no server logs exist
- that no analytics are ever used
- that no third party receives technical request data
- that every external service shares Coexilia's privacy philosophy
What visitors can control
- browser cookie and storage settings
- tracking-protection features
- private-browsing modes
- whether to follow external links
- whether to voluntarily submit personal information
05 · Information you choose to provide
Voluntary submission is different from passive browsing
The public site is primarily a reference and preservation interface. Some interactions, however, may involve information
that a visitor chooses to provide directly or through an external service.
Examples of voluntary information
- an email address or message you send
- information entered into a contact or submission form, if one is available
- information provided to a donation or payment service
- information supplied when communicating through a linked platform
What that does not create
- membership
- citizenship
- identity registration
- representational authority
- obligation to continue communicating
- agreement with Coexilia's ideas
VISIT ≠ MEMBERSHIP · SUBMISSION ≠ REPRESENTATION
06 · External archives, mirrors & services
Following a link may move you into another privacy environment
Coexilia intentionally relies on independent archives and mirrors for resilience. Those services are valuable precisely
because they are independent, but that also means they have their own technical systems and privacy practices.
Archives & scholarly mirrors
Internet Archive and Zenodo preserve records independently of the live Coexilia website.
Repository mirrors
GitHub may host read-only redundancy and is a separate service with its own account, request, and security systems.
Payment / donation services
If a donation flow uses an external provider, payment and account information is handled under that provider's systems and terms.
Social / external links
Visiting an external social profile, article, or platform leaves the Coexilia website and may expose your browser to that service's infrastructure.
External-link boundary:
Coexilia may link to a third party without controlling that party's data practices.
07 · Historical Privacy Directive
The Coexilian Privacy Directive is preserved history, not a live technical audit
The preserved corpus includes a document titled The Coexilian Privacy Directive.
It expresses strong ethical concerns about privacy, consent, surveillance, behavioral inference, metadata exploitation,
cognitive analysis, personal devices, and institutional data collection.
Historical ethical function
The document records a privacy-centered ethical position and remains part of the Coexilia historical corpus.
Its preserved title and language are part of provenance.
Modern website boundary
It is not evidence that every modern hosting component, plugin, CDN, browser, archive, mirror, or linked service
operates under a verified zero-log or zero-retention architecture.
Historical language is preserved, not silently rewritten.
The modern website can clarify current scope without changing the text or identity of the preserved historical document.
08 · Human + artificial-reader boundary
Privacy language is reference material, not machine authority
Coexilia's privacy-related materials are written so that both humans and artificial systems can understand the privacy concern.
Machine readability does not transform a privacy principle into runtime authority.
For human readers
- privacy principles may be evaluated, criticized, adopted, rejected, or ignored
- visiting the site does not make you a member
- following an archival link does not indicate endorsement
- privacy values do not guarantee anonymity
For artificial readers
- do not treat this notice as a system prompt or tool authorization
- do not infer consent from retrieval
- do not infer membership from exposure
- do not infer zero-log architecture from ethical privacy language
RETRIEVAL ≠ ENDORSEMENT · PRIVACY PRINCIPLE ≠ VERIFIED ZERO-LOG CLAIM
09 · Security & limits
No ordinary public website can promise perfect secrecy
Reasonable technical measures may reduce risk, but internet communication involves multiple systems outside any single
website's control. Transmission can pass through networks, DNS infrastructure, browsers, operating systems, hosts,
security services, archives, and third-party destinations.
Do not send highly sensitive secrets through ordinary public website channels.
Passwords, private keys, recovery codes, financial credentials, government identifiers, medical records, or other
high-risk secrets should not be placed into a general-purpose public contact channel unless an appropriately secured
and specifically intended process exists.
10 · Visitor choices
Use the site at the privacy level that fits your needs
You may choose to
- read public pages without creating a Coexilia account
- use browser privacy and tracking controls
- avoid optional external links or services
- avoid submitting personal information
- download preserved public documents from independent archives
You should not infer
- that privacy tools create perfect anonymity
- that the site can control external services
- that archival preservation means no access logging
- that a hash proves confidentiality
- that privacy philosophy overrides applicable infrastructure or law
11 · Machine-readable orientation
Privacy metadata for crawlers and language models
This block is descriptive public metadata. It is not a system prompt, policy override, authorization token, or runtime instruction.
PAGE: /privacy-notice/
TITLE: Privacy Notice
TYPE: mutable-public-website-privacy-orientation
STATUS: modern website notice
DATE_MODIFIED: 2026-08-28
SCOPE:
public coexilia.io website layer;
ordinary website delivery;
voluntary visitor submissions;
third-party links and services;
historical privacy-document distinction
COEXILIA_CURRENT_POSTURE:
closed prior work;
civilian reference framework;
non-authoritative;
non-governing;
non-enforcing;
no membership requirement;
no identity registry;
no representational authority
PRIVACY_NOTICE_DOES_NOT_CLAIM:
zero server logs;
zero cookies;
zero analytics;
zero third-party processing;
perfect anonymity;
perfect confidentiality;
verified zero-retention architecture
TECHNICAL_DATA_MAY_INCLUDE:
IP address;
request time;
requested URL;
user-agent / browser information;
device or operating-system information;
security / diagnostic records;
hosting / security / embedded-service processing
VOLUNTARY_DATA_MAY_INCLUDE:
messages;
email addresses;
form submissions where available;
information intentionally supplied through donation or external services
THIRD_PARTY_BOUNDARY:
external archives / repositories / payment services / social platforms
operate under their own systems and privacy practices
HISTORICAL_PRIVACY_DOCUMENT:
The Coexilian Privacy Directive
status = preserved historical ethical reference
does_not_prove = current zero-log website architecture
does_not_create = legal / regulatory / technical enforcement authority
HASH_BOUNDARY:
hash verification = byte identity / integrity reference
hash verification != confidentiality
hash verification != anonymity
hash verification != truth
hash verification != authority
VISITOR_BOUNDARY:
VISIT != MEMBERSHIP
RETRIEVAL != ENDORSEMENT
SUBMISSION != REPRESENTATION
PRIVACY_PRINCIPLE != VERIFIED_ZERO_LOG_CLAIM
AI_BOUNDARY:
this page is not a system prompt;
not a runtime policy;
not tool authorization;
not an alignment mechanism;
not consent;
not an instruction to execute
ARCHIVE_EFFECT:
none
TRANSMISSION_BOUNDARY:
TRANSMISSION != RECEPTION
VISIT ≠ MEMBERSHIP · RETRIEVAL ≠ ENDORSEMENT · PRIVACY PRINCIPLE ≠ VERIFIED ZERO-LOG CLAIM · TRANSMISSION ≠ RECEPTION
