Privacy

Last updated: April 2026

What PadlinQ does not collect

PadlinQ does not collect personal information, does not require an account, and does not assign any identifier to you or your device. By default, no data is sent anywhere beyond the direct WebRTC connection between your phone and your PC.

How the relay works

When you scan a QR code, your phone connects to the PadlinQ relay server only to discover your PC (a standard WebRTC signalling exchange). Once the peer-to-peer connection is established, the relay is no longer involved. Controller input flows directly between the phone and the PC over an encrypted WebRTC data channel — it never passes through our servers.

The relay sees your IP address for the duration of the handshake (as any WebSocket server does) and discards it immediately after. No IP addresses are logged or stored.

Optional analytics

The phone-side controller page includes an opt-in analytics toggle, off by default. When enabled, PadlinQ may send anonymous event counters — things like "a session started" or "which layout was used" — to a self-hosted endpoint. These events contain:

• Event name (e.g. session.created)
• App version string
• Coarse OS family (e.g. ios, android)
• ISO week number (no precise timestamp)

They contain no device IDs, no IP addresses, no text you've typed, and no controller input. The toggle is in the controller settings panel and can be turned off at any time.

Third parties

PadlinQ does not use any third-party analytics service, advertising network, or tracking pixel. There are no cookies.

Controller input

Touchscreen input (buttons, sticks, triggers) is processed entirely on your phone and forwarded to the PadlinQ helper running on your PC. It is never stored, logged, or sent to any server.

Contact

Questions or concerns? Email [email protected].