10seconds SECURE
Enterprise-Grade Ephemeral Messaging

Professional Secure Communications. End-to-End Encrypted. Ephemeral by Design.

In an era where every exchange is logged, analyzed, and retained — 10 Seconds is a professional encrypted communication software designed for minimal server-side data retention, end-to-end confidentiality, and ephemeral session management. Built for organisations where confidentiality is a governance requirement.

10s
Message lifespan
30 min
Max chat duration
0
Server-side message storage
E2E
NaCl + AES-GCM
NaCl Curve25519 Encryption
No server-side message persistence
No phone number at signup
Privacy-by-design architecture
Password never sent in clear

Every conversation you have today is a data point someone else controls.

Many messaging workflows are designed to retain and synchronize conversations over time. Device histories, cloud chats, backups, and service metadata can outlast the discussion. End-to-end encryption protects message content, while retention practices vary by platform and configuration.

For legal teams, executive committees, M&A workstreams, HR decisions, and sensitive internal discussions, this is an unacceptable exposure.

Permanent server-side storage
Cloud chats, device histories and backups can preserve messages long after a discussion ends.
Metadata exploitation
Who you speak with, when, how often. Metadata reveals as much as content — and is rarely encrypted.
Third-party data exposure
Platform breaches, legal discovery, regulatory audits — your internal communications can be compelled or leaked.
No ephemeral channel by default
Most enterprise tools offer no genuine temporary channel for truly sensitive discussions.

Why 10 Seconds is categorically different

Every design decision was made with a single principle: the server should never be able to read, retain, or betray your communications.

End-to-End Encryption

NaCl public-key encryption (Curve25519/XSalsa20/Poly1305), with AES-256-GCM for D3 video chunks. Your private key is generated on-device, encrypted with your password, and never transmitted in plaintext.

Self-Destructing Messages

Every message is automatically removed from display after 10 seconds. No in-app history or scroll-back. Configurable up to 20 seconds. Device-level captures may persist.

30-Minute Session Lifespan

Every chat room has a 30-minute countdown. The app closes the session when the countdown ends, and D3 video transfers respect a server-checked deadline. There is no server-side message archive. Device-level or network-level captures may persist.

No Server-Side Message Storage

Messages are relayed in real time and are not written to any persistent database. The server processes encrypted relay traffic only. Server-side message content is not retained beyond the active session.

Multi-Layer Authentication

SHA-256 client-side hashing (WebCrypto native) before transmission. Server re-hashes with bcrypt cost 12 inside an isolated thread pool. Raw passwords never sent or stored at any point.

Auto-Destroy on Empty

When all participants have left and the room is empty, the server schedules session cleanup after 30 seconds.

⚡ KEY FEATURE

Forensic Watermarking

Every session displays an account-linked watermark with the participant's username, date and verifiable fingerprint. It remains visible in in-app media viewers and can help identify the account displayed in a shared capture. Screenshot alerts are limited to supported native apps; the web version does not detect screenshots. The watermark does not prove who made or shared a capture.

Encrypted Media & Documents

Exchange images, PDFs, voice recordings and video inside the conversation. D3 video transfers use encrypted chunks and recipient acknowledgements, while media viewers remain inside the app.

Separate Room Credentials

Your account login and room access are separate. Joining a conversation requires its session name and shared password, so an account alone does not grant access to every room.

Trace the account shown in a capture

10 Seconds combines account-linked watermarks with screenshot alerts in supported native apps. The web version does not provide screenshot detection. No app can prevent every form of capture.

Account-linked forensic watermark

A visible watermark carrying the viewer's username, date and fingerprint is rendered across the conversation and its in-app media viewers. It can remain visible in captures that include the marked area. The fingerprint can be checked by an administrator.

LIVE

Native screenshot alerts

Available in supported native apps only. Screenshot alerts depend on the operating system and the capture method. The web version does not detect screenshots. An alert does not identify who shared a capture, and external cameras remain outside detection.

Fingerprint verification

A capture with a readable, valid fingerprint can be linked to the account and UTC day displayed. This can support an internal review, but does not prove who captured or shared the image. Evidential value in formal proceedings depends on the applicable jurisdiction and procedural rules.

