In short
Fusion is the moment a person, their device, a touchpoint and the platform are bound together into one verified relationship. It happens once, takes a few seconds, and everything else — Connections, private messages, passwordless sign-in, payments — is built on top of it.
The part that surprises people: Fusion is not a login and there is nothing to remember afterwards. A binding is not an account credential you re-enter; it is a fact the platform keeps on your behalf, and it is separate for every relationship you form.
On this page
The problem Fusion solves
Almost every digital relationship starts by asking a stranger to prove who they are, then storing something risky — a password, an email address, a phone number — so the next visit can be recognized. That works, and it costs both sides something. The person hands over contact details before they know whether the relationship is worth anything. The organization collects a pile of details it now has to defend, most of which belong to people who will never come back.
Fusion inverts that. Instead of identifying a person by information they hand over, the platform binds the relationship itself: this human, on this device, arriving through this specific touchpoint. Once that binding exists, the person can be recognized on every later visit without disclosing anything, and can then decide — separately, later, per relationship — what they want to reveal.
That is why the platform describes itself as relationship infrastructure rather than as a login system. The binding is the product. Sign-in, messaging and payments are things you can hang off it.
The four things that get bound
Read the four boxes left to right and the guarantee falls out of them. The person is present because a biometric was satisfied on the device. The device is genuine because its keys live in the phone's secure hardware and cannot be copied to another handset. The touchpoint is genuine because a Linxy Mark, tag or code has to be read to reach this point at all. The platform records the resulting binding so nobody has to redo the work.
What actually happens the first time
- You arrive through a touchpointYou scan a Linxy Mark, tap a tag, enter a code, or open an invitation link. Nothing has been shared yet.
- The Linxy App opens and confirms it is youFace or fingerprint. This is the step that makes the binding mean something: without it the platform would only know a device was present, not a person.
- You are shown what you are about to enterWho is on the other end, and — for a brand — what they are asking to see. Nothing is disclosed before this screen is answered.
- The binding is createdPerson, device, touchpoint and platform are joined. On a brand relationship this happens the moment you agree; between two people it waits for the other person to accept.
- The relationship appears in your ConnectionsFrom here on it is a place you can return to, not an event that happened once.
The ways a Fusion can begin
All of these produce the same kind of binding with the same protections. They differ only in how the first contact is made, and in what the other side learns about how you arrived.
| Starting point | How it feels | Typically used for |
|---|---|---|
| Scanning a Linxy Mark | Point the App at a printed image, pack, sign or label | Anything physical — the most common path, and the one that proves a real object was present |
| Tapping an NFC tag | Hold the phone against the tag | Reusable placements: badges, table tents, shelf edges, doors |
| Entering a code | Type a short code into the App | Spoken, broadcast or printed-in-small-type situations where scanning is awkward |
| Opening an invitation link | Tap a link sent to you directly | Person-to-person introductions, and follow-ups by email or message |
The other side is told which of these you used, because it is genuinely useful context — “scanned your card” and “used your invitation link” describe different meetings. It is context about the encounter, not information about you.
Bind once, then biometric
After the first time, the sequence is: open the App, satisfy the biometric, tap the relationship. No code, no password, no scan — and nothing to lose or write down. The touchpoint has done its job and does not need to be present again.
Behind that, the platform is free to refresh the cryptographic material that backs the binding whenever it needs to. You will not see it happen and nothing you hold becomes stale, because the thing you hold is the relationship, not a secret.
What Fusion is not
| It is often assumed to be… | What it actually is |
|---|---|
| A password replacement | Closer, but too narrow. Passwordless sign-in (LinxyPass) is one thing built on Fusion; messaging, Connections and payments are others |
| A social account or profile | There is no public profile, no follower count and no directory of people. Nothing about a Connection is visible to anyone outside it |
| One identity used everywhere | Each relationship is bound separately. Nothing links them to each other on the far side |
| Proof of who you are, to everyone | Proof that a verified, accountable person is present. Your actual identity is disclosed only where you choose to disclose it |
| A location or presence check | Unrelated. Location gating is a separate, optional feature of a Mark |
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| Scanning opens content but no relationship forms | That Mark is not set up for connection — most Marks simply deliver content | Expected. Only touchpoints configured for it can start a Fusion |
| The App asks for a biometric every time | Working as designed — the biometric is what proves a person, not just a phone, is present | Nothing to fix. It replaces every password you would otherwise be typing |
| “Not accepting connection requests right now” | The person you are trying to reach has turned off inbound requests | Ask them to turn it back on. It is a setting on their side, not a fault on yours |
| A person-to-person request stays pending | The other person has not answered yet. Requests are not automatic | Wait, or ask them directly. Unanswered requests expire after fourteen days |
| Nothing recognizes you on a replaced phone | The binding includes the previous device | Use the account recovery path. Do not expect a password reset to exist |
| A brand relationship shows almost nothing about you | You disclosed almost nothing, which is the default | Also working as designed. Open the connection and share more if you want to |
Things people commonly get wrong
Related reading: Types of Connection, Consent, and what each side can see, Private channels and message privacy, and Recovering your account after losing your device.