Privacy
A description of what actually happens, written for someone who intends to read it. Where a capability is not built yet, this page says so rather than describing a future state in the present tense.
Scope of this notice
This notice covers this website and the Phase 01 access programme. The EmotiLink Node and the oracle described elsewhere on this site are not generally available, and this notice will be replaced with a specific one before either is offered to the public.
Where this site describes a capability belonging to a later phase, that capability does not exist today and processes no data today.
What this website collects
If you submit the access form, we hold the address you gave us and the interest you selected. Nothing else from that form is retained.
This site does not run advertising trackers, third-party analytics profiles, or session recording. Fonts are served with the page rather than fetched from a third party at view time.
What the Node will do
The EmotiLink Local Engine is designed to process signals on your own device. Sensors, inference and the consent layer execute locally, and signals are reduced to the minimum shape a state requires before anything is considered for transmission.
Where a state must be retained, the design intent is that it is encrypted under a key you control and stored in decentralized infrastructure — not centralized in a conventional database belonging to us.
What leaves your device
The design intent of the architecture is that raw emotional and behavioral signals do not leave your device. What is shared with an application is a cryptographic proof that a specific condition was satisfied, together with its expiry.
A proof does not carry the state that produced it, and it cannot be reversed into that state by the application that receives it.
Consent, scope and revocation
Consent is intended to operate as a live state, checked at the moment of use, scoped to a specific purpose and set to expire. It is not a single permission recorded once at signup.
Revoking a grant stops the corresponding signal at its source. Because the signal was not duplicated into a central store, revocation is a matter of stopping production rather than chasing copies.
What is never placed on-chain
Raw emotional or personal data is never written to a blockchain. On-chain records are limited to cryptographic proofs, references, hashes, verifiable states, events, and mechanisms that require on-chain execution.
This is treated as a permanent architectural constraint rather than a current-configuration choice.
Your rights
You can ask what we hold about you, ask for it to be corrected, and ask for it to be deleted. During Phase 01 that is a short list, which makes all three straightforward.
Requests are handled by a person. We will confirm what was deleted rather than replying with a template.
This is a plain-language draft published during Phase 01. It will be superseded by a jurisdiction-specific notice before the Node is offered publicly, and this page will record when that happens.