What DeviceHop handles — and what it does not keep

01

Transferred files

File contents travel through an encrypted WebRTC connection between the participating browsers. A direct connection is preferred. If direct transfer is unavailable, encrypted packets may pass through DeviceHop's TURN relay. The relay does not intentionally save the file to disk.

The receiving browser temporarily assembles the file in memory. A lasting copy is created only when the receiver downloads or otherwise saves it on their device.

02

Temporary session data

DeviceHop keeps a random session token, expiry time and the two connected peer roles in server memory. This enables QR pairing and signaling. Active sessions are extended while the browsers remain connected and expire after inactivity. Restarting the service also clears in-memory sessions.

03

Network and operational metadata

Like most public websites, the web server can process technical information such as IP address, request time, requested URL, response status, transferred byte count and browser user-agent. Security and connection services also process IP addresses and timing information to establish or protect the connection.

File names and file contents are exchanged inside the browser transfer channel; they are not intentionally written into ordinary HTTP access logs.

04

Cookies, advertising and analytics

DeviceHop currently has no user accounts, advertising network, behavioral tracking pixel or visitor analytics service. The transfer interface does not require an analytics cookie to function.

05

Connection and infrastructure providers

Hosting, DNS, certificate and network providers necessarily process ordinary internet traffic. WebRTC connection discovery may contact a STUN service, which can observe the connecting IP address and time but cannot read the transferred file. DeviceHop's own TURN service may relay encrypted packets when a direct path fails.

06

Retention and security

File content is not retained by DeviceHop. Temporary session state expires automatically. Limited operational logs may be kept for a short period for reliability, abuse prevention and security, then removed through normal server log rotation.

07

Your choices

Do not share a pairing URL with anyone who should not join the session. Keep both browser tabs open only while transferring, close them when finished, and remove unwanted downloaded copies using the receiving device's normal file controls.

08

Changes to this notice

This page will be updated when DeviceHop's data practices materially change. The current revision date appears near the top of the page.