RSKTV ← Back to site
Your data

Privacy policy

Last updated :

This page is a courtesy translation. The agreement is drawn up in French in accordance with the Charter of the French Language; in the event of any discrepancy, the French version prevails — read the French version.

RSKTV Player Pro is a media player. It does not provide, host, resell or suggest any content: no channels, no films, no content subscription. Playlists and access credentials are added by the user, who is solely and entirely responsible for them.

This policy describes the data we process, why we process it, and the rights available to you. It describes how the service actually works, not a general intention.

1. Controller

RSK DIGITAL SOLUTION S.E.N.C., Québec, Canada.

Person in charge of the protection of personal information

As required by Québec law, one person within the enterprise is in charge of the protection of personal information. Their contact details:

2. Applicable framework

Several sets of rules apply at the same time, and where they differ we apply the more protective one:

Representative in the European Union

Article 27 of the GDPR requires a controller established outside the Union to designate a representative established in the Union, whom data subjects may contact instead of us.

The contact details of the publisher's representative in the European Union will be published here as soon as one is designated. Data subjects may contact the publisher directly, using the details given above.

3. Data we process

DataWhyLegal basis
Device identifier (MAC address) Attach the licence to a device, start the trial only once per device, apply activation after payment Performance of the contract
Device key Authenticate access to the playlist configuration area Performance of the contract
Playlist settings: server address, username, password, or direct link Send the configuration to your device so that you do not have to type it in with the remote control Performance of the contract
Name of the programme being watched — only during a diagnostic window that you have requested, sixty minutes at most Understand a playback failure you have reported to us. A single value, overwritten on each send and erased when the window closes. This reading is separate from the playback history described below Performance of the contract — support at your request
Answer to the verification test (captcha) Prevent automated attempts on the form Legitimate interest — security
IP address and server logs Security, abuse prevention, diagnostics Legitimate interest — security
Customer account, if you create one (optional): email address, password if you choose one (stored in hashed form), single-use sign-in codes, linked devices (name, model, platform), playback sessions in progress Identify you, link your devices to the account, apply the limit on devices and on simultaneous playback Performance of the contract
Preferences synchronised through the account: playlists, favourites, resume points, display settings, parental code (stored in hashed form), hidden groups Find your settings again on each linked device Performance of the contract
Email, name, country and amount of the order, where the publisher is itself the seller of the licence Issue the invoice, apply the licence, handle a refund request Performance of the contract and legal obligation — accounting
Country inferred from the IP address at the time of purchase Determine the applicable sales tax and keep evidence of it, as tax law requires Legal obligation — taxation
Transaction reference Match a payment to the device to be activated Performance of the contract
What you watch: title of the programme or item opened, type (live or video), start time and playback duration Helping you: seeing what happened when you report a fault, checking that a device is playing correctly, and measuring usage. Nothing is sent before twenty seconds of stable playback Consent, requested in the application and off by default (see below)
Errors reported by the application (code, message, context, number of occurrences, first and last date), playback performance measurements and, on Android, crash reports (technical trace, application version, device identifier) Fixing faults without having to ask you to describe them Consent, requested together with the previous item

We never see your banking details: payment takes place on our payment providers' platforms.

Your playlist credentials, and your list of titles

When you save a server-type playlist, the address, username and password are sent to our server; the password is stored there encrypted. Depending on the playlist, one of two things happens. Either our server connects to your source with those credentials to retrieve the list of categories and titles and keeps a copy of it — that copy lets your device show the playlist without delay rather than reloading it at every start. Or your device queries the source directly, and our server keeps nothing of it. It is partitioned per device — no query cross-references it with another user's — it serves no ranking, no recommendation and no directory, and it is disclosed to no one. If you would rather entrust us with nothing, enter your settings directly on the device: the site is only a convenience shortcut.

Your playback history and your error reports

The first time it starts, the application asks whether you agree to send your playback history and your error reports. This choice is off by default, and declining changes nothing in how the player works. You can change it at any time in Settings › Privacy.

Your choice is sent to our server, which applies it to your device: if you decline, recording stops and the history already recorded, the error reports and, on Android, the device's crash reports are erased. Versions of the application released before this update do not yet send this choice: if you use one of them, update the application, or write to us (article 10) so that we apply your refusal directly on our server.

When it is active, the history comprises the title opened, whether it is live or video, the start time and the duration. It is attached to your device identifier and kept for ninety days, then deleted automatically. It is accessible only to the service administrator — never to a reseller — and it is never sold, never passed to a third party, and never used for advertising or profiling.

4. What we do not collect

If you have agreed to it, a playback history, on the other hand, is kept on our servers: it is described in article 3, and therefore does not appear in this list.

5. Recipients

Your data is disclosed only to the following recipients, and only to the extent they need it:

No other disclosure to third parties takes place, except where required by law or requested by a competent authority.

6. Retention periods

7. Location and transfers

Location of our servers: France (Paris). The publisher is established in Québec, Canada.

If you reside in Québec

Your information is communicated outside Québec: to our servers in France, and to the providers established in the United States named in article 5 (Cloudflare, Stripe, Google). Before these communications, Québec law requires us to carry out a privacy impact assessment and to satisfy ourselves that the information will receive adequate protection.

If you reside in the European Union

Our servers are located in France, therefore within the European Union: hosting your data does not constitute a transfer outside the European Economic Area. As the publisher is established in Canada, access to that data from Canada relies on the European Commission's adequacy decision for private organisations subject to PIPEDA, which is our situation. No additional safeguard within the meaning of article 46 of the GDPR is therefore required.

Should hosting be moved outside the Union, this policy would be updated accordingly.

Cloudflare, Stripe and Google may process data in the United States. According to their own statements, these companies participate in the EU–US Data Privacy Framework, and their terms otherwise provide for the European Commission's standard contractual clauses.

8. Local storage, cookies

This site sets no cookies. It uses only your browser's local storage, for four strictly functional items:

These values stay in your browser, are never transmitted, and disappear when you clear the site's data. They do not require prior consent.

As payment takes place on our providers' platforms, those providers may set their own cookies on their own domains, for security and fraud prevention purposes. Those cookies are governed by their respective policies.

9. Security and incidents

Exchanges with the site and with the server are encrypted (HTTPS). Playlist passwords are stored encrypted; account passwords and parental codes are stored in hashed form. Attempts to access the configuration area are limited in number.

Where a confidentiality incident presents a risk of serious injury, we promptly notify the Commission d'accès à l'information and the persons concerned.

As no system is infallible, we invite you to report any anomaly to us without delay.

10. Your rights

You have the following rights over your personal information:

To exercise them, write to [email protected] stating the identifier of the device concerned. We reply within thirty days.

For the playback history and error reports, the simplest way is to withdraw your consent in Settings › Privacy: the history already recorded is then erased. You may also write to us.

Erasure of all the data relating to a device ends the use of that device: it can no longer be used, nor start the free trial again. We remind you of this before carrying out the request. For the period required by tax law, we keep the accounting records and the sole record that the trial has already been used.

You may also lodge a complaint with the competent authority:

11. Minors

The licence and the account are taken out by a person of full age. The application may be used by members of that person's household, under their responsibility; profiles and parental controls exist for that purpose. We ask for no information about the age or identity of household members.

In Québec, processing the personal information of a person under fourteen years of age requires the consent of the person having parental authority, except where it is manifestly done for that person's benefit. This is one of the reasons why the playback history is off by default.

12. Changes

This policy may be updated. The date of the last change appears at the top of this page. Any substantial change will be announced on the site.