Use dummy content for your first run. A short note is enough to check creation, clipboard behavior, and recipient reveal.
1. Pick a tool
For a browser-only start, open privatenote.ai. If you prefer an installed tool, use the Chrome extension or editor extension. The CLI and MCP server require Node.js 18 or later.
2. Create a test note
Enter a harmless message such as “PrivateNote test — no real credentials.” Keep burn after reading enabled and choose a short expiry.
npx privatenote-cli --expire 15m --output-url-only < demo.txtFor the CLI alternative, create demo.txt yourself with the dummy message. Its contents become the note body, rather than a downloadable attachment.
4. Verify the lifecycle
- Reload after reveal. A read-once note should no longer reveal its content.
- Create a second note for expiry testing. Leave it unopened until its lifetime has passed, then verify access is refused.
- Use a new note for each test. A consumed link cannot serve as a fresh test fixture.
Keep going
Follow your tool’s guide for passwords, sign-in, defaults, and troubleshooting. Use the four-tool test checklist for a structured acceptance run.