JamarvusTechStreamingPrivacy Policy
Effective date: October 24, 2026
Short version: Google connection is optional. Every viewer authorizes their own account. JamarvusTech stores that viewer’s Google tokens encrypted on the server and associates them only with an opaque, secure browser cookie. It does not sell account data or use it for advertising.
Information stored on your device
Your queue, favorites, JTS viewing history, resume points, preferences, and connection URL are kept in this browser’s local storage. They are not automatically synchronized with other devices.
Optional Google and YouTube connection
If you choose “Sign in with Google,” Google provides an authorization code to our HTTPS callback. The server exchanges it for read-only credentials and stores the access token, refresh token, basic Google profile, granted scope, and connection time in encrypted persistent storage. Each browser session receives a separate random identifier in a Secure, HttpOnly, SameSite cookie. Inactive server sessions are retained for no more than 180 days.
The read-only YouTube permission is used to show your subscriptions, playlists, liked videos, channel information, and profile in JamarvusTech Streaming. YouTube’s public API does not provide normal account watch history. Google-synced content is played with an official YouTube playback surface.
Private playback and device activity
Search and playback requests require normal network information such as IP address, request time, route, and user agent. Television clients may send a generated device ID and friendly device name. Roku channels cannot read the television’s hardware MAC address. Operational logs and security records may be retained to prevent abuse and diagnose failures.
Other services
Official playback sends normal playback information to YouTube under Google’s policies. Optional SponsorBlock sends a video ID and requested segment categories to SponsorBlock. The support form sends the information you enter to the JamarvusTech server.
What we do not do
- No sale of Google user data
- No use of Google user data for personalized advertising
- No JamarvusTech advertising SDK or third-party analytics SDK
- No collection of contacts, photos, precise location, or microphone recordings by the web app
- No sharing of Google tokens with Roku, Android clients, or other viewers
Your controls
Use Google account → Disconnect to revoke the Google grant and delete the encrypted server session. Use Settings → Erase local data to remove browser-local history and preferences. See Data controls for complete instructions.
Security and changes
HTTPS, encrypted token storage, signed OAuth state, no-store account responses, protected administrator access, and isolated per-browser sessions are used to reduce risk. No internet service can promise absolute security. Material policy changes will be posted on this page.