Privacy Policy

1. Introduction

You can use PlayGuard's public video browsing, search, playback, and filtering features without signing in. Google sign-in is optional and is used only when you request account-related functionality.

2. Information We Access

Google account information

When you choose to sign in, PlayGuard may access:

• your Google account's unique user identifier;
• your display name;
• your email address; and
• your profile picture URL.

YouTube account information

PlayGuard requests read-only YouTube access. When you are signed in, PlayGuard may access the ID and title of your YouTube channel, a limited list of channels you subscribe to, and a limited list of videos you have marked as liked together with their public title, channel, publication date, and category identifier. These signals are used to personalize PlayGuard recommendations. PlayGuard does not request permission to upload, edit, or delete videos or to modify your YouTube account.

3. Google API Services

PlayGuard uses Google OAuth 2.0, OpenID Connect, the Google user information service, and the YouTube Data API. Authentication uses a device authorization flow so that approval can take place on a phone or computer rather than inside the TV application.

The application requests these scopes:

YouTube access is read-only. PlayGuard cannot use these permissions to upload, edit, or delete YouTube content.

4. How We Use Information

PlayGuard uses Google user data only to:

• authenticate you;
• display your signed-in profile in the application;
• identify and display your associated YouTube channel;
• use your YouTube subscriptions and liked-video topics as read-only interest signals for PlayGuard's personalized home recommendations;
• maintain your signed-in session; and
• provide account-related YouTube functionality that you request.

Information received from Google APIs is used only to provide the user-requested features described above. PlayGuard does not use Google user data for marketing, advertising profiles, or analytics.

5. Authentication Tokens

OAuth access and refresh tokens are handled on the server and are not exposed in frontend JavaScript or stored in browser local storage. The access token is used to request the authorized profile, YouTube channel, subscriptions, and liked-video signals. A refresh token may be used to maintain the authorized session and to request a new access token when needed.

6. Cookies and Sessions

PlayGuard uses a PHP session cookie for authentication and session security. On the required HTTPS connection, this cookie is configured as Secure, HttpOnly, and SameSite=Strict. It is used to associate the TV browser with the server-side authentication session and CSRF protection state. It is not used for advertising or analytics.

The embedded YouTube player is provided by Google and YouTube. When it is loaded, those services may receive normal network and device information and may use their own cookies in accordance with their policies.

7. Local Storage

PlayGuard stores the following information locally in the TV browser:

• the AI video filter preference;
• the ad-blocking preference;
• recent search history, including the search text, time, and repeat count;
• recent watch history, including video ID, title, channel information, watch time, repeat count, duration, video type, and available public category or keyword metadata;
• a limited cache of public candidate videos generated for recommendations;
• limited video impression counts and last-shown times used to reduce repetitive recommendations; and
• a limited cache of AI classification status for YouTube video IDs.

This browser-local information is used for application preferences, recent-history features, recommendation ranking, and avoiding unnecessary repeated requests or checks. OAuth tokens and raw Google account authorization data are not stored in local storage. Users can remove individual PlayGuard watch and search history entries or clear either local history list from the application. Other local data remains on the device until it is replaced by newer entries or the browser's site data is cleared.

8. YouTube Video Data

PlayGuard processes public YouTube video information to provide video lists, search results, related videos, thumbnails, titles, channel information, duration information, playback, and AI filtering. The server may temporarily cache public YouTube responses and video status results to improve reliability and avoid unnecessary repeated requests. This public video data is not used to build personal advertising profiles.

The PlayGuard home feed is personalized from recent browser-local search and watch activity. When you sign in, the limited read-only YouTube account signals described above may supplement that profile. Candidate videos are obtained through PlayGuard's public YouTube web adapter; the ordinary search feature is not replaced by YouTube Data API search. Related-video ranking is based primarily on the currently playing video's public metadata and web-related results.

9. AI Video Filtering

PlayGuard may examine public YouTube metadata and disclosure information to determine whether a video contains an official indication that it is AI-generated or AI-assisted. The resulting video status may be cached locally and temporarily on the server so the same public video does not need to be checked repeatedly. This feature does not analyze your Google profile for AI classification.

10. Data Sharing

We do not sell users' personal information.

PlayGuard communicates with Google and YouTube as necessary to complete OAuth authentication, retrieve the authorized profile and read-only channel, subscription, and liked-video signals, refresh or revoke authorization tokens, retrieve public video information, and provide embedded video playback. PlayGuard does not share Google user data with advertisers or use it for third-party advertising profiles.

PlayGuard's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

11. Data Retention

Authentication information is retained only as needed to maintain your session and provide the requested account functionality. YouTube subscription and liked-video signals are cached on the server for up to six hours to avoid unnecessary API requests; a short failure cache may be used when those services are unavailable. Signing out removes PlayGuard's server-side authentication state and its account-signal cache for that profile. Public YouTube response data and AI video status results are cached only for limited operational periods. Browser-local preferences and recommendation data remain until replaced by newer entries or cleared through the browser's site-data controls. PlayGuard watch and search history can also be removed from the application's History page.

12. Sign Out and Revoking Access

You can sign out from the PlayGuard account dialog. When you sign out, PlayGuard removes the local server-side account session and attempts to revoke the associated Google OAuth token. You can also revoke PlayGuard's access at any time from your Google Account permissions settings.

13. Security

PlayGuard requires HTTPS for account operations, handles OAuth tokens on the server, uses CSRF protection for account-changing requests, and configures secure session-cookie protections. No internet service can guarantee absolute security, but these measures are intended to reduce unauthorized access and disclosure risks.

14. Children's Privacy

PlayGuard does not ask users to provide an age and does not use Google account information to create advertising profiles. A parent or guardian who has a privacy concern about a child's use of PlayGuard may contact us using the address below.

15. Changes to This Privacy Policy

This Privacy Policy may be updated from time to time to reflect changes in PlayGuard's features, data practices, or applicable requirements. The current version and its latest update date will remain available on this page.

16. Contact

Questions or concerns about this Privacy Policy can be sent to:

Contact: menyhart403@gmail.com