Privacy notice

Last updated: 16 September 2026

What EasyView does now

EasyView is an Android phone, tablet, and TV application for selecting familiar videos from a caregiver-managed picture library. A caregiver can add official content links and optional tile details such as a title, image, icon, and colour.

Data stored and sent by EasyView

EasyView stores the video-library details on the device. This can include the video identifier or official content link, title, thumbnail URL or selected image, icon, colour, and playback preferences. The library is stored in the browser or app's local storage (IndexedDB, with legacy local storage support).

When a caregiver sends a selected YouTube video to a paired EasyView TV, EasyView relays the selected video metadata and command between those paired devices. This includes the video identifier, title, provider, allowed thumbnail URL, and tile style information needed by the receiver. The relay temporarily keeps commands and playback state in memory; its sessions end when the relay restarts. EasyView also stores local settings such as playback preferences, the selected app role, and TV-pairing state.

YouTube and Google data

Individual YouTube links work through YouTube's official player without Google account access. When the player loads or plays a video, or when an image or thumbnail is loaded from a provider, the relevant provider may receive standard web or app request data. If these pages are hosted, the hosting service may also process standard request data. Google and YouTube process their data under their own Privacy Policy and Terms of Service.

Private YouTube playlist import is available only in a designated verification test build and is not enabled in the public release. It requests the https://www.googleapis.com/auth/youtube.readonly permission to read the signed-in user's playlists and playlist items so the caregiver can add selected videos to the local EasyView library. It does not create, change, or delete YouTube content. Standard Google sign-in permissions (OpenID, email, and profile) also provide account identity to Firebase Authentication, including the account identifier, email address, display name and profile picture where available.

For that feature, EasyView's own code keeps the returned Google access token in browser or app session storage and clears it when the user signs out. Firebase Authentication processes account identity and may also manage its own sign-in state according to its configured platform behaviour. EasyView does not put the Google access token or account profile in its video-library database. Selected playlist and video metadata is retained locally until you remove it; signing out does not remove tiles already imported.

How sensitive data is protected

EasyView uses the following safeguards for Google account and YouTube data:

• Encryption in transit: Google sign-in, YouTube Data API requests, the hosted EasyView pages, and remote TV relay traffic use HTTPS/TLS. The Google access token is sent only to Google's authenticated API endpoints in an HTTP authorization header; EasyView does not send that token to its TV relay.
• Limited access: EasyView requests the read-only youtube.readonly scope and uses it only after the caregiver deliberately chooses Connect. The token and private playlist results are available only inside the caregiver-controlled import screen. They are not exposed to the simplified viewer screen.
• Limited storage: EasyView keeps the Google access token in session storage and in application memory, not in the video-library database or relay. Session storage is isolated to the EasyView origin and is cleared when the user signs out or the browser session ends. EasyView does not retain copies of private playlists on its server.
• Local control and deletion: Only videos deliberately selected by the caregiver are copied into the local EasyView library. The caregiver can remove those local tiles, sign out to clear the current token, and revoke EasyView access from the Google Account permissions page.
• Relay protection: Controller-to-TV commands use a short-lived, one-use pairing code followed by random bearer credentials. Relay sessions, commands, and playback state are held temporarily in server memory and expire; Google access tokens and private playlist contents are never included.
• No sale or advertising use: EasyView does not sell Google user data, use it for advertising, or allow humans to read it except when necessary for security, legal compliance, or support requested by the user.

Sharing

EasyView does not sell the local library data. It sends selected-video metadata and commands to a paired EasyView TV through its relay when the caregiver chooses remote playback. It sends requests to Google and YouTube when using YouTube playback or, if a future approved build enables it, when a user chooses private playlist import. Netflix, Stan, and Disney+ links open those providers' own apps; EasyView does not collect their passwords.

Choices and deletion

See Support and deletion to remove the local library, sign out, or revoke an existing or future Google connection.

Contact

Email sigmaequilibrium@gmail.com with privacy questions.