Privacy Policy
Last Updated: March 21, 2026
This Privacy Policy explains how FetchP2P ("we", "our", or "the Service") manages your information. Unlike traditional file sharing platforms, FetchP2P is designed with a "Privacy First" architecture. We prioritize peer-to-peer connectivity to ensure that your data remains your own. By using our Services, you acknowledge the data practices described in this policy.
We collect minimal information to ensure service availability and security. Our architecture is designed to avoid the collection of personal data wherever possible.
Through our infrastructure providers (including Cloudflare), we may process standard web logs such as IP addresses, browser types, and geolocation data. This data is used solely for rate limiting, DDoS protection, and ensuring the technical stability of our signaling servers.
We monitor aggregate usage metrics, specifically the total number of bytes transferred through the network. This data is processed as a raw numerical value and is not linked to any specific user, file content, or metadata. We do not collect or store filenames, file types, or directory structures.
Service Operations
We use temporary signaling data to establish Peer-to-Peer connections (WebRTC) between users. Once the connection is established, our involvement in the data stream ceases.
Analytics and Growth
Aggregate byte counts are used to understand overall platform usage and to share growth milestones with our community. No individual transfer patterns are analyzed.
Security
IP data is used to prevent automated abuse of our signaling server and to maintain the integrity of our Peer-to-Peer network.
Zero Server Storage
Our core principle is that no user files are stored on our servers. Data streams directly browser-to-browser. There is no central database of transfers, and there is no "history" of sent files once a session ends.
Signaling Server Access
Developers may have access to signaling server logs for debugging purposes. These logs contain ephemeral connection metadata but no content-level data.
Technical Security
All transfers are encrypted end-to-end using WebRTC standards (DTLS/SRTP). This ensures that even our signaling infrastructure cannot read the data passing between peers.
Browser Sandbox
We leverage the browser's security model to ensure that file access is isolated and secure. No software installation is required, reducing the attack surface on your device.
Ephemeral Records
Signaling data and transfer codes are deleted immediately after the transfer is completed or the session times out. Aggregate traffic statistics (byte counts) are retained indefinitely for historical analysis.
We work with trusted infrastructure providers to deliver the Service:
Cloudflare
Used for DNS, CDN, and network security. Cloudflare processes request data in accordance with their own privacy standards to protect our site from attacks.
Because we do not collect personal identifiers or store your files, we have no "Personal Data" to provide, correct, or delete upon request. Your primary control is your 5-character code; do not share it with unauthorized parties.
The Service is not intended for users under 13. By using FetchP2P, you represent that you meet the age requirements in your jurisdiction.
Our signaling server may be located in a different country than you. By using the Service, you consent to the transfer of minimal signaling metadata to establish your P2P connection globally.
We may modify this policy. Continued use of the Service after changes constitutes acceptance. Major changes will be highlighted on our homepage.
For privacy-related inquiries, contact me at [email protected].