Last Updated: August 2026
Safe2Send (safe2send.cc), created by Akira Akiyama ("we", "us", or "our"), is built with privacy-first principles. This Privacy Policy explains how information is handled when you use our WebRTC file-transfer tool.
1. Data Controller & Contact Information
Safe2Send serves as the Data Controller for processing signaling metadata strictly necessary to connect users.
- Entity Name: Safe2Send
- Privacy & Support Inquiries: support@safe2send.cc
- Service URL: https://safe2send.cc
2. Data We Do NOT Collect or Store
- File Contents: We do NOT see, intercept, inspect, or store any files, filenames, or content transferred using the Service. All file transfers happen strictly Peer-to-Peer (P2P).
- User Identities & Activity Logs: We do NOT maintain audit logs, user accounts, timestamped activity records, or sender/receiver connection histories. We do not track who sent what file to whom.
3. Local Browser Storage (On Your Device Only)
To support resume-after-interruption transfers and remember your display preferences, Safe2Send stores a limited amount of data locally in your own browser. This data is NOT transmitted to, accessible by, or stored on our servers:
- Language Preference: Your chosen interface language is saved in your browser's local storage. It contains no personal information and is used solely to display the interface in your preferred language.
- Transfer Resume Fragments: To allow an interrupted transfer to resume, in-progress file fragments may be temporarily cached in your browser's IndexedDB storage. These fragments remain on your device only and are never uploaded to our servers.
- You Stay in Control: All of the above exists solely on your device. You may clear it at any time via your browser's developer tools, or by using the in-app "Clear local data" control, which removes the current room's local data while keeping your language preference. Not clearing it does not affect the Service's functionality — it only occupies local storage space on your device.
4. Information We Handle & Purpose
- Ephemeral Signaling Data: To bridge connections between peers, our signaling server temporarily relays session description protocol (SDP) messages and network connection information (such as IP addresses). While IP addresses may be considered personal data under certain regulations, this data exists solely in volatile memory (RAM) during the active signaling phase to establish the WebRTC connection and is immediately and permanently purged afterward.
- Aggregated Statistics: Our servers collect and aggregate anonymized global usage metrics, limited to:
- Total number of successful transfers.
- Total volume (size) of data transferred.
Once aggregated, these metrics contain no identifying information and are used solely to display aggregate public site status and usage statistics.
5. Visibility Between Users
By design of WebRTC P2P protocols, connecting peers inherently exchange network routing metadata (e.g., IP addresses) directly with each other to establish a direct connection channel. By using Safe2Send, you acknowledge and accept this technical operational necessity.
6. Third-Party Services & Cookies
We do not use persistent tracking cookies, ad networks, or third-party analytics trackers that follow individual user identities across the web.
7. Legal Basis & Data Subject Rights (GDPR / Data Protection Compliance)
- Legal Basis for Processing: Ephemeral processing of IP addresses during signaling is based on our Legitimate Interest (GDPR Art. 6(1)(f)) to facilitate the specific network connection requested by the user.
- Data Minimization: We follow the principle of Data Minimization by retaining zero persistent personal data or user logs once a connection sequence completes.
- Your Rights: Under data protection regulations (such as GDPR or local laws), users have rights to request access to, correction of, or erasure of their personal data. However, because Safe2Send operates on a strict "No-Logs" basis and holds no persistent personal data tied to user identities, we generally hold no retrievable records to fulfill personal data access or erasure requests. If you have any inquiries regarding data protection, please contact us at support@safe2send.cc.
8. Security
While signaling communications are secured via HTTPS/WSS and P2P transfers are encrypted by standard WebRTC protocols (DTLS/SRTP), no system can be guaranteed 100% secure. You are encouraged to use strong, optional room passwords when creating room links.
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated revision date.
10. Children's Privacy
The Service is NOT intended for or directed to individuals under the age of 16 (or the legal age under local data protection laws). We do NOT knowingly collect, handle, or persist personal data from children.