Why this matters for you
In a confidentiality breach, account context can help an internal review. With 10 Seconds, a visible watermark is a deterrent before the breach and an account reference for review after it. Executive communications, legal counsel, journalistic sources, M&A rooms: an additional accountability layer inside the room.

Full stack, in writing

No marketing claims. Here is every cryptographic primitive at every layer. Verify it in the Security Overview and reproduce it from the open specifications below.

Specifications — version 2026.4
Message encryption
TweetNaCl box (Curve25519 ECDH + XSalsa20 + Poly1305); D3 video chunks: AES-256-GCM
Private key at rest (WC1)
AES-GCM 256-bit · PBKDF2-SHA256 · 600 000 iterations
Password transit
SHA-256 client-side (WebCrypto) · plaintext never leaves the device
Password at rest
bcrypt cost 12 · offloaded in a gevent thread pool
Room identifier
HMAC-SHA256 · anti-enumeration · constant-time password comparison
Billing at rest
Fernet (AES-128-CBC + HMAC-SHA256) · master key held outside the database
Server logs
Fernet-encrypted lines · usernames HMAC-SHA256 pseudonymised · ERROR level only
Forensic watermark
Account-linked visible DOM + canvas overlay · server-issued fingerprint · admin verification
Transport
TLS 1.3 · HSTS 1 year + includeSubDomains + preload · strict CSP
Infrastructure
gunicorn + geventWebSocket · Redis-backed relay · pooled MySQL connections
Full details, operational posture and auditor notes in Security Overview and Transparency Report.

Built to the standards auditors ask for

The controls below draw on published security standards and guidance. We document the cryptographic primitives and operational posture for review.

OWASP ASVS 5.0.0
Application Security Verification Standard
Security controls include bcrypt cost 12, PBKDF2-SHA256 with 600,000 iterations for WC1 keys, and constant-time HMAC-SHA256 comparisons. ASVS provides the verification framework.
NIST SP 800-63B-4
Digital Identity Guidelines
Digital-identity guidance used when reviewing password hashing, salted credential storage and authentication controls.
GDPR
Regulation (EU) 2016/679
Art. 25 Privacy by Design (E2E encryption as default), Art. 32 technical safeguards (Fernet log encryption, HMAC pseudonymisation), DPA framework ready.
UAE PDPL
Federal Decree-Law No. 45 of 2021
Personal data protection, lawful processing basis, subject rights honored. Publisher established in Meydan Free Zone, Dubai.
UAE Cybercrime Law
Federal Decree-Law No. 34 of 2021
No circumvention tooling bundled; no VPN or anonymisation layer promoted; AUP forbids unlawful use in any applicable jurisdiction.
DSA (EU)
Regulation (EU) 2022/2065
Transparency reporting (Art. 15 & 42), law-enforcement procedure (Art. 9), warrant canary. Published Transparency Report updated October 2026.
TLS 1.3
RFC 8446
Transport-layer encryption, strict HSTS 1-year with includeSubDomains and preload, no downgrade allowed.
CSP Level 3
W3C Content Security Policy
Strict Content Security Policy, no unknown third-party scripts, X-Frame-Options DENY, cross-origin opener/resource policies same-origin.
No ISO 27001 certification is claimed. We align with the controls that matter for an E2E encrypted messaging platform in 2026 and publish our posture openly rather than relying on a seal of approval.

What we do, continuously

Not just the standards we follow — the operational posture we maintain over time, verified on every deployment.

Key Rotation — Server
Scheduled rotation policy
The operational checklist includes session-signing key rotation, rollback validation and user re-authentication checks.
Key Rotation — User
Controlled key lifecycle
Account key pairs remain stable across sign-ins. Personal password changes re-encrypt the existing private key; an owner-managed sub-account reset generates new keys and makes earlier encrypted messages inaccessible.
Ephemeral Content Lifecycle
No server-side message archive
Messages are relayed without a persistent server-side history and disappear from the app after their display window. Copies captured on a participant's device are outside this lifecycle.
Separation of Secrets
Isolated keys per data category
Session cookies, billing records, affiliate attribution and forensic watermarks each use dedicated keys with distinct lifecycles. This reduces the impact of a compromised secret.
Automated Rollback
Health checks and fallback
Deployment tooling checks service health after an update and can reinstate the previous working version automatically if those checks fail.
Continuous Testing
700 regression checks in the test plan
The regression test plan covers authentication, crypto, affiliate attribution, billing records, watermarks and key-management workflows. Results are reviewed for each release.
Manual Sanity Checks
621-point manual release checklist
Alongside the automated suite, a maintained manual sanity-check list contains 621 points across 38 sections — covering UI flows, legal pages, admin tools, email delivery, account-watermark verification and multi-device scenarios.

