Get started

Introduction

Developer docs for sharing a secret without putting it in the conversation.

These pages document the PrivateNote developer tools. PrivateNote turns sensitive text and files into encrypted links that expire. Create a note from your editor, terminal, or AI workflow, or on the website at privatenote.ai. Encryption runs locally before upload; the decryption key stays in the link’s URL fragment.

Choose your tool

How it works

  1. Create your note locally. Choose an expiry and whether it should burn after reading.
  2. Your tool encrypts the content and uploads ciphertext to PrivateNote.
  3. Share the generated link. Its #fragment contains the key the recipient needs to decrypt.
  4. The recipient opens and reveals the note. The read limit and expiry determine when access ends.

Understand the privacy boundary

PrivateNote’s server receives encrypted content and the metadata needed to enforce access rules. Anyone who has the full link may be able to open the note, so treat the link as sensitive.

For agent workflows, pass file paths to MCP. Pasting a secret into a prompt exposes it to the model before encryption. The current MCP host can see the returned sharing link, even when it never sees the file’s plaintext.

Read the security model before handling production credentials.

Next steps

Something unclear?Help us improve these docs

Search setup guides, tools, and troubleshooting.