Why WolfP2P asks for file and folder access

WolfP2P runs in a browser, so the browser acts as a safety boundary between the website and your files. WolfP2P cannot silently browse your computer. You must choose the file or folder, and the browser may show a warning or permission prompt before allowing access.

The exact wording and appearance of these messages vary by browser and operating system. A request to view files or save changes is expected when you deliberately select a source or destination in WolfP2P.

When sending, you choose a file or folder. WolfP2P receives read access to that selection so the browser tab can list the files and read their bytes for transfer.

This does not give WolfP2P unrestricted access to other files or folders. If you do not recognize the selection shown by the browser, cancel the picker and start again.

In a Compatible Browser, the receiver chooses a destination folder. WolfP2P needs read and write access within that folder to:

• create the received files and nested folders;
• locate destination comparison candidates by relative path and size and verify reusable content with SHA-256 evidence;
• skip verified matching files during the current transfer; and
• preserve recoverable progress when supported.

This is why the browser may warn that the site can view files or save changes in the selected folder. Choose a dedicated destination when you do not want WolfP2P working inside a broader folder.

Selecting one file or folder does not expose the rest of the computer. The browser grants a handle to the selection—not general disk access—and continues to enforce that boundary.

The permission belongs to the local browser and is used by the WolfP2P browser client. It does not give the coordination server access to the selection, and the server does not receive its file bytes or file metadata during transfer.

To support recovery, a compatible browser can keep a reference to the selected source or destination in its local site storage. The browser may ask you to approve that access again after a reload, restart, restored session, changed site setting, or earlier refusal. WolfP2P cannot approve or bypass a browser permission on your behalf.

You can review or revoke WolfP2P permissions through the browser's site settings. Revoking access prevents WolfP2P from continuing to use that saved file or folder reference and can stop a transfer from resuming until access is granted again.

Safari and Firefox currently provide WolfP2P with more limited file handling. The sender can still select individual files, but the receiver cannot grant WolfP2P direct access to a chosen destination folder. The current receiver has no individual-download fallback. Use a browser whose live capability check confirms writable destination-folder access to receive files.

See Browser and OS Compatibility for the current capability differences.

If Documents is refused with a system-files message, create a subfolder inside it and select that instead. If a prompt was denied, dismissed, or blocked—or a location is still refused—follow Browser Folder Permissions and the relevant file, folder, permission, and disk error instead of weakening browser or operating-system protections.