Privacy Policy
What send collects, what it never can, and why. In plain language.
Last updated 16 September 2026
The short version. send is built so we can't read your conversations. Calls, chats, files and voice/video notes are end-to-end encrypted and travel directly between devices over WebRTC. Our servers only ever hold ciphertext they cannot decrypt, plus the minimum needed to run an optional account — a handle, a one-way hashed email, your contacts list, and (if you turn on alerts) a push subscription. No trackers. No ads. No profiling. Nothing sold. Ever.
1Who we are
send (send.xwira.tech) is a private communications tool — file transfer, chat, voice & video calls, async voice/video notes, and a personal recorder — operated from Malaysia by xwira. This policy covers the send web app (PWA) and the send by xwira native apps for iOS and Android, which are the same web app wrapped for the app stores and talk to the same hosted backend. Questions or requests: salam@xwira.tech.
2Two ways to use send
Ephemeral · no account
Share a code, connect two browsers, transfer or talk peer-to-peer, close the tab. Nothing about the session is stored — no account, no history, no content. This is the default.
Account · opt-in
Create a handle so people can reach you again, keep contacts, and receive end-to-end encrypted notes. Only then do we store the small amount of account data described below.
You can use send fully without an account. Everything in section 4 applies only if you choose to create a handle.
3The heart of it — we cannot see your content
Your messages, files, calls, and notes are end-to-end encrypted on your device before they leave it. They flow directly between devices over an encrypted WebRTC channel (media is protected with DTLS-SRTP). We are not in the middle, so we have no ability to read, scan, or hand over your conversations — we simply don't have them.
Async voice and video notes are the one thing that must wait on a server for the recipient to pick up later. They are encrypted on your device and only the ciphertext is parked in our storage. We hold the encrypted blob, not the key; we cannot open it. It is delivered play-once and then deleted.
What we never store or see
Message text · file contents · call audio/video · note contents in the clear · your encryption keys · your location · your contacts' phone numbers or address book.
What we do store (account only)
Handle · one-way hashed email · hashed recovery code · your contacts list (handles you mutually added) · push subscription (only if you enable alerts).
4Exactly what an account stores
| Data | Why | Retention |
|---|---|---|
| Handle | So contacts can find and reach you. | Until you delete your account. |
| Email (one-way hashed) | Optional. Only to prevent duplicate accounts and to help recover access. Never displayed, never emailed to, never shared. Stored as a salted hash — we can't reverse it to your address. | Until you delete your account. |
| Recovery code (hashed) | Lets you restore your handle. Stored hashed; the plaintext lives only on your device. | Until you delete your account. |
| Contacts graph | The handles you and another person have mutually added, so your contacts list persists. | Until you remove a contact or delete your account. |
| Push subscription | Only if you turn on call/message alerts — a browser Web-Push endpoint (or an APNs/FCM token in the native apps) so we can wake your device for an incoming call or note. Carries no message content. | Until you disable alerts or delete your account. |
| Encrypted note blobs | Ciphertext of async voice/video notes awaiting pickup (see §3). | Deleted after play-once / short expiry. |
Your private key never leaves your device. We do not store your name, phone number, address book, birthday, or any advertising identifier — because we don't ask for them.
5Connection metadata
To pair two devices, a small signaling relay briefly passes the WebRTC handshake between them. Like any web server, it necessarily processes network-level connection details (such as an IP address) for the moment of connection, and it sees a short room/contact code — never your content. This is transient and used only to make the connection.
When two devices can't reach each other directly (restrictive networks / NAT), media is relayed through our self-hosted TURN server using short-lived credentials. TURN forwards the already-encrypted stream — it cannot decrypt it, and we do not record the media. We may keep minimal, short-lived operational logs (e.g. IP, timestamp, room code — never content) to protect the service against abuse and to answer valid legal process; these are kept briefly and used for nothing else.
6The recorder & transcription
The personal recorder is your own private space, not a shared feature. Recordings and their transcripts are encrypted at rest and tied to your account. Transcription runs on our own self-hosted speech model inside our cluster — audio is not sent to any third-party AI or transcription service. Nothing from the recorder is shared with anyone unless you choose to send it.
7No tracking, no ads, no selling
- We run no third-party advertising and no cross-site tracking. We set no advertising cookies and use no ad SDKs.
- We never sell or rent your data, and we don't share it with data brokers.
- We keep only the minimal privacy-respecting, aggregate visitor counts needed to know the service is up — no profiles that follow you around the web, and none on this policy page itself.
- The app stores only essential technical storage on your device (e.g. your session/keys) so send works — not for tracking.
8Device permissions
send asks for a permission only when a feature needs it, and only to make that feature work on your device:
- Camera & microphone — for video/voice calls and voice/video notes. The stream is peer-to-peer and end-to-end encrypted; we never receive it.
- Notifications — only if you enable alerts, to wake your device for an incoming call or note.
- Files / storage — to pick a file to send and to save a file you receive.
You can revoke any of these in your browser or OS settings at any time; the rest of send keeps working.
9Your rights & choices
You can sign out, remove contacts, disable alerts, or delete your account and everything tied to it at any time — from the app, or by emailing salam@xwira.tech. Because we deliberately hold so little, there is very little to export; we'll provide what we have on request. Deleting your account removes your handle, hashed email, hashed recovery code, contacts graph, push subscription, and any pending encrypted note blobs.
10Children
send is not directed to children under 13 (or the minimum age of digital consent where you live), and we do not knowingly collect data from them. If you believe a child has created an account, contact us and we'll remove it.
11Security
End-to-end encryption is the core of the design, keys stay on your device, transport is HTTPS/WSS with DTLS-SRTP for media, and stored secrets (email, recovery code) are one-way hashed. No system is perfectly secure, but by holding almost nothing we keep the impact of any incident as small as possible.
12Changes
If we update this policy we'll change the date at the top; material changes will be highlighted in the app. Continued use after an update means you accept the current version.
Contact. Privacy questions, data requests, or an abuse report: salam@xwira.tech. For emergencies or serious crimes, please also contact your local authorities.
🔒 End-to-end encrypted · nothing is ever uploaded in the clear — it goes straight between your devices.
See also our Terms & Acceptable Use.