Privacy
Draft. This page explains how the service handles data today. It is not yet the operator’s reviewed legal text.
Xferio connects two browsers so a file can travel directly between them. This page lists what the service records while it does that and what it never sees.
File contents
- Files are read from the sender’s device and written to the recipient’s device. They are not uploaded to or stored on Xferio’s servers.
- Browser connections are encrypted in transit (WebRTC uses DTLS). When a direct connection isn’t possible, the encrypted stream passes through a relay server, which forwards it without storing it.
What a transfer records
- File names, sizes and types, so the recipient knows what is coming. A workspace can switch off keeping file names.
- When the link was created, joined, used and ended, and how many bytes the relay carried.
- Names that participants enter, and a one-way hash of their network address for abuse prevention.
- To connect directly, each browser shares its network addresses with the other participant. Recipients and senders can therefore see each other’s IP address.
Accounts and workspaces
- Email address, name, a salted password hash, and an encrypted two-step verification secret if you turn it on.
- Sign-in sessions with the IP address and browser they came from, so you can review and end them.
- An audit log of changes to each workspace, including who made them and from which address.
- For paid plans, the payment provider’s customer and subscription references. Card details are handled by the payment provider and never reach Xferio.
How long records are kept
These are the defaults; the operator may shorten or lengthen them.
- Workspace transfer records, including file names and participant names: 90 days after the link ends.
- Anonymous transfer records: 7 days after the link ends or lapses.
- One-time links inside sent emails: removed after 7 days; the email record after 90 days.
- Expired or signed-out sessions: 30 days.
- Invoices, metered usage and the audit log are kept as financial and accountability records.
Rights and contact
To be completed by the operator: the legal basis for processing, the list of sub-processors (hosting, email delivery, payments), how to request access or deletion, and a contact address.