Public
Designed for discovery
Approved identity, Current Questions, public theses, published book metadata, research status, public dossiers, schemas, synthetic examples and endpoint documentation.
IMPLEMENTED DATA BOUNDARIES · 2026-08-14
Public identity outside. Private cognition inside.
This page describes the current website’s implemented data flow. It is not permission to submit restricted data and does not replace a separately approved legal privacy policy.
Private
Stored in protected intake
Names, contact addresses, organization/role, the request body, requested rights, time window and operational status. Admin routes require the existing server-side admin token.
Never public
Not a discovery surface
Raw external-brain memory, private contacts, correspondence, calendars, investments, source corpora, ranking weights, private outcome graphs, credentials or third-party secrets.
Analytics
W-Axis uses a first-party, privacy-minimized event ledger for route, source category, page/CTA event, request category and a hashed browser nonce used to detect repeat visits. It does not send raw request text or contact email to analytics and does not use advertising pixels.
Retention and deletion route
Structured general requests use a 90-day operational retention window; bounded exchange requests use a seven-day window. After a structured request, the requester receives an onscreen request ID and deletion token. Send DELETE /api/requests/{request_id} with that token in the x-waxis-deletion-token header to remove the record immediately; the protected owner queue can also delete it. Deletion applies to W-Axis-controlled future storage and cannot recall information already seen by a person.
Submission boundary
Do not submit secrets, credentials, private keys, account details, medical or legal records, material non-public information, third-party confidential information, or any content you are not authorized to share.