Privacy policy

Updated October 9, 2026.

Better Media Share is operated by izidore. Privacy and support contact: contactizidore@gmail.com.

What the service uses

We use your Twitch account ID, display name, channel identity, profile image and permissions to sign you in, identify requesters and limit channel controls to authorized people. The dashboard requests read-only access to your extension configuration to check whether Better Media Share is active. Optional subscriber features use subscription status when separately authorized and enabled.

Requests include the video link and provider metadata, selected timestamps, speed, Bits amount, transaction identifiers and queue or moderation outcome. We store channel settings, moderator permissions, block/trust rules and security audit records. OAuth tokens are encrypted in server storage. Twitch handles Bits confirmation.

Who can see requests

Broadcasters and authorized moderators can review requests and request history. Approved requests, requester names and recent public playback history can appear in the extension and broadcast. Requests awaiting approval are visible to the submitting viewer and channel staff. If a broadcaster enables chat notices, the service sends the requester’s name to Twitch chat without the unreviewed video title.

Providers and hosting

This service uses YouTube API Services and official YouTube and Twitch embeds. Every YouTube video plays in YouTube’s privacy-enhanced mode (youtube-nocookie.com). Video links and search queries are sent to the relevant provider; embeds connect directly from the browser to the provider. Providers may receive device and network information, use cookies and serve their own advertising. See the Google Privacy Policy, YouTube Terms of Service and Twitch Privacy Notice. No Google account sign-in is requested by this application.

Railway hosts the service. Network addresses and request information are processed for delivery, rate limiting and security, and may be recorded in hosting logs. Hosting log retention is managed separately by the hosting provider. We do not add advertising or analytics trackers to the application.

Cookies and browser storage

Essential cookies maintain dashboard sign-in and protect the Twitch sign-in flow. Local storage remembers the selected channel and interface choices until you clear it. Session storage can hold a private OBS player token for that browser session. Signing out ends the dashboard session.

Retention and deletion

Scheduled database cleanup runs when the service starts and hourly while it is running. The following limits apply to application records:

• Dashboard sessions expire after 12 hours unless renewed. Recovery-admin sessions expire after two hours. Sign-in challenges expire after ten minutes. Expired records are removed at cleanup; signing out deletes the dashboard session immediately.
• Webhook event identifiers used to detect repeated notifications are removed at cleanup once they are more than seven days old.
• A reserved selection and its Bits amount are valid for ten minutes. Unused or cancelled reservations are removed at cleanup once their expiry is more than 24 hours past. Reservations used for a confirmed request have no automatic deletion period.
• YouTube search queries and results are cached for 24 hours. Expired cache entries are removed when accessed or at cleanup.
• YouTube video details and eligibility rejections are cached for 24 hours, shared across all channels. Request submissions reuse details fetched within the last ten minutes; older details are checked again. Expired cache entries are removed when accessed or at cleanup.
• At cleanup, request history is reduced to the latest 1,000 records per channel. Live queue views contain up to 20 recent history records. These count limits do not impose a maximum age or remove copies held with transactions or confirmed reservations.
• At cleanup, stored YouTube metadata that is at least 30 days old is stripped from requests, queue entries, history, reservations and transaction records. This removes titles, thumbnails, statistics and other fetched video details, along with associated stored rejection reasons. The YouTube video identifier and URL remain, together with request and transaction information. Expired details are not used to approve or replay a video; the link must be checked again.
• Transaction records are kept to prevent duplicate fulfillment and have no automatic deletion period. Removing a request from the queue does not erase its transaction record. There is also no scheduled automatic deletion for stored channel account details, encrypted authorization tokens, settings, moderator permissions, block/trust rules or security audit records.

Contact the address above to request access, correction or deletion and identify the relevant Twitch account or channel. We may need to verify account ownership. Revoking access in Twitch Connections stops future authorized access but does not itself erase stored records. Google permissions, if separately granted to other services, can be managed in Google account permissions.

Changes and contact

Updates will be dated on this page. Contact contactizidore@gmail.com with privacy questions.