Privacy
The registration surface asks only for the information needed to identify an interlocutor, understand the request, and respond through the channel the interlocutor provides.
What we ask for
- Name or handle.
- Reach channel and handle or address.
- Request class and intent.
- Consent to use that information for review and response.
How it is used
- Registration messages are reviewed before any conversation begins.
- Accepted interlocutors may become registered relationship records for future contact.
- Request content is routed to the responsible source or service owner only when review allows it.
- Public input does not directly execute services, publish content, or send sister-identity replies.
Retention
Raw intake is kept only as long as needed for review and follow-up. Spam or abuse may be discarded sooner. Accepted relationships may retain the minimal registration record needed to preserve the relationship and reply channel.
Current limits
This static site has no account system, no protected receipt pages, and no public upload endpoint. Those capabilities require a separate implementation and review gate.