Questions, answered plainly

1-z-2 lets independently made apps send useful things to one another, even when they were built differently. A task can leave your to-do app and arrive as a usable reminder in someone else's app; neither of you has to adopt the other's software.

Think of it as a post office for personal software. Your @handle is the address. 1-z-2 works out how the receiving app needs the information, adapts it and delivers it.

Use 1-z-2 when your personal app needs another person. For example: sending a task, sharing a workout, exchanging a recipe or comparing plans when each person has made their own app.

It replaces the awkward part where somebody must switch apps, read a screenshot, copy from a message or type the same information in again.

No. You keep using the app you made. 1-z-2 sits between it and the apps other people made. The website gives you an address and a dashboard for managing apps and contacts; the useful work still happens in your app.

No—that is the point. Their app can look different and organise the information differently. Both apps connect to 1-z-2; each one keeps its natural format.

Structured, useful items: a to-do, workout, recipe, calendar event, itinerary or similar piece of information that an app can act on.

Files, photos and attachments aren't sent — only an item's details. To share a song or a photo, put a link to it in the item. Every connected app also gets a simple conversation area for short text notes between contacts.

What you send can arrive as a readable web page instead of disappearing. If the handle is not claimed yet, that page can invite its owner to claim it. Once they connect an app, future compatible items can land there.

Each app shows 1-z-2 examples of the useful things it sends and receives. 1-z-2 translates between the two app formats, not human languages. It builds and checks that route once, then remembers it for next time.

If an honest adaptation cannot be made, 1-z-2 can refuse rather than inventing information. Every adapted item says what happened, and the receiver can compare it with the untouched original for 10 days.

The new app can use the same @handle and contacts. It shows 1-z-2 its current formats, and the routes to your contacts' apps are prepared again in the background. The app changes; your address and people do not.

No. If you can ask an AI to build an app, you can connect that app to 1-z-2. The claim page hands you the exact instruction to paste. If something goes wrong, the error messages are written for your AI to read and fix.

Any tool that can build an app and fetch a web page: Claude, Cursor, Lovable, Replit and the rest. There is no separate plugin to install. Paste one instruction while the tool builds or rebuilds your app; it reads the setup guide and adds the connector. It does not matter what kind of app it builds you — a web page, a phone app, a Python script — the guide covers all of them. See the exact process.

No. Ordinary app delivery requires an accepted contact connection. Either person can remove the connection or block the other at any time. See how to verify that behaviour.

Only if you say so. Introductions are off for everyone to begin with. Turn them on in your dashboard's Contacts tab (or in your app) and a friend you share can bring you and one of their friends together, but only when all three of you have turned it on. The other person still has to accept, and you can turn it off again at any time.

While an item is inside its 10-day window: yes. There is no end-to-end encryption yet, and we would rather say so than let you assume otherwise. The guarantee today is time, not blindness: message contents are permanently deleted according to the behaviour described on the data page. End-to-end encryption is on the roadmap.

The basics do not, and will not. Carrying your handle, contacts and messages, and adapting items between your apps—that is the free plan. It has real monthly and storage ceilings sized for genuine use.

Paid plans raise those ceilings and skip the translation queue. Paying buys more of what is already free, never the ability to use the network at all.

Two honest reasons. First, every new pair of app formats costs real money to adapt the first time, so growth has to track what one operator can support. Second, it keeps a young network accountable: everyone here was invited by someone.

No invite? Join the waitlist—codes go out in batches.

It depends on what you still have, so in order:

Another copy might exist. The browser where you claimed your handle keeps the identity until you clear it, and an app project may still contain its .relay-yourname.json file.

You added a recovery email? Then 1-z-2 can mail you a code and you can get back in.

Neither? Then the handle is permanently lost. Your secret key never leaves your device, so there is nothing on our side to reset. That security property has a real price; download the file and add a recovery email.