Skip to content
EmotiLink OS

Open now

Your feelings stay yours.

EmotiLink OS notices how you are doing from the rhythm of how you work. Not from what you type, read or click. The rhythm stays on your device, and only a summary of it ever leaves.

  • Nothing is measured until you allow it
  • Turn any signal off in one tap, with no questions asked
  • See everything held about you, and erase it with one click
How it works

Four steps, and you can stop it at any one of them.

No vocabulary you have to be taught first. If you read only this far, you should still be able to say what this does.

01

You choose what it may notice

Typing rhythm, pointer movement, how often you switch tasks. Each one is a separate yes, on each device, and nothing is on until you say so.

02

The rhythm stays where it was measured

Your device holds it for about a minute, measures it, and discards it. What leaves is a short summary of the rhythm. Nothing that could be read back as what you typed, clicked or looked at, because none of that was ever recorded.

03

Nothing happens until something asks

There is no feed, and nothing runs in the background waiting to be collected. An application asks a question, and that question is what wakes any of this up.

04

Each app has to ask you separately

A yes to one application is not a yes to the next. You decide per app and per signal, you can see every decision you have made, and withdrawing one takes effect immediately.

02Permission

One yes does not become every yes.

Elsewhere, agreeing once hands over everything to everyone, for as long as the company exists. Here a permission is a single square: this signal, for this application, until you say otherwise.

Try it. Nothing on this page is connected to anything, and nothing is allowed to begin with.

Your permissions

0 of 9 allowed

SignalYour work toolWhether to hold back a notificationA wellbeing appWhether today was a heavy dayYour bankWhether this session looks like you
Typing rhythm
Pointer movement
Task switching

Nothing is allowed. This is what a fresh install looks like, and it stays this way until you change it.

01Privacy-by-Design

Minimized at the source, not cleaned up later.

Processing happens locally first. The infrastructure is built so the sensitive version of a signal never needs to travel, rather than travelling and being protected afterwards.

02Privacy-by-Consensus

Trust is validated, never asserted.

No single server is the authority on whether something is true. Verification is distributed across independent participants, so privacy does not rest on our good behaviour.

03Emotion-by-Consent

No signal exists without a deliberate yes.

Every signal is authorized, scoped and revocable. Consent is a live, enforced state in the architecture, not a checkbox recorded at signup.

01The inversion

Every system that wants to understand you asks for the same thing. Everything.

That is the bargain the last two decades normalized: hand over the raw material of your inner life, and receive a slightly better feed in return. The data is copied, pooled, retained, and eventually leaked. The person it describes is the only party in the exchange with no leverage.

EmotiLink OS refuses the premise. An application almost never needs to know how you feel. It needs to know whether a condition is true.

The conventional request

Give us your data. We will tell the application about you.

The EmotiLink OS request

Keep your data. We will prove the one thing the application is entitled to know.

01Raw signalNever leaves the device
02The rhythm of itMeasured, then discarded within the minute
03A summaryStatistics. No text, no location, no recording
04An answerThe only thing an application ever receives
08Why a person participates

Value has to flow back, or none of this is voluntary.

The hardest problem in this project was never cryptographic. It is convincing someone to run a Node at all. That requires an exchange a reasonable person would accept, and more than one way to benefit from it.

EmotiTribe

EmotiTribe

A community and wellness layer inside the ecosystem, explicitly not a marketplace, and not competing with one. Partners are selected for alignment with the community's principles, then integrated directly.

When a member buys through an integrated partner, the compensation that transaction generates can be shared back with eligible members. The value created by a community's own activity returns to it.

Four routes, not one
  • 01Consented contribution → compensation
  • 02EmotiTribe participation → benefits
  • 03Partner purchases → shared value
  • 04Later stage → token mechanism

Deliberately plural, so that nobody has to treat their own data as their only asset.

09Roadmap

Not a delivery schedule. The order in which trust is earned.

Each phase is defined by what becomes true for a person, not by which technology ships. Nothing here is claimed as finished.

Full roadmap
  1. Phase 01Now

    Market entry & validation

    Someone installs the Node because they want to.

    Web2 → acquisition → Node → consent → local processing → data layer → first use case

  2. Phase 02

    Identity, emotion & trust

    Your signals become state you own.

    Identity State → Emotion State → ZTAL™ → Trust Layer → ZK Privacy

  3. Phase 03

    Distributed infrastructure

    Verification stops depending on us.

    P2P / WebRTC → Validation → Node Scoring → Consensus → Anti-fraud

  4. Phase 04

    Oracle & Web3

    Any application can consume emotional state.

    Oracle → Blockchain → Smart contracts → Indexing / API

  5. Phase 05

    Intelligence, anomaly & security

    The infrastructure protects the person it learns from.

    Behavioral analysis → Anomaly detection → Emotional risk analysis → Security

  6. Phase 06

    Ecosystem interoperability

    Emotional context becomes shared infrastructure.

    Web2 ↔ Web3 ↔ dApps ↔ DAOs ↔ AI systems

10What we will not build

The refusals are the specification.

It is easy to describe what an infrastructure does. What defines this one is the set of things it is architecturally prevented from doing.

  • A surveillance infrastructure

    A human–machine interaction infrastructure built on consent, transparency and voluntary participation.

  • A Web2 lake of personal emotion

    Sensitive data kept encrypted and decentralized, never centralized in a conventional database.

  • Raw personal data on-chain

    Proofs, references, hashes, verifiable states and events on-chain. Nothing readable about a person.

  • A closed application

    Open infrastructure: other apps, APIs, platforms and devices can contribute authorized signals.

  • Another marketplace

    EmotiTribe, a community and wellness layer where value returns to the people who created it.

We are not building an application that collects emotions. We are building the layer that lets emotion be used without ever being exposed.

EmotiLink OS · Architectural position
Request access

Built for people who read the terms.

EmotiLink OS is in Phase 1, market entry and validation. We are looking for the first people to run a Node, and the first applications willing to act on a proof instead of a payload.

No tracking pixel on this page · Consent before signal · Always