SecretNote - 自己破壊するプライベートノートを共有
読まれた後に自動的に自己破壊する暗号化メッセージを送信できます。SecretNoteは、機密ノートとプライベートメッセージを共有できる無料のウェブベースサービスです。暗号化されたノートを安全に送信するための秘密のリンクを生成 - あなたの機密情報は完全にプライベートで保護されます。
Check more toolsプライベートメッセージを共有するためにSecretNoteを使用すべき理由は?
あなたのプライベートノートはブラウザ内で暗号化され、読まれた後に消えます。
ゼロ知識アーキテクチャ
SecretNote encrypts every message using AES-256 directly in your browser before anything is sent to the server. The decryption key is embedded in the URL fragment - the part of the URL after the # character. Web browsers do not transmit the URL fragment in HTTP requests, so the key never reaches the server. The server stores only encrypted ciphertext. Without the key, that ciphertext cannot be read by anyone, including SecretNote.
自動消滅メッセージ
When a recipient opens the note link, the ciphertext is fetched from the server and decrypted locally in their browser. The server then immediately and permanently deletes the ciphertext. No backup, log, or cached copy is retained. If the same link is opened again seconds later, it returns a not-found response because the data no longer exists on the server.
完全に匿名
No account, email address, or personal information is required to create or read a note. The only data stored server-side is the encrypted ciphertext, a randomly generated note ID, and an expiration timestamp. None of these values are linked to any identity. SecretNote does not use tracking pixels, fingerprinting, or persistent identifiers.
How SecretNote protects your data
A step-by-step explanation of what happens to your message
Encryption happens in the browser
When you write a note and click Encrypt, your message is encrypted using AES-256 inside your browser tab. A random 256-bit encryption key is generated locally for each note. Neither the plaintext message nor the encryption key is ever transmitted to the server.
Only ciphertext reaches the server
The server receives only the encrypted ciphertext - a block of unreadable data that is meaningless without the key. The server stores this ciphertext under a random ID and holds it until the link is opened or the expiration timer runs out.
The decryption key lives only in the URL fragment
The generated link contains both the note ID and the decryption key. The key is placed after the # character in the URL, which is called the URL fragment. Browsers do not include the URL fragment in HTTP requests sent to the server. This means when a recipient opens a SecretNote link, the server receives only the note ID - the decryption key is never transmitted.
Permanent deletion after the first read
When the recipient opens the link, their browser uses the key from the URL fragment to decrypt the ciphertext locally. The server then permanently deletes the ciphertext. The note cannot be read a second time, and no recovery is possible after deletion - not by the recipient, not by SecretNote.
人々がSecretNoteで共有するもの
パスワードと認証情報
ログイン詳細、APIキー、アクセストークンをチャットログやメールスレッドに残さずに共有できます。
機密文書
デジタルチャネルに残るべきではない財務データ、契約書、個人情報を送信します。
DevOpsおよびITシークレット
SSHキー、データベース認証情報、設定シークレットをチームメンバー間で安全に送信します。
プライベートメッセージ
消えていく機密ノートを送信 - 真のプライバシーに値する瞬間のために。
SecretNote vs other ways to share sensitive data
Why email and chat apps are not designed for one-time secrets
| Feature | SecretNote | メールアドレス | Chat Apps |
|---|---|---|---|
| End-to-end encrypted | |||
| Message deleted after reading | |||
| Server never sees plaintext | |||
| No account required | |||
| Leaves no message history | |||
| Expiration timer | |||
| Free, no registration |
よくある質問
Answers about encrypted notes, zero-knowledge security, and safe data sharing
To send personal data securely, use a tool that encrypts the content before transmission and does not retain a permanent copy. SecretNote encrypts your message in the browser using AES-256, generates a one-time link, and permanently deletes the note after it is read. Send the link through any channel, set an expiration timer, and enable burn-after-reading. This is significantly more secure than sending data through email or chat, which store message history indefinitely.
No. Email is not designed for secret delivery. Messages can be forwarded, indexed by email providers, stored in backups, and accessed by anyone with access to either inbox. API keys sent over email may remain accessible for years. 使用 SecretNote instead - credentials are encrypted in the browser, the server never sees the plaintext, and the note is permanently destroyed after the recipient opens it.
Ideally, never. If temporary access is unavoidable, rotate the password immediately after use and share it only through a self-destructing encrypted note. Using SecretNote means the password cannot be recovered from a chat log, email thread, or server log after the note is opened and deleted.
No. When a note is opened, the server permanently deletes the ciphertext. The decryption key exists only in the URL fragment, which is never stored by SecretNote. There is no database backup, server log, or cached version that contains the plaintext. Even the SecretNote team cannot recover a note that has been read and deleted. This is the defining property of the zero-knowledge, burn-after-reading design.
Avoid passwords, API keys, SSH keys, private keys, recovery codes, identity numbers, tax IDs, and unredacted personal records in normal chat apps. These messages are stored on servers indefinitely and can be accessed if the account or server is compromised. Use SecretNote for this type of data so it does not remain in chat history.
For sensitive data, yes. Email attachments are often duplicated across inboxes, mail servers, and backups. The file may persist for years in locations neither sender nor recipient controls. Files shared through SecretNote are encrypted before upload, stored only as ciphertext, and permanently deleted after the recipient downloads them.
You can set the auto-destruction time for unviewed notes in Options before creating the link. The default is 3 days. Available options range from 1 hour to 30 days. Once a note is viewed with burn-after-reading enabled, it is destroyed immediately regardless of the expiration timer. A note that is never opened is deleted when the timer expires.
Zero-knowledge encryption means the service provider never has access to the content of the data they store. In the context of SecretNote, the server stores only the encrypted ciphertext of your note. The decryption key is never transmitted to the server - it exists only in the URL fragment, which web browsers exclude from HTTP requests. The result is that SecretNote staff, server administrators, or anyone with access to the server infrastructure cannot read the content of any note.
AES-256 (Advanced Encryption Standard with a 256-bit key) is a symmetric encryption algorithm used by governments, banks, and security professionals worldwide to protect sensitive data. A 256-bit key provides 2 to the power of 256 possible combinations, making brute-force attacks computationally infeasible with current or foreseeable computing technology. SecretNote uses AES-256 to encrypt every note directly in the browser before anything is transmitted to the server.
A URL fragment is the portion of a URL that comes after the # character. For example, in a SecretNote link, the fragment contains the decryption key. Web browsers do not include the URL fragment in HTTP requests sent to the server. This means when a recipient opens a SecretNote link, the server receives only the note ID - not the decryption key. The key is used entirely within the recipient's browser to decrypt the ciphertext locally. The server never learns the key at any point.
Burn-after-reading means a note is permanently deleted from the server the moment it is opened and decrypted by the recipient. The link stops working immediately after first use. This is the default behavior for SecretNote. It ensures that even if the link is later intercepted, forwarded, or found in a message history, the data it pointed to is already gone and cannot be retrieved.
An expiration timer deletes a note after a set time period regardless of whether it has been opened. For example, a note set to expire in 1 hour will be deleted after 1 hour even if nobody read it. Burn-after-reading deletes the note the moment it is first opened. Both options can be combined in SecretNote: a note set to expire in 1 day with burn-after-reading enabled will be deleted after 1 day if unread, or immediately upon first read - whichever comes first.
Yes. SecretNote is operated by RapidFoundry LTD, a company based in the European Union, and the service is built with GDPR compliance in mind. Notes are stored as encrypted ciphertext only, with no personally identifiable information linked to the content. Because SecretNote uses zero-knowledge architecture, the service processes no personal data contained within the notes themselves. A privacy policy and terms of service are available on the website.
Yes, SecretNote is completely free. No subscription, payment, or account registration is required to create or read notes. All core features - AES-256 encryption, self-destructing notes, file attachments, expiration timers, burn-after-reading, and password protection - are available without any cost.
その他のプライバシーツール
プライベートなデータを安全に共有するために必要なすべてが揃っています - 無料、アカウント不要、ブラウザで動作します。
SecretNote
プライベートなメモを書き、ワンタイムリンクを生成して共有できます。メモは読まれた瞬間に自己消滅し、何も保存されず、情報が漏れることもありません。
SecretScreen
スクリーンショットをアップロードして、自己消滅する共有リンクを取得できます。画像はアップロード前に暗号化され、最初の閲覧後に削除されます - 永続的なホスティングはありません。
SecretFile
任意のファイルをアップロードして、ワンタイムダウンロードリンクを共有できます。ファイルはエンドツーエンドで暗号化され、受信者がダウンロードした後に完全に削除されます。
ハッシュジェネレーター
ブラウザ上でMD5、SHA-1、SHA-224、SHA-256、SHA-384、SHA-512のハッシュを即座に生成できます。入力内容がサーバーに送信されることはありません。
パスワードジェネレーター
長さと文字セットを完全にコントロールして、強力なランダムパスワードを生成できます。すべてローカルで実行されるため、パスワードがサーバーに送信されることはありません。