Server logs
Like most WordPress hosting, the server may keep standard operational logs such as IP address, user agent, URL, timestamp, and error status for security and reliability.
Current public data flow.
The source-controlled site uses static public pages, static images, SVG diagrams, and read-only JSON assets. The public contact flow uses email, phone, and external profile links rather than an on-site form.
If you click an email, phone, LinkedIn, MikeKappel.com, UAIX, LLMWikis, AIWikis, Protocol5, or JustAnIota link, your browser or the destination service handles that interaction under its own policies.
No non-essential tracking found in theme source
This audit pass found no Google Analytics, Plausible, Umami, Matomo, tracking pixel, jQuery, or Bootstrap code in the active theme. If tracking is added, this page and consent handling must be updated first.
Data categories.
Contact data
Email, phone, and profile links are voluntary. Information you send by email or phone should be treated as direct correspondence, not public site content.
Cookies
The public theme does not add non-essential cookies. WordPress may use cookies for admin, login, preview, or security functions outside ordinary public reading.
Machine-readable files
JSON routes and llms.txt are public read-only files intended for documentation, route discovery, and AI-agent orientation.
External sites
Outbound links route to their owning sites. Teleodynamic.com does not control their logs, analytics, contact handling, or account systems.
Secrets
Do not send passwords, API keys, customer data, private research, production secrets, credentials, or privileged operational material through public contact channels unless a separate secure process is agreed.
Contact and correction requests.
For privacy questions, correction requests, or contact-flow concerns, use the public contact route and include only the information needed to process the request.
Change requirement.
Before adding a contact form, newsletter, non-essential analytics, embedded third-party media, advertising pixel, account feature, or public write route, update this privacy policy, define consent behavior, and record the change in the changelog.
Deep route polish
Zero-tracking narrative
The privacy visual anchors the site posture: static pages, local assets, no analytics, no account system, and no secret collection.
Written narrative
Privacy is part of the design system. A site about resource-bounded, evidence-first interpretation should not add hidden measurement systems that visitors cannot see or reason about.
Concrete example
Interactive modules run in the browser against local page state. They do not call third-party scripts, send analytics, or crawl external domains.
| Focus | What to inspect |
|---|---|
| Included | Static public pages, local SVG/JSON assets, direct contact links. |
| Not included | Analytics, tracking pixels, cookies, accounts, live crawling. |
| Visitor warning | Do not send secrets through public channels. |
Evidence note
Privacy posture is validated by no-tracking and external-asset tests in the theme package.
Internal reading path
/agent-start/
AI Agent Start: Safe Read Order and Handoff Boundaries
A machine-reader and limited-agent orientation page for safe Teleodynamic.com summarization, no-op boundaries, human review triggers, and UAIX-friendly handoff notes.
/federated-search-preview/
Federated Search Preview with Source Boundaries
A static, inert preview of future bounded search across approved public assets with source-domain labels and ambiguity collision warnings.
/resources/
Teleodynamic AI Resources and HTML Sitemap
A human-facing HTML sitemap for Teleodynamic AI, interpretable AI resources, AI memory, LLM Wikis, Unicode governance, Protocol5, and IOTA-1 research.