YAKITASHA WATCH PARTY

Privacy Policy

Effective date: September 27, 2026
Operator and privacy contact: Yakitasha — pjpkaj@hotmail.com

Information processed and why

The Activity uses Discord authorization to obtain an access token and check the user's membership in the configured Discord server and eligibility through the WatchPartyViewer or ProSelector role. The membership response includes account and role information. The application retains the Discord user ID, display name, and whether the user may control playback to authenticate access and enforce ProSelector permissions. It does not request Discord messages, contact lists, microphone input, or camera input.

The server processes media searches, selected titles or live channels, playback positions, subtitle choices, queue changes, and playback requests to provide shared viewing. Other authorized participants can see shared titles, channel selections, queues, and playback changes. Viewing and control requests are sent to the operator's server; media and guide requests are sent to the configured Plex server and HDHomeRun tuner.

The server and network infrastructure necessarily process request and connection information to deliver the service. Diagnostic error records can include request categories, error types, status codes, and timestamps. Plex and the surrounding server infrastructure may retain additional operational records, such as connection information and media-access history. Their retention follows the relevant service configuration and is not covered by the Activity’s eight-hour in-memory session limit. Contact the operator for information about those records or a deletion request.

Storage and retention

The Activity's own Discord sessions are held in server memory for up to eight hours, or the shorter Discord access-token lifetime. Expired sessions are removed by a periodic cleanup task, and server restarts clear them. Leaving playback does not immediately delete an authentication session. The Activity does not maintain a separate persistent user-profile or per-user watch-history database.

Shared playback and queue state are held in memory and reset on server restart. Live television segments are held in a temporary rolling buffer, approximately two minutes of playable history plus processing overhead. They are removed as the window advances, when a live stream is stopped, or when its temporary filesystem is reset. The operator's underlying media library, Plex records, and operational logs are separate from this temporary buffer.

The operator's Plex token and Discord application secret are stored on the server to operate the service. They are not provided to viewers. Users' temporary session credentials are held in the running Activity; this application does not intentionally add advertising cookies or analytics trackers.

Recipients and third-party services

Information is processed by the operator's hosting infrastructure and by Discord as needed for authorization and Activity operation. Discord's own privacy policy applies to its platform, embedded browser, and proxy services. The operator's Plex installation and HDHomeRun supply media, channel listings, and guide information and may keep their own operational records. The Activity does not implement data sales or advertising profiles.

Choices and requests

You can leave playback, close the Activity, and revoke its authorization through Discord's Authorized Apps settings. Server membership and ProSelector access are managed by the operator. Contact pjpkaj@hotmail.com for access, correction, deletion, or other privacy requests, identifying your Discord account without sending passwords or tokens. Requests involving Discord's own records should also be directed to Discord. Applicable privacy rights depend on your location and circumstances.

The operator should announce material policy changes and update the effective date. Contact the operator with questions or concerns.