Request, do not collect
Ask for the fact you need. Let the person decide what answers. A yes can stay a yes instead of becoming a photograph of everything.
Liir for business
Meet the person. Keep less of them.
Liir lets a business ask for a fact, a file, an approval, or a payment. The person answers from their own Liir. You receive exactly what the relationship needs without collecting the rest of who they are.
No passwords · no pile of ID photos · no customer key that works anywhere else
atelier@liir.netBusiness Liir · example
Complete one checkout
The person answers the order in one approval.
EligibilityAre you over 18?
Yes · signed
FulfillmentShipping for this order
One label
ApprovalApprove $64.00
Waiting for you
The person's Liir reads the request, applies
their rules, and asks them before anything new crosses.
What changes
A customer relationship without the identity pile.
A business still keeps what belongs to its side of the relationship: orders, obligations, support history, and receipts. Liir removes the reusable secrets and unnecessary copies gathered around them.
One customer, one relationship
Each relationship gets its own path. The key a customer uses with you means nothing anywhere else.
Keep evidence, not credentials
A signed approval shows what was approved, in which relationship, and when. It is not a secret anyone can use twice.
Make a breach less interesting
Keep the records you genuinely need. Stop accumulating passwords, card numbers, identity documents, and universal join keys around them.
5reusable dependencies
The business holds the person
- A password or recovery path
- A copied identity document
- A universal email or phone number
- A reusable payment credential
- A profile that joins activity elsewhere
A breach inherits every reusable edge.
The inversion
The person holds the path to the relationship.
Today the business holds the account and the person asks to be let back in. Liir turns that around. You keep your own records. The person holds the key that can speak into them.
Switch the model and five reusable things collapse into signed answers that work only here.
What crosses
Ask for the smallest useful answer.
Asking for less is not a privacy setting you turn on afterward. It is the shape of the request. You ask for what the sale actually needs, and the answer you get back works only with you.
Business needs
Person chooses
Business receives
What never needs to cross
Age eligibility
Approve once
Signed over-18 answer
Birth date, address, ID photograph
Ship this order
Share for shipping
One-order shipping label
A permanent customer profile
Return customer
Use this relationship
Pairwise capability and history
One name for the person that works across sites
Receive a record
Choose the fact or file
The approved file, and who signed it
Vault access or unrelated records
Approve a payment
Approve amount and destination
Signed authorization and receipt
Card number or bank credentials
The person's side
The operator works for the person.
The person's Liir works for the person, not for you. It takes your request, applies the person's rules, keeps their separate paths apart, and moves only what they have allowed.
Reads the requestOne company asks, through one relationship.
Applies the person’s ruleStanding permission can answer. Anything new can ask the person.
Moves the answerThe approved fact, file, or action reaches only its intended destination.
ANTI-GRAPH: Liir looks up paths, not
people. It keeps no map of who knows who.
Person side
Request arriving
Relationship requestShipping for order #8421
Ask once
1
Capability resolvesOnly this relationship
Now2
Policy evaluatesAsk once for shipping
Waiting3
Person authorizesApproved for this order
Waiting4
Scoped answer movesNothing else opens
WaitingDeliveredOne shipping label crosses · vault remains sealed
Complete
The commercial model
You are not buying a database.
Liir does not sell access to a person. A company pays for the plumbing around a relationship: requests, signature checking, approved transfers, uptime, and support.
Companies pay us to move the right thing safely without making the thing itself our product. Volume and enterprise terms follow real usage. The person stays the customer of their own Liir. None of this is on sale yet: today it is a working demo and a written spec.
Relationship formationPer connection or volume
Proof and verificationPer verified response
Authorized transferUsage based
Payment orchestrationTransaction fee
Enterprise integrationSupport and service terms
Where it fits
Start where the identity pile hurts most.
Liir does not ask a business to replace everything at once. Begin with one request, one checkout, or one relationship where copied identity and reusable credentials create the most cost and risk.
One approval instead of another form
The person answers shipping, eligibility, and payment in one go. The merchant gets what it needs to fill the order, not another login and card record.
Verify the fact, not a folder of evidence
Ask for signed facts or records. The person shows what qualifies them without emailing copies of everything behind it.
Let the relationship bring them back
The private path recognizes a returning customer. Standing permissions and subscriptions stay visible in their Liir, and they can end one at any time.
Keep the whole transaction in one chain
Approval, shipping, refund, and receipt stay attached to the same relationship. A refund goes back the way the payment came.
Start with one relationship
Show us what you ask people for today.
A fact. A file. An approval. A payment. We will map what Liir replaces, what moves through the relationship, and what remains entirely yours.
Talk to Liir