AnySign Vault
Your file leaves. Your control doesn't.
Attach a document to an email and it is gone: forwarded, downloaded, kept forever, and invisible to you. Vault sends the same document as a link you paste into the thread you were already replying to. Only the people you named can open it, it expires on the date you chose, and one click takes it back.
TRY IT
Name who gets in. Then open it as someone else.
Add an address or a whole domain, open the link as Ada and as Sam, and read the log that results. Every line is one the product writes.
Nobody has opened the link yet.
ONE LINK'S LIFE
It happens inside the email thread you are already in.
What you keep after you hit send.
Encryption is table stakes and everybody has it. What almost nobody has is a document that still answers to you a fortnight later.
Only people you named get in
A link cannot exist without an allowlist. Name individual addresses, allow a whole domain, or both. Everyone else lands on a page that tells them nothing about the document.
The link expires when you say
Pick 7, 30, 90 or 365 days when you create it, or no expiry at all. After that the link is dead, including for the people who already opened it.
Revoke works on the next click
Revoking kills the link, every live session and every outstanding code in one transaction. Edit the allowlist instead and the change lands just as fast.
A view log that names them
You see the link was opened; from the moment someone puts an address in, every step after it — code sent, failed, denied, verified, viewed, downloaded — is written down against that address.
Forwarding gets nobody in
The URL is not the credential. Whoever holds it still has to be on your list and still has to prove the address is theirs, and that is re-checked on every request.
THE LINK IS NOT THE CREDENTIAL
Holding the URL gets nobody in.
Whoever opens a Vault link still has to be one of the addresses you allowed and still has to prove that address is theirs. That check runs on every request, including the file download, and every attempt is written down.
- Allowlist re-checked on every request, the download included
- A six-digit code emailed to the recipient's own address: ten minutes, five attempts
- Revoke ends the link, every live session and every outstanding code in one transaction
- Append-only log: opened, code sent, code failed, denied, verified, viewed, downloaded
FROM CODE, OR FROM YOUR AI
Share, watch and revoke from code.
Vault documents live on /v1/vault: store a file, share it to a named allowlist with an expiry, and revoke it with one call. The view log is queryable, so your stack can react the moment a document is opened — or denied.
- Store, list and download Vault documents on /v1/vault from code
- Allowlists, expiry and revocation are API fields, not dashboard-only settings
- MCP server handles the envelope side, so the agreement can go out before the share does
npm i @anysign/sdkSend the consulting agreement to [email protected]
- list_templatesConsulting agreement
- create_envelope[email protected] · signer
- send_envelopeenv_8f14e2
envelope.completed · sealed, webhook delivered
Works from
- Claude
- ChatGPT
- Cursor
- Gemini
- Copilot
- Perplexity
Built for the people who send the same documents every week.
- AccountantsSend draft accounts, tax packs and fee proposals as links only named clients can open, with an expiry date, one-click revoke and a log of every view.See the use case
- BrokersShare lender packs, policy documents and client financials as links tied to named addresses, with an expiry you set, instant revoke and a full view log.See the use case
- RecruitersSend CVs, offer letters and references as links only the named hiring team can open, with an expiry, one-click revoke and a log of every open.See the use case
Vault is free while AnySign is in beta: a hundred share links a month, with named allowlists, expiry and one-click revoke, and no card required.
What the beta includesThe questions people actually ask.
Does the recipient need an AnySign account?
No. They click the link and type the six-digit code we email to their own address, which is good for ten minutes and five attempts. Anyone already signed in to AnySign with a verified email skips the code.
What happens if the link gets forwarded?
Nothing useful for whoever receives it. The URL proves nothing on its own: the person opening it still has to be one of the addresses you allowed, and we re-check that on every single request, including the file download.
Can I take a link back after someone has opened it?
Yes. Revoking ends the link and every live session and code behind it in one go, so it stops working on the next click even for someone who had it open a minute ago. Removing a single address from the allowlist does the same for just that person.
What exactly goes into the view log?
Every attempt, welcome or not: opened, code sent, code failed, denied, verified, viewed, downloaded. Every open is an unnamed line, because nobody has named themselves yet; everything after someone enters an address carries it, with the IP, the browser and the time, refusals included.
Can the same document go out for signature afterwards?
Yes. One click turns a stored PDF or Word file into a draft envelope in the signing builder with the document already attached, so the pack you shared is the pack that gets signed.