Your half of the
infrastructure.
The Node is not a collector we ask you to install. It is the part of EmotiLink OS that belongs to you — running on your device, holding your consent, and deciding what, if anything, ever leaves.
- Runs
- In the browser or on the device. WASM sandboxed.
- Transmits
- Proofs. Not signals, not content, not raw state.
- Revocation
- Immediate, per source, with nothing left behind to delete.
Six components, one job: make transmission unnecessary.
Local processing is not a performance optimisation here. It is the reason the rest of the architecture is able to make the promises it makes.
WASM runtime
Portable execution inside the browser or device sandbox, with no privileged install and no background service quietly outliving your attention.
On-device models
Inference happens locally. The model comes to the signal rather than the signal being shipped to the model.
Sensors & signal sources
Whatever you have authorized, and nothing else. Sources can be added and removed one at a time.
Consent layer
A live, enforced state in the runtime — not a record of a checkbox you ticked at signup two years ago.
Signal preparation
Raw input is reduced to the minimum shape a state requires, before anything is considered for transmission.
State generation
Emotion, intensity, timestamp and a DID signature — assembled and signed on the device that produced them.
Try the trade-off yourself.
Consent is only meaningful if the consequence of granting it is visible at the moment you grant it. Switch sources on and off — the panel shows what becomes provable, and what stays out of reach regardless.
Every switch is reversible, scoped and expiring. Revoking one stops the signal at the source — there is no copy elsewhere to delete.
Fewer signals means a less confident state — never a less private one. The trade is yours to make, and it is legible before you make it.
- Behavioral baseline · anomaly detection
- Receptivity banding
- Message, document or page content
- Precise location history
- Raw audio, video or camera frames
- Any identifier sold, brokered or shared
- Anything at all, without a scope you granted
The Node should not be viewed merely as a data-collection mechanism. It is the interaction surface between a person and the infrastructure.
An exchange you would accept if you read it carefully.
Phase 1 exists to test exactly this. Not whether the cryptography works — whether the offer is fair enough that someone with options says yes.
- CompensationConsented contribution is paid for, on terms visible before you grant anything.
- Better systemsRecommendations that read the room instead of your history.
- EmotiTribe standingCommunity benefits that do not scale with how much you share.
- ProtectionFrom Phase 5, the same understanding defends the account it belongs to.
Less than you would expect. On purpose.
We do not receive your signals. We receive proofs, aggregate statistics that cannot be resolved to a person, and the operational learning EmotiLoop needs to improve the models.
- raw_signal
- no access
- emotion_state
- no access
- identity_state
- no access
- proofs
- verification only
- aggregates
- non-identifying
We need the people who will argue with the terms.
If the consent model is confusing, the exchange unfair, or the value thin, Phase 1 is when we need to hear it — while the architecture is still soft enough to change.
No tracking pixel on this page · Consent before signal · Always