Protect the handoff,not just the storage.
Choose an async one-time link, a live browser-to-browser session, or a threshold split for your team. Each mode makes its trust boundary explicit before you share.
Choose the trust boundary
Match the mode to the job
Standard
Async · AES-256-GCM
Maximum Security
LIVELive P2P · X3DH-style + ML-KEM-768
Team Split
Shamir · k-of-n threshold
Included from day one
Full access for 14 days. No card required.
Short-lived by design
Why Teams Switch to Secretus
Every week, teams accidentally expose credentials. Here's how it happens — and how Secretus stops it.
Passwords in Slack messages
DMs get archived, searchable by admins, and exposed in breaches. Credentials sit in plaintext forever.
Credentials emailed to new hires
Email is not encrypted end-to-end. Onboarding emails with temporary passwords are a permanent liability.
API keys shared in docs or spreadsheets
Shared drives keep version history. One misconfigured permission exposes every secret ever stored.
No audit trail, no expiry, no threshold control
When an employee leaves, old threads and shared notes retain access. Critical secrets should require multi-party approval — not trust in one person.
Secretus solves this at the root.
Every secret is encrypted in your browser before it leaves your device. The recipient opens it once — then it's gone. Need multi-party approval? Split it with Shamir's Secret Sharing so no single person can access it alone.
A visible trust boundary
Three Modes for Different Threat Models
Choose the mode that fits your situation. No training required.
Send Now. They Open Anytime.
Generate an encrypted one-time link and share it over any channel — email, Slack, SMS, QR code. Choose expiry from 15 minutes up to 30 days or a custom date. After the first successful access, the link record is invalidated before response and ciphertext cleanup follows separately.
Write your secret
Type your message. An AES-256-GCM key is generated randomly in your browser.
Share the link
The key is embedded in the #fragment — browsers never send this to servers. Only the ciphertext is stored.
They open anytime
Recipient decrypts locally in their browser. No app, no account, no simultaneous presence needed.
Link invalidated after first access
After the first successful access, the server record is deleted before response and the ciphertext object is removed shortly after on a best-effort basis, with lifecycle deletion as a backstop.
Operational control
Built for Business-Grade Security
Every feature designed for security-conscious teams — from a single developer to a distributed org.
X3DH-style + ML-KEM-768
Maximum Security mode: authenticated X3DH-style session setup hybridized with ML-KEM-768, plus per-message symmetric key rotation during the live transfer.
Async Standard Mode
AES-256-GCM encrypted one-time links. Set expiry from 15 minutes to 30 days, or pick a specific date. During normal operation, the URL-fragment key is omitted from the secret endpoint request.
Team Split — Shamir SSS
Split secrets with k-of-n threshold control: 2-of-3, 3-of-5, and more. Optionally set a 24h / 7-day / 30-day expiry on share links. Information-theoretically secure — no single holder can reconstruct alone.
One-Time Viewing
Each Standard-mode link is single-use. After the first successful access, the server record is deleted before response and the ciphertext object is removed shortly after on a best-effort basis, with lifecycle deletion as a backstop.
File & Audio Support
Business supports browser-encrypted file and audio attachments up to 5 MB with the same claim-and-consume one-time link flow.
EU Operation & Privacy Controls
Operated from Romania, EU, with core account infrastructure in eu-central-1, consent-gated optional analytics, and account export/deletion controls. These controls support privacy obligations but are not a blanket legal-compliance determination.
Zero-Knowledge Architecture
During normal operation, Standard-mode endpoints receive ciphertext but not the URL-fragment key, and P2P private/session keys remain browser-held. Compare the P2P safety number over an independent channel to detect identity-bundle substitution.
Hybrid Post-Quantum Component
ML-KEM-768 (NIST FIPS 203) is used as a hybrid layer to reduce harvest-now-decrypt-later exposure during P2P setup.
Installable PWA
Add Secretus to your home screen — no app store needed. Works on iOS, Android, and desktop via Chrome/Edge. Full offline-ready shell with push-installable experience on any device.
Secret Request Links
Reverse flow: generate a request link and ask someone to send YOU a secret. They encrypt it in their browser — only you can decrypt it. Perfect for collecting credentials from contractors or new hires without exposing your own keys.
Delivery Confirmation & Revocation
Know the moment your secret is opened — real-time delivery status shown in the sender UI. Changed your mind? Revoke any unread secret instantly, even hours after sharing the link.
Labels & Structured Templates
Annotate every secret with a plaintext label visible in your audit log and dashboard. Use built-in templates for SSH keys, database credentials, API keys, or Wi-Fi — structured fields with per-field copy and masked passwords.
QR Code — Tap to Reveal
Every secret link has a built-in QR code. It stays hidden by default and only appears when you tap — preventing passive scanning by nearby cameras or screen-recording tools. Auto-hides after 60 seconds.
Flexible Expiry — Pick Any Date
Standard Mode offers preset durations (15 min, 1h, 24h, 7d, 30d) plus a custom date picker — set expiry to any specific day you choose. Team Split links also support optional TTL: 24h, 7 days, or 30 days.
Firefox Browser Extension
Share a one-time secret from any page: right-click selected text or press Ctrl+Shift+S. The same in-browser AES-256-GCM encryption, with SRP sign-in that keeps your password on your device. Track and revoke links from the popup. Available now for Firefox; Chrome is planned.
Built for awkward handoffs
What Teams Use Secretus For
Any time your team needs to share sensitive information exactly once — or require threshold approval — Secretus is the right tool.
Password Sharing
Share database passwords, admin credentials, and service account logins without leaving a permanent record in your chat history.
⚡ StandardTeam Approval Workflows
Split API keys, root credentials, or recovery codes with Shamir's Secret Sharing. Require 2-of-3 or 3-of-5 holders to approve before anyone can access. No single point of trust.
🔑 Team SplitEmployee Onboarding
Send new hires their temporary credentials, VPN access, and system logins securely on day one — credentials expire immediately after first use.
⚡ StandardSensitive Documents
Share contracts, financial summaries, or confidential reports as encrypted file attachments that disappear after the recipient downloads them.
⚡ StandardAPI Keys & Tokens
Distribute API keys, OAuth tokens, and webhook secrets to developers without exposing them in pull requests, emails, or shared docs.
⚡ Standard or 🔑 Team SplitHigh-Security Transfers
When you need browser-to-browser delivery with no server-side secret-payload storage, share directly over P2P with an ML-KEM-768 hybrid handshake.
🔒 Maximum SecurityA different job
Why Not Just Use…?
These categories serve different jobs. Capabilities vary by product and plan; this table compares typical workflows, not every vendor implementation.
| Feature | Secretus | Slack / Teams / Chat | Email | Password Manager |
|---|---|---|---|---|
| Single-use delivery by default Secretus invalidates Standard-mode link metadata before the first successful payload response. | Default | Not typical | Not typical | Product-dependent |
| Recipient needs a product account A Secretus recipient opens the link without signing up; sender access still requires an account and active trial or plan. | No | Usually | Email account | Product-dependent |
| Payload encryption model The relevant distinction is what the provider processes, not whether transport TLS exists. | Browser-side | Product-dependent | Usually transport TLS | Product-dependent E2EE |
| Backend key boundary During normal operation, the secret endpoint does not receive or store the URL-fragment encryption key. | Mode-specific | Product-dependent | Provider processes content | Product-dependent |
| Hybrid post-quantum key agreement for live transfer Secretus Maximum Security combines ECDH with ML-KEM-768 to reduce harvest-now-decrypt-later exposure. | ML-KEM-768 hybrid | Product-dependent | Not typical | Product-dependent |
| k-of-n threshold approval Require multiple parties to reconstruct — no single holder can access it alone. | Not typical | Not typical | Product-dependent | |
| Delivery confirmation Know the exact moment the recipient opens the secret. | Product-dependent | Product-dependent | Product-dependent | |
| Revocation (cancel before view) Invalidate the link immediately after sharing — before it's been opened. | Delete/retention varies | Recall is unreliable | Product-dependent | |
| Full audit log Every create, view, revoke event with timestamps — exportable as JSON or CSV. | Often enterprise-tier | Provider/admin logs | Product-dependent | |
| Hosting and processing location Secretus core origins and persistent stores are in AWS eu-central-1; global edge delivery and external processors have separate footprints. | EU-hosted core | Product/config-dependent | Product/config-dependent | Product/config-dependent |
Password managers are excellent for storing credentials you use repeatedly — Secretus is designed for the complementary task of single-use delivery and prompt ciphertext cleanup.
Security without theatre
Quantum Resistance — What It Actually Means
Under the generic Grover model, AES-256 retains an estimated 128-bit brute-force security level. Maximum Security additionally uses an ML-KEM-768 hybrid component to address key-agreement exposure.
Grover's Algorithm
Attacks symmetric encryption (like AES). A quantum computer running Grover's algorithm can halve the effective key length — so AES-256 becomes the equivalent of AES-128. That still means 2¹²⁸ possible keys to brute-force. Considered secure for the foreseeable future. AES-256-GCM is resistant to this.
Shor's Algorithm
Attacks asymmetric key exchange (like the ECDH used in most key-agreement protocols). Shor's can efficiently break elliptic curve cryptography — the foundation of most key agreements today. Nation-state actors already run "harvest now, decrypt later" attacks. This is what ML-KEM-768 guards against.
Protection by mode
vs. Grover's (symmetric)
AES-256-GCM → 128-bit equivalent. Still strong.
vs. Shor's (asymmetric)
N/A — there is no ECDH key exchange. The key is generated locally and embedded in the URL #fragment. Nothing for Shor's to attack.
vs. Grover's (symmetric)
AES-256-GCM for the actual message encryption.
vs. Shor's (asymmetric)
ML-KEM-768 (NIST FIPS 203) is hybridized with authenticated X3DH-style key agreement to reduce harvest-now-decrypt-later exposure.
vs. Grover's (symmetric)
Shamir's Secret Sharing is built on finite field arithmetic — not AES — but is information-theoretically secure regardless of computing power.
vs. Shor's (asymmetric)
N/A — Shamir's SSS uses polynomial arithmetic over GF(2⁸), not elliptic curves. Quantum computers offer no advantage here.
For Standard Mode, the generic Grover model reduces the brute-force security estimate for AES-256 to roughly 128 bits. This does not cover key-exchange attacks addressed by Shor's algorithm; only Maximum Security adds the separate ML-KEM-768 hybrid component.
Pricing without procurement theatre
Simple, Transparent Pricing
Every plan starts with a 14-day free trial — full access, no credit card required.
Displayed prices exclude applicable VAT, sales tax, or GST. Your final total is shown before checkout confirmation.
Starter
Async one-time secret sharing for individuals
14-day free trial included
- No plan-based monthly secret quota — rate and abuse limits apply
- Text-only secrets
- ⚡ Standard Mode — AES-256-GCM (estimated 128-bit security under generic Grover model)
- Custom expiry: 15 min to 30 days
- One-time viewing — link invalidated before delivery; cleanup follows
- Mode-specific backend trust boundary
- Secret labels & annotations
- Secret revocation — cancel before opening
- Delivery confirmation — know when opened
- 📬 Secret request links — ask others to send you secrets
- Secret templates — SSH, database, API key, Wi-Fi
- Audit log — 90-day history, JSON & CSV export
- Two-factor authentication (TOTP / MFA)
- Installable PWA — iOS & Android
Pro
Add hybrid P2P for high-security transfers
14-day free trial included
- Everything in Starter
- 🔒 Maximum Security — X3DH-style + ML-KEM-768 hybrid P2P
- Zero server storage (P2P mode)
- Priority email support — best effort, no SLA
Business
Full suite: files, voice & k-of-n team approval
14-day free trial included
- Everything in Pro
- 👥 Teams — share your plan with up to 5 members
- 🔑 Team Split — Shamir k-of-n threshold
- Text + file + audio attachments (up to 5 MB)
- API keys — up to 5 keys, REST API integration
- 📊 Compliance PDF — SOC-2, GDPR Art. 30, DORA
- 1-year audit log retention
Enterprise
Custom limits · SSO / SAML · SLA · Dedicated support · Volume licensing · Compliance review
Self-serve, trial first. Sign up for a 14-day free trial — no card required. When you're ready, subscribe in-app through Stripe's secure checkout; plan changes are prorated automatically and you can cancel anytime from your profile. Billed monthly, or annually with 2 months free. Enterprise? billing@secretus.app.
The details matter
Frequently Asked Questions
Three Modes. One Platform. Zero Compromise.
Whether you need async convenience, browser-to-browser P2P, or k-of-n threshold control — Secretus has the right tool for every secret.