2xBRShow phone QR ↗
SIGNATURE / PHONE BRIDGE / SIGNPAD V1.0

Your phone is
the signature pad.

Show one QR on this computer. Sign naturally on the phone or tablet, undo strokes, choose the ink and return a transparent PNG or scalable SVG over the same verified Phone Bridge used by SCAN.

Show signature QR →
PHONE / PENVECTOR INK
TRANSPARENT PNGSVGWEBRTC RETURN
SIGNPAD / PHONE BRIDGE / WEBRTC
CHECKING SIGNALINGDIRECT MODE
01 / PHONE BRIDGE
Sign on the device in your hand.

Scan the QR with a phone or tablet. The handwriting pad opens there; the finished transparent PNG or SVG returns here over verified WebRTC.

NO APPLOCAL INK20 MIN ROUTE
FILE PAYLOAD NEVER ENTERS SIGNALING STORAGE / QR ONLY CARRIES A TEMPORARY ROUTE
SESSION / IDLEChoose a direction to begin.
For nearby transfer, show a receiver QR here. Or join a sender by code.

Connection metadata expires automatically. File bytes travel over the encrypted WebRTC channel.

TRANSPORT WEBRTC DATACHANNEL / DTLSCHUNKS 64 KIB / BACKPRESSUREINTEGRITY SHA-256SESSION 20 MIN / ONE USE
PHONE BRIDGE / IMPLEMENTED
01

No app install.

The computer creates a short-lived receiver QR. The phone opens the handwriting surface directly in its browser.

02

Finger or pen.

Pointer input captures real pen pressure when the device exposes it and uses a stable touch fallback when it does not.

03

Fix mistakes immediately.

Undo removes the last complete stroke. Clear starts clean. Nothing is committed to the computer until you explicitly send it.

04

Useful outputs.

Transparent PNG drops cleanly into common documents and slides; SVG keeps a scalable vector representation of the handwriting.

05

No signature archive.

Stroke data stays in the phone browser. Signaling coordinates the devices; the resulting asset returns through WebRTC.

06

Verified arrival.

The computer independently verifies SHA-256 before showing the returned signature preview and download.

PRODUCT BOUNDARY

Handwritten capture.
Not legal e-signing infrastructure.

SIGNPAD captures the mark you draw. It does not claim identity verification, certificate-based signing, qualified signatures, audit trails or jurisdiction-specific electronic-signature compliance.