WolfP2PCookies and similar technologies
For:Legal and privacy readers
No technical knowledge required.Version 1.0.2 — Effective September 15, 2026 at 04:00:23 UTC
Authored September 14, 2026. Version 1.0.2 became effective September 15, 2026 at 04:00:23 UTC, replacing version 1.0.1.
WolfP2P is operated by Exist.Dev LLC. For questions about browser storage and optional technologies, use Contact Us.
This page retains its own version. A material change to browser storage, purpose, provider, duration, or control receives a new version and archived prior copy without automatically changing every other privacy document.
WolfP2P currently sets no cookies. It uses first-party browser storage for functional preferences, legal continuity, essential transfer continuity, and—only after acceptance—optional product analytics. Personalization and marketing-measurement purposes are not active launch choices. No external analytics or advertising SDK is active today.
Current storage position
Current browser-storage inventory
WolfP2P stores different kinds of information for different lengths of time. localStorage can remain after the tab closes, sessionStorage belongs to the current tab session, and IndexedDB holds structured browser-local records used for transfer continuity. These records remain in the browser unless a description below expressly says otherwise. A browser may restore a tab session; closing a tab is not a guaranteed erasure method. Browser-private file storage holds staged received bytes separately from IndexedDB.
localStorage
Analytics consent
- Key
- wolfp2p.analytics.consent
- Purpose
- Remembers the consent decision and applicable policy version
- Created
- After the first consent decision
- Removed
- On withdrawal or when browser storage is cleared
Analytics browser identifier
- Key
- wolfp2p.analytics.uid
- Purpose
- Identifies a pseudonymous browser profile for optional product analytics
- Created
- Only after product analytics is first accepted
- Removed
- On withdrawal, reset, confirmed profile erasure, or when browser storage is cleared. A refused or unreachable erasure request stops analytics but retains this identifier for retry
Appearance preference
- Key
- wolfp2p.theme
- Purpose
- Remembers the selected clear-sky or night-signal appearance instead of the system default
- Created
- After the user explicitly changes the appearance
- Removed
- When browser storage is cleared; a later appearance choice replaces the stored value
Terms acceptance reference
- Key
- wolfp2p.acceptance
- Purpose
- Remembers the most recent Terms acceptance reference so the browser can quote it during the 30-day arbitration opt-out period
- Created
- After creating or joining a tunnel when the effective Terms are presented and accepted
- Removed
- When browser storage is cleared or a later acceptance replaces it
Large-file handling preference
- Key
- wolfp2p.transfer-mode.v1
- Purpose
- Remembers the Safe or Quick transfer preference for future transfers
- Created
- After the user changes the setting
- Removed
- Through browser settings or when browser storage is cleared
sessionStorage
Analytics visit identifier
- Key
- wolfp2p.analytics.sid
- Purpose
- Identifies the current analytics visit after optional product analytics is accepted
- Created
- After product analytics is accepted for the current tab session
- Removed
- On withdrawal, reset, erasure, browser-storage clearing, or when the tab session ends
Analytics session activity
- Key
- wolfp2p.analytics.sid.seen
- Purpose
- Stores the last activity time used to start a new analytics visit after 30 minutes of inactivity, not a fixed 30-minute lifetime for an active visit
- Created
- With the analytics visit identifier after product analytics is accepted
- Removed
- On withdrawal, reset, erasure, browser-storage clearing, or when the tab session ends
Transfer tab identifier
- Key
- wolfp2p.tab-id.v1
- Purpose
- Identifies this tab for transfer continuity; not an analytics identifier
- Created
- When the tab needs a transfer identity
- Removed
- When its browser-managed tab session is cleared
Ended tunnel marker
- Key
- wolfp2p.ended-session
- Purpose
- Remembers an ended tunnel code so stale recovery state is not resumed
- Created
- When an ended session is recorded
- Removed
- When replaced or cleared by session handling or the browser-managed tab session is cleared
Consent prompt engagement
- Key
- wolfp2p.consent.engagement
- Purpose
- Holds a local interaction counter used to decide when to offer privacy choices; it is not a record of every navigation sent to analytics
- Created
- As relevant interactions update the prompt counter
- Removed
- When the browser-managed tab session is cleared
IndexedDB
Transfer continuity, reports, remembered handles and activity
- Database
- wolfp2p-browser-state
- Stores
- sessions, transfer-reports, remembered-handles, activity-log
- Location
- Browser-local storage, separate from optional analytics
Session recovery records
The sessions store holds recovery information for a tab, not file bytes. Records remain until the session ends or is discarded. Discarding a saved session or dismissing a terminal outcome removes the corresponding record; a record for an ended tunnel is invalidated when read.
Transfer reports
The transfer-reports store holds local transfer reports, including filenames, sizes and per-file outcomes as seen by this participant, but not file bytes or content hashes. Reports are retained for up to 365 days, with at most 250 reports. Use Delete on the Reports page to remove a report; automatic trimming also removes reports.
Remembered file-system handles
The remembered-handles store holds up to 50 file-system handles granted by the participant, not the files. WolfP2P checks permission before reusing a handle. Use Forget in My Settings to remove a remembered handle.
Browser activity log
The activity-log store records activity for this browser, including activity across tabs and outside a transfer. Entries identify the event kind, code, actor, tab and time, not what was typed, chosen or named. The log is not a session-only history or the optional analytics event stream.
The retention target is 5,000 entries. Trimming is batched, with a 250-entry allowance before it is triggered after the count exceeds 5,250; the target is not an instantaneous maximum. Entries older than 30 days are removed when the log is updated, not at an exact scheduled time. Use Clear in the activity drawer to remove the log. These limits apply to activity entries, not staged received files or other browser storage.
Browser-private received-file staging
Received bytes and their lifetime
Browser-download receiving writes file bytes to the origin-private file system (OPFS), in directories named with wolfp2p-download- and a random suffix. These are actual received bytes, not just handles or recovery metadata. They are created during receiving and may remain after the transfer or tab ends. Verified completion there is separate from saving a download.
The application currently has no automatic cleanup, fixed retention period or in-app deletion control for staged files. Browser eviction or clearing WolfP2P site data can remove them. This storage is not a backup or a promise of later recovery. Save and verify the files you need before clearing site data. Browser storage controls do not remove downloads already saved elsewhere or another participant's copies.
No analytics identifier is created and withheld before consent: it does not exist until product analytics is granted. The transfer session and IndexedDB records are essential, not analytics. Filenames required for local reload recovery remain in the browser and are not transmitted as analytics.
Declining product analytics prevents creation of a persistent analytics profile and optional cross-visit history.
The browser's current consent choices remain until withdrawal, reset, erasure, or a superseding policy requires a new decision. A refused or unreachable erasure request stops analytics collection but keeps the browser-profile identifier for retry; keeping that identifier does not authorize collection.
Server-side consent evidence
Separate minimal server-side consent evidence is retained for no more than five years after the last relevant decision or withdrawal. It is not a cookie or browser-storage record. That audit record is separate from browsing history and from the profile record. Deleting a profile does not necessarily delete this retained evidence; retained evidence follows its separate retention period.
Your controls
Use Privacy Preferences to accept, decline, or withdraw optional product analytics.
Before clearing WolfP2P site data
Global Privacy Control is detected, but WolfP2P currently has no sale, sharing, or targeted-advertising purpose for it to disable. Product analytics remains a separate optional choice.
No optional technology may run before the applicable choice permits it. Refusal must not reduce ordinary transfer functionality.
Version history
Version 1.0 was effective August 19, 2026. Version 1.0.1 is effective September 14, 2026 and corrects the IndexedDB database and store names, separates the four stores and their controls, and describes the confirmed browser-scoped activity retention behavior. This is an inventory correction, not authorization for new analytics or a change to connection discovery.
Version 1.0.2 was authored September 14, 2026 and became effective September 15, 2026 at 04:00:23 UTC with the correction release. It corrects storage keys, describes received-file staging and clarifies clearing and profile-control limits. No new storage purpose or optional analytics is authorized.