Temporary encrypted sharing
Share encrypted content with links that expire.
Send temporary artifacts, instructions or messages from the browser, CLI or MCP. Choose how long they stay available and use one-time access when a resource should only be retrieved once.
Connect your agentEncrypt before uploading
The browser, CLI and local MCP encrypt content locally. The HTTP API stores encrypted content and listing metadata. Remote MCP processes plaintext and keys on the server to perform the operations you request.
Choose a short link or a private link
Default short links entrust the resource key to the server, encrypted at rest. Private links keep the key in the URL fragment, off the server. Both are access links: anyone holding a complete link can open the resource.
Limit the lifetime and the reads
Expired resources become inaccessible and are deleted during cleanup. One-time content requires an explicit opening action and is consumed atomically on retrieval. Revoking an agent key blocks that key; revoke the resource itself to invalidate an existing share link.
How it works
Choose your content
Publish an artifact, message or instruction from a connected agent, the CLI or your browser workspace.
Set the sharing options
Choose the expiry and, when needed, a private link or one-time access. Use the browser, CLI or local MCP when content must be encrypted on your device.
Share and revoke
Send the link through your chosen channel. Revoke the resource when you no longer want the link to work, or let it expire.
Try this prompt
Publish this handoff note to tivq using local MCP, with a private link, a five-minute expiry and one-time access. Return the share link.
Find connection steps in integrations and workflow details in the agent guide.
Questions
Is every MCP connection encrypted locally?
No. Local MCP encrypts content on your device. Remote MCP necessarily receives the plaintext it processes. Choose the local connection for workflows that require encryption before upload.
Does one-time access erase saved copies?
No. It prevents a second retrieval from tivq. A recipient can still save, copy or capture content after opening it.
Are shared resources listed in search engines?
tivq marks share and workspace pages noindex and excludes them from its sitemap. This is an indexing instruction, not an access control: keep the share link confidential.