How a session works

Four steps. Authentication required. Username is pseudonymous — no real identity required.

01

Initialize

Create a named session with a strong password. Your device unlocks your account's encryption key locally — the private key is never sent in plaintext.

02

Distribute

Share the session name and password out-of-band — verbally, or via a separate secure channel.

03

Communicate

Exchange end-to-end encrypted messages, images, audio, documents, and video. The server relays ciphertext only — it does not hold decryption keys.

04

Terminate

Close the session manually or let the 30-minute timer expire. Server-side session data is purged from server memory. Note: device-level or network-level capture by third parties may independently persist data.

Non-negotiable constraints

30-minute countdown
The app closes the session when its 30-minute countdown ends. D3 video transfers enforce the session deadline on the server.
10-second message window
Messages are removed from display after 10 seconds. Configurable to 15 or 20 seconds.
Admin termination power
The session creator can close the room immediately for all participants at any time.
Automatic empty-session purge
Sessions detected as empty are scheduled for cleanup after 30 seconds.
Ephemeral by design
Server-side message content is not written to persistent storage. No server-side recovery is possible after session expiry.
Password-gated access
Every session requires a password to create and to join. No open sessions.
Forensic watermarking
Each screen carries an account-linked visible watermark and a server-verifiable fingerprint. The admin panel can identify the associated account and UTC day. A valid fingerprint does not authenticate the entire image or prove who captured or shared it.

How 10 Seconds compares

How 10 Seconds compares
Capability10 SecondsWhatsAppSignalTelegram
End-to-end encryptionNaCl + AES-GCMYes — personal chatsYesSecret Chats only
Server-side message retentionLive relay; no persistent historyTemporary delivery queues and mediaTemporary encrypted delivery queuesCloud Chats; Secret Chats device-specific
Auto-destruct messages10 / 15 / 20 seconds after display24h / 7d / 90dCustom timerConfigurable in Secret Chats
Auto-close conversation session30-minute app countdownNo fixed room countdownNo fixed room countdownNo fixed room countdown
No phone number at signupYesNoNoNo
Personal-message decryptionOn participants’ devicesOn participants’ devicesOn participants’ devicesOn devices for Secret Chats
Account-linked watermarkVisible + fingerprint verificationNo built-in account watermarkNo built-in account watermarkNo built-in account watermark

Transparent pricing. Individual or Enterprise.

Pseudonymous crypto, invoiced card payment, or multi-seat packs for teams — same end-to-end encryption.

👻 Ghost Protocol
Pseudonymous · USDT cryptocurrency · No real identity required
PSEUDONYMOUS
Annual
$280.00
for 12 months · USDT
Subscribe
test
$1.00
for 12 months · USDT
Subscribe
🧾 Clear Trail
Invoiced · Credit / debit card · Full receipt · USD billing
BEST VALUE
Annual
$280.00
per year · USD
Subscribe
test
$1.00
per year · USD
Subscribe
🏢 Enterprise Packs
Buy a pack, create multi-user sub-accounts for your team
View all enterprise packs
5 SEATS
Enterprise 5
$1 120.00
per year · excl. VAT
≈ $224 per seat
You create and manage each sub-account directly. Card or USDT.
Subscribe
20 SEATS · ⭐ BEST SELLER
Enterprise 20
$3 808.00
per year · excl. VAT
≈ $190 per seat
You create and manage each sub-account directly. Card or USDT.
Subscribe
100 SEATS
Enterprise 100
$14 560.00
per year · excl. VAT
≈ $146 per seat
You create and manage each sub-account directly. Card or USDT.
Subscribe

Some conversations should not exist in a database.

10 Seconds is built for organizations and individuals who understand that true confidentiality requires a channel designed from the ground up for minimal data retention and end-to-end encryption.

Create a Secure Account
No phone number. No compromises.

Keep your credentials safe. Personal accounts have no forgotten-password reset or encryption-key recovery. Team sub-account resets are managed by the workspace owner.