Your devices.
Your connection.

At a glance

MeowDisplay connects your own devices for display streaming, audio, and input. It does not require a MeowDisplay account, and MeowDisplay does not operate a hosted media relay or cloud account service.

The apps contain no analytics, advertising, or tracking SDKs, and do not send telemetry. Screen, audio, and input data travel directly between your paired devices, not through servers run by MeowDisplay.

This page describes the current app and this website. Last reviewed: 25 September 2026.

Data on your devices

• Identity and pairing: your device’s private key, self-signed certificate, stable identity, and trusted peers’ public-key pins are held in the local Keychain. MeowDisplay does not enable iCloud synchronization for these Keychain items.
• Preferences: app settings and device preferences are stored locally.
• Connection hints: saved remote hosts and ports, device identifiers, and Wake-on-LAN information are retained locally to reconnect to known devices.

No name, email address, or MeowDisplay account is required to use the app. Device names and network identifiers can appear in discovery, saved device information, and diagnostics.

What travels between devices

During a session, captured display content, system audio when active, input events, and connection-control information travel between the Mac and receiver. Discovery advertises information needed to find nearby devices.

Sessions use mutually authenticated TLS 1.3. Pairing confirms a matching authentication code, then pins the other device’s public key. A network address is used for routing, not as proof of identity.

USB stays within the device pair. Local-network sessions use the local network. Remote Access uses the reachable network you configure.

Third-party networks & services

Remote networking is supplied by you. If you use Tailscale or another service, that service’s infrastructure, policies, and account requirements apply separately. Traffic may traverse that provider’s relay infrastructure while the MeowDisplay session remains encrypted.

MeowDisplay does not operate its own relay or see session media through infrastructure it controls. External links on this website take you to services such as GitHub, which have their own privacy policies.

Diagnostics & logs

The apps keep local diagnostic logs for connection and playback troubleshooting. Logs can include device names, peer identifiers, network addresses, timings, and technical errors.

Mac logs are size-capped and rotated under ~/Library/Logs/MeowDisplay. The iOS receiver keeps a capped connection log in its app storage, with a share/export action. Logs are not automatically submitted to a MeowDisplay analytics service.

If you choose to share a log or file a GitHub issue, review it first and remove private device names, endpoints, identifiers, and personal content. What you submit is handled by the service you use to share it.

Update checks: the current apps do not contact a server to check for updates. The Mac apps include the Sparkle updater, but no update feed is configured and automatic checks are off. The iOS version check is disabled.

Your controls

Use Allow Input to control remote interaction, and macOS permissions to control screen capture and Accessibility access. Disconnect to end a session.

Forget Device removes that peer’s trusted pin; connecting again requires pairing. Saved remote endpoints can be removed in connection settings. Forgetting a peer does not mean every preference or diagnostic log has been erased.

Uninstalling an app may leave Keychain entries behind. For help with stored identity or trust, contact the maintainer through the project’s support channels.

This website

This static website adds no analytics, advertising pixels, cookies, fingerprinting, external fonts, or third-party embedded scripts. It does not use browser storage.

The site is served through Cloudflare. Like any web host, it receives ordinary technical request information, such as your IP address and browser details, to deliver and protect the site. That is separate from the app’s local diagnostics.

Questions & security

For privacy questions, visit the project’s issues. For sensitive security reports, use GitHub’s private vulnerability reporting as described under Security reporting. Don’t put private information or exploit details in a public issue.

The security description documents the implementation. It is not a claim of a completed independent audit or regulatory certification.