Privacy Policy

Last updated: October 2026

Summary

Peerino does not collect or store personal data. Connection metadata is processed by the third-party services listed below.

What Peerino Does Not Do

• No collection of personal information: no names, no email addresses, no logs of IP addresses
• No usage analytics or telemetry
• No cookies for profiling or advertising
• No storage of file content on any server. File content travels directly between peers.

Peerino keeps nothing. The services listed under "Third-Party Services" see connection metadata. These are two separate facts, and neither one cancels the other.

Data Stored Locally on Your Device

• Peer ID: a stable identifier generated once and stored in config/peer_id.json. It is kept across restarts so that links you generate continue to work.
• Shared files: stored in your local shared-folder/
• Configuration: stored in config/. A .env file is used only during development or for manual overrides; it is not required for the released app.

All this data stays on your device. You can delete it at any time by removing the Peerino folder.

Local Network Transfers

When both peers are on the same local network, the desktop application can serve files over plain HTTP on the local network. This path is not encrypted and never leaves the local network.

It is not advertised automatically: the generated link does not point the recipient at the local server, so this path is reachable only by opening the local server address manually. See the README for the current state of this feature.

Third-Party Services

Peerino uses the following external services only for connection setup (never for file content):

• Signaling: 0.peerjs.com sees temporary connection metadata (Peer IDs and public IP addresses for ICE negotiation), not file content.
• STUN servers: public servers. The desktop app uses Google STUN; the receiver page uses a fallback list.
• TURN service (Cloudflare): TURN credentials are used only to diagnose whether a direct peer-to-peer connection is possible. No file, fragment, or file content is transmitted through TURN. If a direct connection is not possible, Peerino informs the user and suggests trying from a different network.
• TURN credential proxy: a Cloudflare Worker run by the project issues short-lived TURN credentials to the receiver's browser. It sees the requesting IP (used only for rate limiting, with a short in-memory retention) and the peer ID from the link (not retained). The credentials themselves are generated by Cloudflare's TURN service.

Your Rights (GDPR)

Peerino does not store personal data. There is therefore nothing to request, export, or delete from Peerino: we hold no copy of your personal data, no file content, and no connection logs. You have full control over the data stored on your device, and you can delete it at any time by removing the Peerino folder.

Connection metadata, however, is processed by the third-party services described above. PeerJS and Cloudflare act as the controllers of that data for their respective parts of the connection. If you wish to exercise your rights over it, you must direct your request to those services. Peerino is not able to access, export, or delete it, because it does not hold it.

Changes to This Policy

We may update this policy. The "Last updated" date will reflect the change.

Contact

For any question: [email protected]

← Back to Peerino