WolfP2PPrivacy notice
For:Legal and privacy readers
No technical knowledge required.Version 1.0.2 — Effective September 4, 2026
This notice explains how Exist.Dev LLC, legally registered in Florida as EXIST.DEV LLC, handles information when you use WolfP2P. Questions or privacy requests can be sent to info@exist.dev.
Privacy at a glance
The most important boundary
WolfP2P's coordination server does not receive, store, or relay the file bytes streamed through the direct browser-to-browser data channel. It also does not receive file metadata, including filenames, folder names, relative paths, file extensions, per-file sizes, manifests, or content-derived verification information, from that channel.
The WolfP2P browser client running locally in each participant's tab necessarily processes the file bytes and file metadata it sends or receives. That local processing remains subject to the browser's permissions and is separate from the coordination data processed by the coordination server.
WolfP2P is not a zero-data service. Its coordination server processes limited coordination data needed to operate, secure, and diagnose the service. What WolfP2P's Server Sees explains the complete categories and purposes.
Information WolfP2P processes
Essential service and security information
When you use WolfP2P, the service may process:
- temporary tunnel state and participation status;
- connection-signaling information used to establish the WebRTC connection;
- network and request information ordinarily visible to an internet service, including IP addresses, IP-derived approximate geography, request URLs, query strings, user-agent strings, request timestamps, and operational correlation identifiers;
- transfer role, lifecycle state, file count, cumulative byte totals, timing, outcome, and coded error categories;
- security and rate-limit information used to prevent abuse and investigate failures; and
- server dependencies, traces, and exception details used for service monitoring.
This coordination data is used to provide the transfer, keep the service secure, enforce limits, diagnose problems, and comply with legal obligations. The coordination server does not receive file bytes or file metadata through the direct channel and does not use coordination data to build an advertising profile.
Optional product analytics
Product analytics is optional and off until you accept it. If accepted, WolfP2P creates a random identifier in that browser. On later document loads it may record the page that began the visit, and it may record transfer-progress events to understand which features are used and where the product fails.
The identifier represents one browser profile, not a verified person or account. At the server boundary it is transformed into a keyed pseudonymous reference; the raw browser identifier is not stored in the analytics destination. Pseudonymous does not mean anonymous.
Declining analytics does not reduce transfer speed, reliability, or access. WolfP2P does not use the analytics profile to select advertising. You can change the choice through Privacy Preferences.
Terms acceptance
When WolfP2P presents effective Terms and you create or join a tunnel, it records the Terms and Privacy Notice versions presented to the browser, the versions current on the server, whether the action was create or join, the time of acceptance, and an opaque acceptance reference.
The acceptance record does not contain an IP address, tunnel code, or analytics identifier. The most recent reference is stored in the browser so it can be included in a dispute notice or arbitration opt-out.
Information you send to Exist.Dev
If you contact Exist.Dev or submit a legal, privacy, copyright, accessibility, or security report, WolfP2P processes the contact details and message needed to answer and document the request. Do not include transferred files, file contents, credentials, live tunnel codes, or unrelated personal information.
WolfP2P does not currently provide user accounts, mailing-list subscriptions, or behavioral advertising profiles.
Why the information is used
WolfP2P uses information only as reasonably necessary to provide and secure the service, enforce the Terms, measure and improve the product when optional analytics is accepted, document choices, respond to requests, meet legal obligations, and establish or defend legal claims.
Sharing and service providers
Exist.Dev does not sell transferred-file information and does not provide transferred file bytes to advertisers.
WolfP2P uses Cloudflare to serve and protect the public site and proxy application requests. It uses Microsoft Azure to host the application, PostgreSQL operational database, Application Insights service monitoring, and the first-party product-analytics destination. These providers process limited information on Exist.Dev's behalf under their service terms. Information may also be disclosed when required by law, to protect people or the service, or in connection with a corporate transaction subject to appropriate safeguards.
WolfP2P currently configures no STUN or TURN servers for the browser peer connection. The current deployment therefore does not send connection-discovery requests to Google through a WolfP2P-configured STUN service. With no ICE server configured, the browsers gather host candidates only; this can establish a direct path on a shared network where browser and network policy permit it, but it does not provide STUN-based traversal between separate private networks.
The receiver obtains the files and transfer information you intentionally offer. WolfP2P does not verify that person's real-world identity; confirm the intended receiver separately before offering sensitive files.
Retention
- Temporary tunnel state, connection credentials, and rate-limit windows expire according to their short operational lifecycles.
- Ordinary essential operational and security records are retained for no more than 30 days.
- Raw optional product-analytics events are retained for no more than 90 days.
- A pseudonymous analytics profile and its governed summary are retained for no more than 395 days after relevant profile activity.
- Minimal consent evidence is retained for no more than five years after the relevant decision or withdrawal.
- Terms acceptance records are retained for no more than six years after acceptance.
- A minimized closed privacy-request record is retained for no more than three years after closure.
A restricted record may be held longer when reasonably necessary for a documented dispute, investigation, security incident, preservation duty, or other legal obligation. Properly deidentified aggregate statistics may be retained longer when they cannot reasonably be linked to a person or device.
Your choices and rights
You may accept or decline optional analytics and later change or withdraw that choice. From the browser carrying the identifier, Your WolfP2P Data can export or erase the associated browser profile.
WolfP2P has no account or identity directory. An email address, name, tunnel code, IP address, or description of a transfer is not used to guess which browser profile belongs to a requester. If the browser identifier has been cleared or lost, Exist.Dev may be unable to locate that profile.
Depending on applicable law, you may also request access, correction, deletion, restriction, or review of a privacy decision. Exist.Dev will acknowledge a human-handled privacy request within 10 business days and respond within 45 calendar days, subject to any permitted extension and any shorter legal deadline. A requester may appeal a denial or limitation within 30 calendar days through the Privacy Appeal form. Exercising a privacy right does not reduce transfer functionality.
Erasure and unlinking
Erasing a browser profile deletes the profile, current identifier, and current consent state and irreversibly unlinks remaining raw events from that browser. Those unlinked events expire within their 90-day maximum. Minimal consent evidence may remain under a non-reversible reference and cannot be used to recreate the profile. A later analytics acceptance creates an unrelated identifier.
Children
WolfP2P is a general-audience service and is not directed to children under 13. Children under 13 may not use it. WolfP2P does not use an age gate, collect a birth date for ordinary use, or infer age from transfer or analytics activity. If Exist.Dev receives information that creates actual knowledge requiring action, it will take the steps required by applicable law.
Security and international access
WolfP2P uses technical and organizational safeguards appropriate to the information it processes, but no internet service can guarantee absolute security. Material incidents will be communicated through legally required channels and linked from WolfP2P Security when public notice is appropriate.
WolfP2P is operated from the United States and is currently offered and supported for the US English market. People may access it from elsewhere, which can result in information being processed in the United States.
Changes to this notice
Material changes receive a new version, effective date, and notice where required. A material expansion of an optional purpose requires a new choice; updated wording alone does not broaden an earlier analytics grant.
Version history: Version 1.0 was effective August 19, 2026. Version 1.0.1 took effect August 20, 2026 and records that optional server-side product analytics and the associated export and erasure endpoints became operational that day. Between the first notice's effective date and activation, the optional analytics interface was visible but the server did not derive analytics subjects or accept optional browser events. No excess collection occurred during that interval. Version 1.0.1 also describes the implemented page measurement more precisely: it records the page beginning a later document load after consent, not every client-side content navigation. Version 1.0.2 took effect September 4, 2026 and corrects the connection-discovery disclosure: the current deployment configures no STUN or TURN servers, so it does not contact Google's public STUN service as previously stated. This correction removes an inapplicable third-party disclosure; it does not add a purpose or broaden collection.
Privacy details and controls
Cookies and browser storage
Review the current first-party storage inventory, its purposes, and the effects of clearing it.
Privacy preferences
Review or change the optional product-analytics choice without changing ordinary transfer functionality.
Your WolfP2P data
Export or erase the browser profile available to this browser, or start another privacy request.
Technical server visibility
See the coordination and operational information involved at each stage of a transfer.
Contact
Exist.Dev LLC
2769 Avalon Street
Cantonment, Florida 32533, United States
+1 850-287-2235