couch tap
Privacy policy

Your remote stays local.

This policy covers the Couch Tap native iPhone app and this support website.

Effective November 18, 2026 · Developer: Eric Sebring · eric@sebringai.com

The current native app has no Couch Tap account, advertising SDK, developer-operated analytics, or developer cloud service that receives your TV commands.

Local TV discovery and control

Couch Tap uses your local network to discover compatible TVs and send remote commands. Commands, keyboard text, and app links you choose are sent to the selected TV. The TV, its manufacturer, and apps running on it may process that information under their own policies. Couch Tap does not upload these commands or text to its developer.

Data stored on your iPhone

Pairing keys, client certificates, trusted TV fingerprints, platform approval tokens, and optional Home Assistant credentials are stored in iPhone Keychain. TV names and addresses, saved rooms, app shortcuts, selected bridge settings, and appearance preferences are stored locally using iOS storage. These are not sent to a Couch Tap cloud service.

Local storage and backups are subject to your iPhone and Apple settings. Removing the app may remove its preferences, but Keychain records can persist across reinstallations. Contact support if you need help resetting local pairing; the developer has no remote copy of those credentials.

Connection security

Google TV uses TLS pairing and remote connections. Samsung and LG use secure WebSockets with TV approval and certificate identity checks. Sony BRAVIA IP mode sends its pre-shared key and commands over unencrypted local HTTP, as disclosed before connecting. Use that mode only on a trusted private network.

Optional Home Assistant connections

Bridge mode sends commands to your own selected local Home Assistant server and configured remote entity. Your server and integrations may keep activity logs according to their configuration. The access token stays in iPhone Keychain after verification and is sent only to the selected server. HTTPS uses iPhone system trust. Local HTTP requires explicit consent and sends the token without encryption. The developer does not operate or receive this traffic.

Purchases

Apple processes the optional Plus purchase. Couch Tap uses StoreKit to retrieve product information and verify access to Plus. The developer does not receive your full payment-card details. Apple processes purchase and platform information under its own policies. Apple may provide the developer with App Store business reports. TestFlight testing and diagnostic information are handled through Apple's services and your Apple settings.

Support messages

If you email support, the developer receives the information you choose to send, including your email address, message, and attachments. It is used to respond to your request and resolve the reported issue, not for advertising or sale to data brokers. Messages are retained only as needed to provide support and meet applicable legal obligations. You may request deletion by emailing eric@sebringai.com, subject to those obligations. Do not send passwords, private keys, access tokens, or sensitive TV login text.

This website

This website has no developer-added advertising, analytics scripts, contact forms, or tracking cookies. Its hosting provider may process standard request information, such as IP address and browser details, to deliver and secure the site. Email links open your email application; a message is sent only when you choose to send it.

Permissions and your choices

You can manage Local Network permission in iPhone Settings → Privacy & Security → Local Network. Disabling it prevents local TV discovery and control. The app does not request microphone, camera, photo-library, contacts, or location access. You control the TV, bridge, and services you connect to.

Children

Couch Tap does not offer developer accounts, chat, social feeds, or targeted advertising. The developer does not knowingly collect children's personal information through the native app. A parent or guardian can contact support with privacy questions.

Separate Windows browser remote

The Windows-assisted browser version is a separate local deployment. Its pairing credentials are stored on the Windows PC, and a private URL token authorizes the browser. The PC must remain running. Do not share that private URL token.

Changes and contact

This policy will be updated when the app's data practices change. The effective date appears above. Send support or privacy requests to eric@sebringai.com.

Return to support