Traceless solves three related challenges in one place:
How do you confirm who you are talking to?
How do you send sensitive data out knowing it wont leak?,
How can you have someone to send sensitive data back.
How do these things work together?
Use Verify to prove identity. Use Send data when you already hold a secret and need to deliver it. Use Request data when the other person holds a secret and you need them to return it securely.
All three keep passwords, messages, and files out of the wrong hands. Links expire. Shared content can be opened only once. You can now verify who you are transacting with.
Where to start
After you sign in, open Verify from the profile menu, or go to the home screen. From that home screen you can:
Search for a contact by name or email
Invite a new contact
Start Verify someone, Send data, or Request data
Review recent activity
If your search already selected a contact, Send data and Request data can carry that person into the compose screen so you do not retype the address.
/verify: confirm identity first
Verify is the identity step. You find (or invite) a contact, choose how they prove who they are, send the challenge, and wait for a result: verified, denied, failed, or timed out.
Typical methods include an email link, a text link, email link plus SMS code, a passkey, or an authenticator push when your organization has that integration.
Use Verify when:
You must be sure you are talking to the right person before you act
You are inviting someone new and want a strong first check
You want a passkey on file for later checks
A successful Verify result is proof for that moment. If the situation changes, verify again. For step-by-step method choices, recipient screens, and troubleshooting, see How to use Traceless Verify.
/send-data: you have a secret to send
Send data creates a one-time, expiring link that delivers a message, password, or file to someone else.
On the compose screen you choose the recipient, the content, how long the link stays valid, and any extra protection (for example a passcode or passkey before the recipient can open the data). You send the link or copy it into a channel you already trust.
Use Send data when:
You already have the sensitive information
You need the other person to receive it once, then have it disappear
You have already verified the person, or you trust the delivery channel for that moment
The recipient opens the link, views or downloads the content once, and the payload is removed on the normal Traceless schedule. You do not leave the secret sitting in ticket history or email threads.
/request-data: they have a secret to give you
Request data is the reverse of Send data. You ask someone to return a message or file to you (or to a return address you choose) through a secure link.
You compose the request: who to ask, an optional subject (plain text, not for secrets), how long they have to respond, and how long the returned data remains available after they share it. You can require stronger checks on the request link, on the returned data, or on both.
Use Request data when:
The customer or contact has the password, file, or details
You need those details inside Traceless instead of pasted into a ticket
You want a clear status while you wait for them to respond
The person you ask opens the request, enters the message or file, and shares it. You watch status on the request screen until the data is ready, then retrieve it through the secure return path. The person who submitted the data cannot open what they just sent through the requester’s retrieve path for a Verify-started request. That keeps the secret with the intended return party.
How the three sections relate
Think of one workflow with three doors, not three separate products.
Situation | Start here | Then |
You are not sure who is on the call or in the ticket | Verify | After verified, Send data or Request data if you still need to move a secret |
You have a password or file for them | Send data | Optionally verify first from the Verify home if identity is unclear |
They have a password or file for you | Request data | Optionally verify first so the ask goes to a known contact |
Practical patterns:
Verify → Send data. Confirm identity, then deliver credentials or files to that same person.
Verify → Request data. Confirm identity, then ask that person to return what you need.
Send or Request without a new Verify. Allowed when the contact is already known and the risk for that step is acceptable. The compose screens still let you require MFA on the link itself.
Same contact search. The home search, Verify, Send data, and Request data share the idea of finding an existing contact or adding someone new. Work stays attached to people, not to free-floating paste into tickets.
Recent activity. The Verify home and the full recent list show verification and data activity so your team can see what completed and what is still waiting.
What stays the same across all three
Sensitive content stays inside Traceless links, not in email bodies, chat, or ticket notes.
Links expire. Prefer the shortest duration that still works for the other person.
Optional subjects and notes are not encrypted places for secrets. Use them only for short, non-sensitive context.
Treat every link like a capability. Share it only with the intended person.
Branding on recipient pages follows your organization when it is configured.
Summary
Verify answers “Are we talking to the right person?”
Send data answers “How do I give them a secret that won't leak once they don't need it?”
Request data answers “How do I ask them to give a secret back securely?”
Start from Verify when identity matters. Move into Send or Request when the secret still needs to move. Leave nothing sensitive in the systems you use to communicate.
