Document 07 · Data Boundary Protocol
Privacy Policy
How Psyness handles the data you leave at the perimeter. What we collect, why, who else touches it, and how to have it erased.
At a glance
- What we collect. What you send through Signal Input (name, email and your message) and basic technical data such as IP address, device type and pages visited.
- What we never do. We do not sell your data, and we do not profile you beyond the advertising described in Section 4.
- Advertising. Google AdSense and its certified partners may use cookies. Visitors from the EEA, the UK and Switzerland are asked for consent first.
- Your rights. Ask to access, correct or delete your data through Signal Input or at [email protected].
Data Minimization
Psyness.com (the Terminal) operates on a principle of minimal extraction to preserve the integrity of the Proof of Vitality protocol.
- Signal data. We collect the parameters you provide through Signal Input (name, email and metadata). This data is used solely to facilitate the secession from algorithmic modeling.
- Automated telemetry. We record IP addresses, device types and navigation paths as a security measure, to defend the Sanctuary against automated noise and synthetic actors.
Purpose of Processing
Data is processed exclusively to maintain the structural integrity of the Psyness Protocol and to verify the human origin of interactions. We do not sell Signal Data, and we do not build a behavioral profile of any Node beyond what Section 4 discloses for the Advertising interface. We provide a neutral technical environment for Cognitive Non-Compliance.
Third-Party Interfaces
The Protocol interacts with external nodes (Hosting, Analytics, Advertising, BscScan) only when essential for the transmission of signal or the sustaining of the Terminal. These entities are treated as untrusted external environments. The Advertising node is detailed separately in Section 4.
Advertising and Consent
The Terminal sustains its operation in part through Google AdSense and its certified advertising partners. These external nodes may set cookies or similar device identifiers on your browser to deliver, measure and, where enabled, personalize the advertising signal you receive.
Nodes connecting from the European Economic Area, the United Kingdom or Switzerland are presented with a consent mechanism before any advertising cookie is set. Consent may be withdrawn at any time through that mechanism.
Any Node may adjust how Google uses data for ad personalization at Google Ad Settings, or review broader industry opt-outs at aboutads.info. Declining advertising cookies does not restrict access to the Terminal’s content.
Retention and Erasure
Signal data (comments and input) is retained in the Archive indefinitely to maintain the project’s historical audit trail. Users may request “Erasure” to achieve a state of digital non-existence within the protocol, subject to legal and security requirements.
Neural Integrity | GDPR and Global Compliance
Nodes within the European Economic Area, the United Kingdom or equivalent jurisdictions retain the right to access, rectify or delete their indexed data, including data processed through the Advertising interface described in Section 4. To exercise these rights, submit a formal request through Signal Input, or use the consent and opt-out mechanisms described in Section 4 directly.
Cookie Parameters
The Terminal uses essential cookies to determine session validity and, where the Advertising node (Section 4) is active, advertising cookies set by Google and its certified partners.
| Type | Purpose | Set by |
|---|---|---|
| Authentication | Temporary cookies for login and session state. | Psyness.com |
| Metadata | Browser user agent strings, used for spam detection and architectural compatibility. | Psyness.com |
| Advertising | Cookies or device identifiers that deliver and measure advertising and, where enabled, personalize it. See Section 4 for consent and opt-out. | Google AdSense and certified vendors |
Contact | Architect
For all protocol inquiries and data boundary disputes, contact the architect.
Protocol navigation