Privacy · Private testing

RelayDeck privacy

Effective July 30, 2026

What RelayDeck handles

RelayDeck stores approved device identity, uploaded presentation content, prepared display assets, presentation state, and sanitized operational events needed to run the private test.

Content retention

Content expires 24 hours after last use by default. The owner may select a shorter period or extend retention up to seven days. Content can be deleted immediately from the approved controller or owner administration surface.

Device identity

The Android controller creates a hardware-backed key when supported. The server stores the public key, not the private key. A device must be approved before it can receive an access token and can be revoked at any time.

Presentation sessions

Receiver join codes can be used once and expire after two minutes. Presentation sessions expire after eight hours. Receiver credentials are held in memory for the session and are never placed in asset URLs or browser storage.

Public webpages

RelayDeck only accepts compatible public HTTPS webpages. It does not proxy pages, retain browsing credentials, or support authenticated browsing. A page may refuse display through its own security policy.

Sharing

RelayDeck does not sell personal data and does not expose a public signup or advertising tracker. Infrastructure providers may process limited technical data required to deliver the service securely.

Private-test contact

Privacy questions for the current private test can be directed to [email protected].