--- url: https://talk.deep.institute/about/index.md --- # How in-browser encryption and text remixing work Deep Talk combines browser-based text encryption with a multilingual text remixing tool: 1. **Remix text** lightly changes letter or character order for a playful, less literal result. 2. **Protect a message** preserves the exact original behind a password using modern authenticated encryption in your browser. The first is a reversible-looking word game that actually loses the original order. The second is designed for private messages that must be recovered exactly. ## Text remixing for any language Choose automatic mode or select a remix style when the text needs different handling. | Remix style | What Deep Talk changes | What it tries to preserve | | -------------------- | ------------------------------------------------------- | ------------------------------------------------ | | Inside words | The inside of longer Unicode words | First and last graphemes, spaces, punctuation | | Across characters | Continuous character runs | The first character, punctuation, unrelated text | | Across mixed scripts | Word-like segments containing different character types | Punctuation, spaces, unrelated text | For example, “Words can still feel familiar” may become “Wrods can sitll feel fmailiar.” Readers can often infer the meaning from word shape, context, grammar, and punctuation. Results vary. Some writing patterns and short words do not tolerate reordering well, and automatic detection will not be perfect for every mixed-script sentence. ## Exact-match resistance is not invisibility Remixing can break a simple verbatim comparison or exact-word filter. It does **not** guarantee that moderation software, a language model, search system, or another person will fail to understand the text. Use it for playful communication, captions, inside jokes, and light visual disguise—not as a security boundary. ## In-browser text encryption Protect mode asks for the original message and a password. Both remain in the current browser while Deep Talk creates a shareable protected message. The recipient pastes that result into Open mode and enters the same password. The protection is authenticated: a wrong password or changed message fails instead of producing plausible-looking text. The normal interface explains this in plain language; implementation details remain available in the [safety guide](/security/index.md). ## A safer sharing habit Send the protected message through your normal chat, then share the password through a different trusted channel. For example, send the protected text in a messaging app and tell the password by phone. ## What Deep Talk does not protect against No browser tool can protect a message from someone who already controls the device, records the keyboard, reads the clipboard, or sees the screen after the message is opened. The recipient can also copy or forward the original text. Read the [plain-language safety explanation](/security/index.md) for the full boundary, or return to the [Deep Talk tool](/index.md#tool). --- url: https://talk.deep.institute/index.md --- # Remix text. Encrypt messages. No account. Encryption and decryption happen entirely in your browser. [Start](#tool)[Privacy & security](/security/) Live preview**Local only** Remixed✓ Words can still feel familiar. ↓ **Wrods can sitll feel fmailiar.** **Encrypted with a password**✓ Share the result. Send the password separately. For any language ## A little disorder can still be readable. Writing systems have different rhythms, but pattern and context can survive a little disorder. Bring whatever you write—these samples are only a glimpse. Wrods can sitll feel fmailiar. 文也字可很以好玩。 ことばで遊んみでよう。 Las plaarbas tmaibén jguean. Les mtos rsetent fmailiers. Wöretr blieben trtozdem lsebar. The tool ## Choose what you want to do. ● Processed on this device **Remix text**Add personality; break exact matches**Protect a message**Modern in-browser encryption**Open a message**Password plus integrity check How should it remix?Decide automaticallyInside wordsAcross charactersAcross mixed scripts Original text0 charactersRemixed text0 characters Remix textClearCopy result Remixing can break simple exact-word matches, but it is not encryption and cannot guarantee that a filter or analysis system will not understand the text. Three useful outcomes ## Playful when you want. Private when you need. Use remixing for expression and resistance to simple exact matches; use encryption when the original must remain recoverable. Less literal ### Break exact matches Light rearrangement can move beyond simple verbatim matching while keeping familiar word shapes and context for human readers. Playful ### Add personality Turn captions, chats, and inside jokes into something more surprising and expressive. Private ### Encrypt in your browser Protect the exact message with modern authenticated encryption. Wrong passwords or changed content will not open. Three small steps ## Private sharing without an account. Protect here, send the protected text in your normal chat, and share the password another way. 1. **Protect locally**Your message and password stay in this browser. 1. **Share separately**Send the protected message and password through different channels. 1. **Open with confidence**Changed content or a wrong password will not produce a message. ## Modern encryption, entirely in your browser. Deep Talk protects both secrecy and message integrity without an account or upload. Technical details remain available, not forced into the interface. [Read the safety explanation →](/security/) Common questions ## What people usually want to know. Can remixed text be restored perfectly? No. Remix mode loses the original order. Use Protect when someone must recover the exact message. Does remixing bypass every word filter? No. It can break simple exact matches, but advanced moderation or language systems may still understand the text. Does Deep Talk encrypt and decrypt text in the browser? Yes. Message and password processing happens in the current browser tab. Deep Talk has no message-upload or account endpoint. Why does the protected result change every time? Fresh randomness is added each time so repeated messages do not produce the same result. Can a forgotten password be recovered? No. Passwords are not uploaded or saved, so there is no recovery key. --- url: https://talk.deep.institute/privacy/index.md --- # Privacy notice Deep Talk is a static browser tool. You do not need an account, and the tool does not provide a server endpoint for uploading the message, password, or protected result. ## Text you enter Text entered into the Remix, Protect, and Open panels is held in the current page state while the tab remains open. It is not intentionally stored in a Deep Talk database. ## Clipboard access Deep Talk writes to the system clipboard only after you click a copy button. Other apps, browser extensions, or people with access to the device may be able to read clipboard contents, so clear sensitive clipboard data after use when appropriate. ## Normal hosting requests Opening the site still makes ordinary network requests to Firebase Hosting for HTML, JavaScript, CSS, icons, and other static files. The hosting provider may receive standard connection data such as IP address, request time, browser information, and requested path under its own policies. ## No password recovery Passwords are not uploaded or stored for recovery. Losing the password means losing access to the protected message. ## Your device remains part of the trust boundary A compromised browser, extension, device, or operating system may observe what you type or display. Deep Talk cannot detect every form of local compromise. Read [Safety and message protection](/security/index.md) or return to the [tool](/index.md#tool). --- url: https://talk.deep.institute/security/index.md --- # In-browser text encryption safety Deep Talk is a browser-based text encryption tool built around one simple promise: **your message and password are processed in the browser you are using, not sent to a Deep Talk message server.** ## How in-browser text encryption works 1. You enter a message and password. 2. The browser turns that password into a temporary key. 3. The browser protects the message and adds a check that detects changes. 4. You copy the protected result and share it. 5. The recipient uses the same password to open it. If the password is wrong or the protected message was changed, Deep Talk refuses to open it. ## What stays private by design - Deep Talk has no account system. - The tool has no business endpoint that receives your original message, password, or protected message. - Passwords are not saved for recovery. - The same message produces a different protected result each time. ## What Deep Talk cannot protect against - Malware, keyloggers, or a compromised operating system. - A malicious browser extension that can read the page or clipboard. - Someone watching the screen or reading the message after it is opened. - A weak or reused password that another person can guess. - A recipient who copies, screenshots, or forwards the original message. - A future compromise of the site’s hosting account that serves altered JavaScript. For important information, verify the site address, use an up-to-date browser, choose a strong unique password, and share that password through a different channel.
Optional technical details Protected messages use authenticated encryption in the browser. The current format uses AES-256-GCM, with a key derived from the password through PBKDF2-HMAC-SHA-256 and a fresh random salt and nonce for every message. The message format is versioned so future upgrades can be distinguished, and protected messages created by the previous version remain readable for compatibility. The technical names describe implementation choices; they do not remove the device and recipient risks listed above.
Read [how in-browser encryption and text remixing work](/about/index.md), return to [Protect a message](/index.md#tool), or review the [privacy notice](/privacy/index.md).