Secret Sharing
Share secrets securely with a link.
LinkPilot secret sharing lets you send passwords, API keys, and confidential notes through a single link that expires, requires a passphrase, and self-destructs after it is read. You stay in control after sending — revoke, audit, or burn at any time.
No credit card required · Free forever plan
Secret Links are not marketing links.
Secret contents are handled separately from short-link analytics. LinkPilot may show basic delivery/audit events, but secret contents are never used for campaign analytics, profiling, or retargeting.
Secret Links vs Smart Links
Two different jobs, kept intentionally separate. Use the right tool for the right share.
| Secret Links | Smart Links | |
|---|---|---|
| Primary use case | Sending sensitive info you want to control after sending | Branded short links for campaigns and content |
| Expiration | Required — minutes to 30 days, or on first view | Optional — set an expiry if you want one |
| One-time viewing | Yes — burn after read enforced atomically | No — designed to be clicked many times |
| Passphrase protection | Optional, hashed client-side before transport | Not applicable |
| Analytics | None on contents — only basic delivery/audit events | Full click analytics: referrers, geo, device, UTM |
| Audit events | Created, viewed, burned, revoked — per secret | Aggregated click stream and link lifecycle |
| Best for | Passwords, API keys, credentials, confidential notes | Marketing, social, email, QR codes, partner links |
Common use cases
- Sending production credentials to a new engineer
- Sharing API tokens with a contractor or agency
- Delivering one-time access codes to customers
- Passing sensitive notes between team members without email or chat
What you get
Passphrase protection
Add a passphrase so only the intended recipient can reveal the secret.
Auto-expiry
Choose how long the link stays alive — from 5 minutes to 30 days.
Burn after read
Secrets self-destruct after a single view so nothing lingers in inboxes.
Full audit timeline
See exactly when a secret was created, viewed, burned, or revoked.
Why teams choose LinkPilot
One platform for every kind of link
Most tools cover either marketing links or secret sharing. LinkPilot covers both — with the controls, audit trail, and team workflows engineering and marketing teams actually need.
| Capability | Secret Links | Smart Links | Controlled Links |
|---|---|---|---|
| One-time Secret Links | |||
| Expiring links | |||
| Passphrase protection | Partial | ||
| Branded short links | |||
| Link analytics | |||
| Audit events | |||
| Team workflows | |||
| API access | |||
| Revocation | |||
| Custom expiration |
How is this actually secured?
No vague "military-grade encryption" claims — here is the real model. Traffic is TLS-encrypted in transit and stored data is encrypted at rest on managed infrastructure. Passphrases are SHA-256 hashed in your browser before transport, so the raw passphrase never reaches our database or logs.
Burn-after-read is enforced atomically with row-level locking, so two concurrent viewers can never both read a secret. Burned, expired, or revoked payloads are irreversibly redacted. Viewer IPs are SHA-256 hashed with a salt that rotates every 24 hours — raw IPs are never stored — and link unfurlers (Slack, email scanners) receive metadata only: a view is recorded solely on an explicit reveal.
Frequently asked questions
How is secret sharing different from sending a password in chat?
Chat and email keep a permanent copy. A secret link can expire, require a passphrase, and burn itself after one view, so the sensitive value does not linger in someone's history.
Can the recipient forward the secret?
They can forward the link, but if burn-after-read is on, the first viewer destroys it. Add a passphrase shared out-of-band for an extra layer.
Do you store the secret in plain text?
No. Passphrases are hashed client-side before transport and the payload is protected at rest. We never log raw secrets.