Use case
Deliver and collect credentials without retaining them in email, chat or tickets
SecretLink encrypts content in the browser, defines recipients and expiry before delivery, and enables credentials to be requested through a protected workflow.
When the process becomes fragile
Passwords and keys remain in email or messaging history beyond the required period.
Credentials requested from clients and suppliers are pasted into tickets accessible to multiple operators.
Recipient, permitted views and duration are not defined consistently.
The workflow with SecretLink
- RuleDefining the recipient, views, expiry and access controls.
- EncryptionEncrypting content in the browser before it is sent to the service.
- RevealExplicit recipient action, without consumption caused by automated scanning.
- ClosureDeletion when the first limit is reached or immediate sender revocation.
SecretLink
SecretLink manages the temporary handover of credentials, keys and sensitive content. The server stores only encrypted content and does not receive the key required to open it.
View the technical product pageRelevant contexts
- Service and support
- Systems and infrastructure
- Staff onboarding
- Suppliers and advisers
Verifiable controls
Initial assessment
The assessment covers secret types, recipients, volumes, duration, identity requirements and required integrations.
Technical questions
Can email scanners open the link?
Visiting the link neither exposes the content nor consumes a view. The count advances only after explicit recipient action.
How are credentials requested?
A request link collects the response and encrypts it in the submitter’s browser. No account is required to respond.