CipherOnce
CipherOnce
FeaturesHow it worksSecurity
CipherOnce
CipherOnce

Built for privacy-conscious users. Zero-knowledge architecture designed from day one — your secrets stay yours, permanently.

AES-256-GCM EncryptedZero Server KnowledgeOpen SourceNo Data Retention
Open source on GitHub

Product

  • How it works
  • Features
  • Security
  • Create Secret
  • User Manual

Company

  • About
  • Privacy Policy
  • Terms of Service
  • Security Disclosure

© 2026 CipherOnce. All rights reserved.

All systems operational
Use Case · Passwords

Securely Share Passwords Online

Sharing passwords is often unavoidable — with a colleague, a freelancer, or a family member. The question is never whether to share, but how. Most methods leave a permanent, readable copy in a chat log, inbox, or server. CipherOnce doesn't.

The Real Risks of How Most People Share Passwords

A 2023 industry report found that over 47% of professionals share credentials via email or messaging apps at least once a week. Every one of those messages is a potential liability — stored indefinitely, indexed by email providers, accessible in chat history archives, and potentially visible to IT administrators.

The danger isn't just interception in transit. It's the persistence of the message itself. A password shared in Slack in 2021 is still sitting in that channel today, searchable, readable, and waiting to be discovered if that workspace is ever breached or subpoenaed.

Email

Archived indefinitely. Accessible by IT and email providers. Exposed in breaches.

Slack / Teams

Logged in workspace history. Admin-visible. Retained by the platform.

SMS

Carrier-stored. Unencrypted on most networks. Accessible via SIM swap.

Shared docs

Version-controlled. Shared access means shared exposure. Rarely deleted.

The CipherOnce Approach to Password Sharing

  1. 01

    Paste your password: Type or paste the credential into CipherOnce. It is encrypted immediately in your browser using AES-256-GCM before anything is transmitted.

  2. 02

    Configure access rules: Set a view limit (e.g., 1 view), an expiry (e.g., 1 hour), and optionally add a secondary passphrase that the recipient must know to decrypt.

  3. 03

    Share the link: Copy the generated link and send it through any channel — email, Slack, or SMS. The link contains the decryption key in the URL fragment, which is never logged by our servers.

  4. 04

    Recipient views and the secret self-destructs: The moment the link is opened and the secret viewed, it is permanently deleted from our database. The chat log now contains a dead link, not a live credential.

Additional Security Features for Credentials

  • Dual-factor access: Combine the link (something they have) with a passphrase (something they know) for two-factor access control on a single secret.

  • View count limits: Restrict access to exactly one view. The moment your intended recipient opens the link, it is burned. If they haven't opened it yet and the link is accessed, you know it was intercepted.

  • Expiry enforcement: Set a maximum window of validity. Credentials shared for temporary access can have a 1-hour or 1-day expiry, ensuring the link becomes worthless after the access window closes.

  • Authentication walls: For internal team use, require that the recipient be a registered CipherOnce user — adding an identity layer to the access control.

Common Password Sharing Scenarios

Onboarding a contractor

Share temporary credentials that expire after 24 hours and can only be viewed once. Confirm receipt before expiry.

Wi-Fi guest access

Share a network password without exposing it in a chat thread that guests or others may see later.

License & activation keys

Send software keys that self-destruct after delivery — no more keys lingering in email threads.

Emergency access

Share a master password or recovery code with a trusted person, with a configured expiry and view limit.

No account required · Free forever · Open source