Practical guides to sharing sensitive information
Plain-language guidance for choosing safer channels, setting useful limits, and understanding what encrypted links can and cannot protect.
Secure sharing guides
How to send a password securely
A password should not sit indefinitely beside the account name and other context that makes it useful. This guide explains a practical, risk-aware way to deliver a password when you cannot avoid sharing one.
How to share an API key securely
API keys often grant direct machine access without an interactive sign-in. A careful handoff combines a narrowly scoped credential, a browser-encrypted delivery channel, independent recipient verification, and prompt rotation.
How to share recovery codes securely
Recovery codes can bypass ordinary multi-factor authentication, so each unused code should be treated like a powerful single-use password rather than an ordinary note.
Secure file sharing versus email attachments
Ordinary email creates readable copies across multiple systems. A browser-encrypted file link can reduce stored plaintext and limit retrieval, while still requiring trusted recipients and endpoints.
How Dead Drop file sharing works
A Strumio Dead Drop is a browser-encrypted chat attachment with a chosen access limit. Each successful claim counts, and the final permitted claim locks later access and queues stored ciphertext for deletion.
How to protect your primary email address
A temporary receiving address can separate short-lived signups and unfamiliar contacts from your primary inbox, but it does not make ordinary email confidential or prove who sent a message.
Temporary email versus primary email
Primary email and temporary email solve different problems. One supports durable communication and recovery; the other limits how long an address remains reachable and connected to your main inbox.
How private chat without an account works
An account-free Strumio room is a temporary two-person encrypted text conversation. Its complete invitation grants access, so safe use depends on careful delivery, participant verification, and realistic expectations.
One-time secret link versus encrypted chat
A one-time link is designed for one focused release; encrypted chat is designed for temporary back-and-forth conversation. Choosing the narrower feature reduces unnecessary access and history.
A practical guide to Split-Key secret sharing
Threshold sharing divides access across distinct participant fragments so one fragment is insufficient. It can reduce reliance on one holder, but link delivery, viewer devices, recovery planning, and post-reconstruction handling still matter.
Password manager versus secret link
A password manager is designed to store and manage credentials over time. A secret link is designed for a focused handoff. They can complement each other, but neither should be stretched into the other's role.
How expiring secret links work
Expiration limits how long Strumio will make an encrypted payload available. It narrows the retrieval window, but it cannot revoke plaintext that a viewer already copied or make the underlying credential expire.
How browser-side encryption protects a secret
Browser-side encryption moves encryption and decryption to the sender's and recipient's browsers. Strumio receives ciphertext for protected content, while links, devices, identity checks, and operational metadata still require care.
What AES-256-GCM does in Strumio
AES-256-GCM combines encryption with an authentication check. Strumio uses the browser Web Crypto API so protected message and file content becomes authenticated ciphertext before upload.
How a URL fragment carries an encryption key
The portion of a URL after # is a fragment. Browsers normally do not send it in HTTP requests, which lets Strumio deliver ciphertext from the server while the recipient browser receives key material from the complete link.
How 2-of-3 secret sharing works
A 2-of-3 Split-Key configuration creates three distinct participant fragments and requires any two to contribute before an authorized viewer can reconstruct the encrypted payload's key in the browser.
How one-time secret links work
A one-time secret link is designed to release an encrypted message once and make the stored payload unavailable afterward. That is useful for delivery, but it is not the same as guaranteeing that only the intended person saw the message.
How browser encryption protects shared text
Browser-side encryption changes what a message-delivery service needs to receive. Instead of sending readable text and asking the server to protect it, the browser encrypts first and uploads ciphertext.
Private chat, group conversations, and Dead Drops
Strumio chat is designed for temporary encrypted conversations rather than permanent message history. This guide explains direct and group rooms, invitation links, optional passwords, Panic Close, encrypted files, and Dead Drop access limits.
Use guidance that matches the risk
These guides focus on short, sensitive handoffs and honest tradeoffs. For long-term team access, use individual accounts, a password manager, or a dedicated secrets-management system instead of relying on a delivery link alone.
Start with how Strumio works, or create an account when an encrypted, expiring handoff fits your situation.