Privacy Policy - React Player

Plain version: React Player has no user accounts, advertising system, or analytics tracker. Most request data stays inside the streamer's own Streamer.bot installation. Hosting and embedded media providers still process ordinary internet connection data when their services are used.

1. Who is responsible

KVALVIK STUDIOS Sole proprietorship (ENK) Organisation no. 936 409 113 · MVA-registered 8013 Bodø, Norway Official registered business details [email protected]

Kvalvik Studios is the data controller for the limited personal data described in this policy.

2. What React Player does not do

No React Player account or Google/YouTube sign-in is required.
No first-party advertising, profiling, or analytics service is used.
React Player does not sell personal data.
React Player does not centrally store a streamer's request queue or history.

3. Data stored on the streamer's own computer

The Streamer.bot package stores the queue, history, current request, playback settings, and related state inside the streamer's own Streamer.bot installation. Depending on which triggers the streamer enables, this local data can include a requester's display name or user ID, the submitted media URL, platform/origin information, and timestamps.

This local queue data is not sent to or stored by Kvalvik Studios. The streamer controls that local data and is responsible for how they use and retain viewer information in their own setup.

4. Functional browser storage

React Player uses limited first-party browser storage to make the tool work and remember choices:

reactPlayerLanguage remembers the selected dock language.
reactPlayerActionId.* remembers resolved Streamer.bot action IDs so renamed actions keep working.
reactPlayerLegalAccepted remembers that the Privacy Policy and Terms were accepted before downloading the package.
Embedded providers can store their own playback preferences in their own browser storage.

You can remove first-party React Player storage by clearing site data for react.melkepakken.tv. Doing so resets saved website/dock choices.

5. YouTube API Services

React Player uses YouTube API Services. When a supported YouTube link is submitted, React Player sends the public YouTube video ID to a Cloudflare-hosted endpoint. That endpoint asks the YouTube Data API for the video's public duration and Made for Kids status.

No YouTube account login or OAuth access is used.
No private YouTube account data is requested.
Successful duration and Made for Kids responses may be cached for up to 24 hours, keyed by video ID.
Ordinary YouTube videos use the normal YouTube embedded player. Videos identified as Made for Kids use YouTube's privacy-enhanced embed domain.

Use of YouTube features is also subject to the YouTube Terms of Service. You can read how Google handles information in the Google Privacy Policy.

6. Embedded media providers

When a streamer plays media from a supported provider, React Player loads that provider's embedded player. The provider may receive technical information needed to deliver the media, such as the IP address, browser/device information, requested content ID, referrer information, and interactions with the embedded player. The provider may also use cookies or similar browser storage under its own policies.

The dock and player also load the Streamer.bot browser client through jsDelivr. jsDelivr and its CDN providers receive ordinary request metadata needed to deliver that file. See the jsDelivr Privacy Policy.

7. Hosting and security logs

React Player is hosted and protected through Cloudflare. Cloudflare processes ordinary network and request data needed to deliver and secure the service. This can include IP addresses, request URLs, traffic routing data, browser/device information, and security events.

The legal basis for this processing is Kvalvik Studios' legitimate interest in providing, securing, and maintaining React Player. See the Cloudflare Privacy Policy.

8. Cookies and similar technologies

React Player does not place optional first-party advertising or analytics cookies. Its own browser storage is limited to the functional items listed above. React Player therefore does not currently show a general cookie banner.

Third-party media players may use their own cookies or similar technologies when the streamer explicitly requests and loads their content. React Player does not use those technologies to create advertising profiles.

9. Contact messages

If you email Kvalvik Studios, the message and contact information you provide are used to answer the request, provide support, handle privacy requests, prevent abuse, or meet legal obligations. The legal basis is taking steps at your request and Kvalvik Studios' legitimate interest in operating and supporting the project.

Support correspondence is normally deleted when it is no longer reasonably needed. Closed support matters are reviewed and may be retained for up to 24 months where useful for support history, security, dispute handling, or legal obligations.

10. International processing

Some infrastructure and media providers operate internationally and may process data outside Norway or the EEA. Their own privacy policies describe the safeguards and legal mechanisms they use for international transfers.

11. Your rights

Where the GDPR applies, you may have rights including access, correction, deletion, restriction, objection, and data portability, depending on the processing involved.

Because React Player has no user accounts and intentionally keeps most state on the streamer's own computer, Kvalvik Studios may hold little or no information that identifies you. Privacy questions and requests can be sent to [email protected].

You may also complain to the Norwegian Data Protection Authority (Datatilsynet).

12. Changes

This policy may be updated when React Player, third-party integrations, or legal requirements change. The effective date at the top will be updated when the policy changes materially.