Security

For:All users

No technical knowledge required.

WolfP2P streams files over an encrypted browser-to-browser connection. Its server helps the browsers connect but does not receive, store, or forward your files or their names.

That design reduces intermediary file handling, but it does not remove every trust decision. The sender must share the invitation with the intended person, both endpoints must be trustworthy, and the transfer must fit WolfP2P's live direct-connection model.

For a practical workflow that applies these boundaries, see Share a Sensitive File Privately.

Security controls and boundaries

Encrypted in transit

The browsers encrypt the connection so others on the network cannot read the files or change them without detection.

No intermediary file copy

Your files and their names travel directly browser-to-browser. WolfP2P’s server does not store or forward them.

You choose what the browser can access

WolfP2P can read or write only after a person deliberately selects a source or destination and the browser grants the required access. Selecting one location does not grant general disk access.

Transfer verification

The encrypted channel protects traffic in transit. WolfP2P also uses local verification when deciding whether destination content can be reused during supported recovery. Neither mechanism proves who created a file or whether it is safe to open.

Understand each boundary

Security details

Encrypted transfer

See how encryption protects your files during delivery and what it cannot protect.

What the server sees

See what connection information WolfP2P uses and what optional usage information you can choose to share.

Browser file and folder access

See what source and destination selections authorize, what remains inaccessible, and why the browser may ask again.

No intermediary copy

Consider how avoiding another stored file copy changes exposure without making either endpoint inherently trustworthy.

Trust, identity, and file integrity

Encryption does not prove who is using the other browser. Someone with your invitation may try to join before the intended recipient. Share it privately and confirm the recipient by phone or another trusted channel before sending sensitive files. Replace an invitation if someone else may have seen it.

Encryption protects files while they travel. During supported recovery, WolfP2P also checks existing file contents before reusing them. Neither check proves who created a file or whether it is safe to open. Keep your computer protected and only open files from someone you trust. Read how recovery checks work.

You still rely on WolfP2P to connect the browsers correctly. It does not independently prove the identity of the person at the other computer. Read the technical trust limits and the Privacy Notice for details about information the service uses.

Does this security model fit?

Choose for the required controls

WolfP2P fits when

Two known participants can remain online for a supervised transfer.
Avoiding an intermediary server copy is important.
A privately shared invitation and separate recipient confirmation provide enough identity assurance.
Both endpoints and browsers are trusted and updated.

Use a managed system when

Authenticated organizational identities, audit records, malware inspection, retention rules, data-loss-prevention controls, or administrator-enforced policy are required.
The receiver must retrieve the files after the sender goes offline.
The network blocks a direct connection. WolfP2P cannot send the files through its server instead.
The files require a durable repository, backup, public distribution, or access by several recipients.

Report a security vulnerability

If you discover a potential weakness, read the Vulnerability Disclosure Policy before testing or reporting it. It defines the authorized scope, reporting instructions, prohibited testing, response targets, and coordinated-disclosure process.

For service incidents and resolved security events, review the current and previous Security Notices.