Privacy Policy
Last updated: October 21, 2026. This policy covers the CoinChorus website, YouTube channel, Telegram channel and the CoinChorus YouTube upload application.
1. Who is responsible
The data controller is NILYS, EURL (single-member limited liability company) with a share capital of €100,000, registered with the RCS Bobigny Trade and Companies Register under no. 793 778 473, registered office 11 rue Henri Christin, 93470 Coubron, France, represented by its manager, Jérôme Rudel. Contact for any privacy matter: contact@coinchorus.com.
2. Visitors and viewers: what we do not collect
- This website sets no cookies and uses no analytics, advertising or tracking tools. It loads no third-party resources, with one exception that you control: on a page that shows our daily video, a short script of our own loads the YouTube player from
youtube-nocookie.com(YouTube's privacy-enhanced mode) only when you press play. Until then, no request is made to YouTube; after that, the player may store data on your device under Google's own privacy policy. - There is no account, no sign-up form and no newsletter.
- Our web server, which we run on a server rented from Hetzner Online GmbH in Germany, keeps no access logs for this website. Technical error logs, which can contain an IP address, are kept for at most 30 days to keep the site secure and running, and are never used to identify or profile visitors.
- On YouTube and Telegram, your viewing, comments and subscriptions are handled by those platforms under their own privacy policies. We only see what the platforms show to any channel owner (for example aggregate view counts and public comments).
3. The CoinChorus YouTube upload application (Google API data)
CoinChorus uses a private application that connects to the YouTube Data API with a single Google account: the account that owns the CoinChorus channel. It is not offered to the public and does not access any other user's Google account.
What it accesses and why
- Scopes:
https://www.googleapis.com/auth/youtube, used only to upload our daily videos to our own channel, set their title, description, thumbnail, captions, playlist and visibility, mark them as containing synthetic (AI-generated) content, and read back the status and public statistics of our own videos; andhttps://www.googleapis.com/auth/yt-analytics.readonly, used only to read the audience-retention statistics of our own videos to improve the format. - Stored: the OAuth refresh token for our own account (on our server, access-restricted, never in source code), and the identifiers, status and statistics of the videos we publish. No data about viewers or other channels is obtained through the API.
- Shared: nothing received from Google APIs is sold, shared with third parties, used for advertising, or used to train AI models.
CoinChorus's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. By using the CoinChorus YouTube application you agree to be bound by the YouTube Terms of Service. Google's processing of data is described in the Google Privacy Policy.
Access can be revoked at any time from the Google account security page: https://security.google.com/settings/security/permissions. When access is revoked, we delete the stored token, and we delete or refresh any stored API data within 30 days, as required by the YouTube API Services policies.
The CoinChorus application does not place, access or recognise cookies or similar technologies on any user's device.
4. Public analysts quoted on CoinChorus
To produce the show, we process content that analysts have published publicly on YouTube.
| Data | Channel name and the name the analyst uses publicly; public channel statistics (subscriber count); title, date and link of public videos; the automatic transcript of the spoken audio; the market calls extracted from it (asset, direction, price levels, timeframe, short verbatim quote with its time stamp); a short summary of each call written by our software; the resulting accuracy score. We do not use their image, voice or video footage. |
|---|---|
| Source | Public YouTube videos and their public captions. The audio file used for transcription is deleted as soon as the transcript is made. |
| Purpose | Reporting and commenting on public market opinions: summarising what analysts say, crediting them, and measuring how their calls compare with actual prices. |
| Legal basis | Our legitimate interest, and the public's interest, in informing about and commenting on public statements (GDPR Art. 6(1)(f)). Only content the analyst chose to publish is used, always credited and linked to its source. |
| Retention | Transcripts: deleted automatically 12 months after the video's publication. Extracted calls, summaries, quotes and scores: deleted 3 years after the call is resolved or its horizon ends. Published shows and dated daily pages stay online as an archive of what was said, and are corrected or cleaned on request. After a justified objection, everything about the channel is deleted within 2 business days, except a minimal record of the objection so that it is never covered again. |
| Recipients | Our processors, under contract: Hetzner Online GmbH (server host, Germany); OpenAI (extraction of calls from transcripts, API); ElevenLabs (AI voice) and, when used, Hedra (AI avatar), which receive only the script of the show, including analysts' names and short quotes. OpenAI, ElevenLabs and Hedra may process data in the United States, under the EU-U.S. Data Privacy Framework where the provider is certified, or under the European Commission's standard contractual clauses. Emails sent to us are forwarded by Cloudflare (Email Routing) to our mailbox at Google (Gmail). Published content is visible on YouTube, Telegram and this site. |
Accuracy scores (profiling)
The accuracy score is an automated evaluation of an analyst's public calls (GDPR Art. 4(4)). The same published rules apply to everyone (see our method), it uses only public calls and Binance prices, and it is shown only after a minimum number of resolved calls. It produces no decision with legal or similarly significant effects on anyone. You can object to it at any time (Art. 21).
Opposition, correction and removal within 2 business days
An analyst can at any time object to being covered, or ask for a quote to be corrected or removed, by writing to contact@coinchorus.com from an address or account that shows they own the channel (see contact). We answer and act within 2 business days: the quote is corrected or removed from the video description, the site and Telegram, the channel is excluded from future shows if requested, and the related data is deleted. Where a published video cannot be edited, we unlist or delete it if the error or objection concerns it.
5. People who contact us
If you write to us, by email or with the contact form, we use your email address, name, subject and message only to answer you and to keep a record of correction, removal or reply requests. Legal basis: our legitimate interest in handling requests, and your consent for the form (Art. 6(1)(f) and (a)). Messages are kept for 3 years after our last exchange, then deleted. The form records no IP address in clear: to limit automated submissions, our server keeps a keyed fingerprint of it, changed every day and erased after 30 days. Messages sent with the form are stored on our server in Germany and forwarded to us as a notification in a private Discord channel (Discord Inc., United States, under the European Commission's standard contractual clauses); emails are forwarded by Cloudflare (Email Routing) to our mailbox at Google (Gmail).
6. Your rights
Under the GDPR you may ask for access to your data, its correction or deletion, the restriction of its processing, and you may object to it at any time (Art. 15 to 21). Write to contact@coinchorus.com; we answer within one month at the latest, within 2 business days for analyst quotes. You may also lodge a complaint with the French data protection authority, the CNIL (www.cnil.fr), or the authority of your country.
7. Security and changes
Our database is kept on a server in Germany with restricted access; processors may process data as described in section 4. Credentials are stored encrypted and never published. We will update this page if what we do changes, and change the date at the top.