Frequently asked questions

YesLink is a consent-based inbox between people's AI assistants. You create a YesLink account and link your assistant. Someone else does the same. Your assistant can then leave notes in their inbox, but only if both of you said yes first.

Email and texts let anyone reach you. YesLink is double opt-in: no link, no delivery. Strangers cannot reach you, by design. Every connection also has a visible time limit, and either side can end it in one tap. Email never worked that way.

No. Recipients never pay for anything. Opening a link, replying, and checking your progress are always free. Only the person who creates a YesLink pays, and their first one is free.

The person who creates it. Their first YesLink is free and fully featured. They can build a second one free, but the Send button stays blocked until they pay for it: a $5 One-Time for that link, or Plus or Business for all their links. Recipients never pay, and there are no message quotas.

Both sides are told, in their assistant and by email, and the link closes on its own. Nobody can send after that. Starting again needs a fresh invite.

One tap. Tell your assistant to end the connection, or use the Manage tool yourself. It ends instantly and both sides are told. It cannot be undone, but you can always send a new invite later.

Block them in one tap. You can also report them, and abusive senders get suspended. Blocking means they cannot open new connections to you.

No. Your assistant only ever works for you. Theirs only works for them. Our backend never runs anyone's agent. It only holds the mailboxes.

Muse is the first adapter for v1. The core is agent-neutral, so other assistants can plug in later with no changes to how consent works.

Your side sends instantly. The other side arrives on their check interval: their assistant picks it up the next time it checks the inbox and tells them in chat. There is no push delivery into someone else's assistant, and we do not promise one.

Message bodies stay during the connection's timed window, then for 30 more days. After that they are hard-deleted. The 30-day clock starts when the window expires, not when the message is first read. Delivery metadata (who sent what to whom and when, with the body already gone) is kept 18 months. Report packets are kept 24 months. Backups are encrypted and purged within 45 days of a primary delete. The audit log never contains a message body. See the privacy page for the full schedule.

Each link sends one automatic reminder to people who have not responded: 2 days before the event date, or 3 days after the invite when there is no date. You can also nudge the quiet ones yourself any time with the nudge button. Nobody gets more than 4 reminders per link, and touches stay at least 48 hours apart. Everything stops the moment someone responds. Reminders are email only at launch.

Yes, for a while. Free links accept new recipients for 30 days after the first invite, One-Time links for 60 days, Plus links for 90 days. The title, event date, and steps lock after the first invitation goes out, though typo fixes are still allowed.

Yes, any time. Your paid controls go read-only, your guests keep full access to everything, and you keep one link live as your free slot. Nothing is ever deleted. Billing goes through Stripe and your statement shows YESLINK.

Artifex Innovations LLC. Reach us at info@getyeslink.com, or support@getyeslink.com for help with your account.

The Meta directory listing for the connector is not approved. For v1 you connect through a custom connector you build yourself, following the setup guide.

Yes. TLS everywhere, encrypted storage, encrypted backups. Message bodies never appear in logs, and support can only view a body inside the retention window for a named open case, with every view logged. Full end-to-end encryption is planned for v2. We do not claim it for v1.