fix(priv): textes factuels — Forgejo couvert (comptes/sessions/tokens/dépôts section 4.1), durée de conservation et sécurité mises à jour, footer ne prétend plus 'aucun cookie' mais cookie de langue unique sans suivi, et nuance sur le tunnel Tailscale (TLS local, sans CDN).
This commit is contained in:
riricdev
parent
537478d016
commit
a95a287327
6 changed files with 29 additions and 17 deletions
|
|
@ -42,7 +42,7 @@
|
|||
<h3 id="canaux">2.2 Website Access Channels: Clearnet Tunnel and Tor Hidden Service</h3>
|
||||
<p>The access channel you use determines the actual level of confidentiality of the traffic. We explain the consequences here with the greatest transparency.</p>
|
||||
<h4>a) Clearnet channel (tunnel)</h4>
|
||||
<p>The clearnet website is made accessible by means of a tunnel whose operator is Tailscale, Inc., a company governed by US law. The TLS encryption on this channel is <strong>terminated on the side of the tunnel operator</strong>, not on our infrastructure. Consequently, <strong>the content you transmit over this channel (requested pages, responses, exchanged content) is decrypted and technically readable by the tunnel operator</strong>, as are IP addresses and connection metadata. These elements are not communicated to us by the operator, and we do not use them. Access to this content may moreover be required of the operator by a public authority in the context of an applicable legal proceeding, including under the US CLOUD Act (22 U.S.C. § 6201 et seq.). For this channel, we for our part collect only the technical logs described in <a href="#logs">Section 2.3</a> below (which do not include the content).</p>
|
||||
<p>The clearnet website is made accessible by means of a tunnel provided by Tailscale, Inc., a company governed by US law, using its "Funnel" feature, which exposes a public TCP port (443) to our infrastructure. The TLS (HTTPS) encryption on this channel is <strong>terminated on our own infrastructure</strong>, not on the side of the tunnel operator: Tailscale Funnel relays do not decrypt the traffic, and the content of the pages (requests, responses, exchanged content) is <strong>not</strong> technically readable by the tunnel operator. The communication between your browser and our server remains encrypted end to end. The tunnel operator nevertheless remains a US-law network intermediary, which sees connection metadata (source IP address, destination, traffic volume and timestamps) and may be called upon by a public authority to provide access in the context of an applicable legal proceeding, including under the US CLOUD Act (22 U.S.C. § 6201 et seq.). These metadata are not communicated to us by the operator, and we do not use them. For this channel, we for our part collect only the technical logs described in <a href="#logs">Section 2.3</a> below (which do not include the content).</p>
|
||||
<h4>b) Tor hidden service (.onion)</h4>
|
||||
<p>The Tor hidden service (<code>http://l5cbkqmok4rnkhbtpltmtlf3pa5i5rfw23z2mtj5tugpo3quta3b5hqd.onion</code>), by contrast, is encrypted end to end, from your browser to our infrastructure, <strong>with no TLS termination point at a third party</strong>. No intermediary operator can read the content, and your IP address remains concealed from us and from any observer. The hidden service is the most privacy-respecting channel. For this channel, we likewise process only the technical logs described in <a href="#logs">Section 2.3</a>; the content is not read by any third party.</p>
|
||||
|
||||
|
|
@ -109,10 +109,14 @@
|
|||
<p>The administration panel (<a href="/z-panel">/z-panel</a>) is an internal tool protected by a password (hashed with Argon2id). It is not indexed by search engines (<code>noindex, nofollow</code>).</p>
|
||||
<p>Administration sessions are managed by random session tokens (32 bytes, encoded in base64url) with a 24-hour lifetime. Login attempts are limited to 5 per 15-minute window per IP address. These authentication data are kept in RAM and are lost upon server restart.</p>
|
||||
<p>The panel provides access to server access logs, request statistics, article administration, translations, and the honeypot system. These data are accessible exclusively by the administrator.</p>
|
||||
<h3 id="forgejo">4.1 Forgejo (Zektyc Git)</h3>
|
||||
<p>A Forgejo server (<a href="/git">/git</a>) hosts the source code of the site and its projects, along with community contributions. Even though it is served from the same domain, it is a separate service.</p>
|
||||
<p>When you create an account on this Forgejo, the data you voluntarily provide (username, email address, optional profile details) is stored in the database of this server, hosted on our infrastructure in France. It is neither sold, nor shared with third parties, nor used for marketing or profiling (Art. 6.1(b) GDPR). Deleting your account removes this data.</p>
|
||||
<p>Signing in to a Forgejo account relies on session cookies (first-party, secure, limited to the <code>/git/</code> path) and, if applicable, personal access tokens (API) that you generate and that are stored encrypted in the database. The content of the repositories you publish (code, pull requests, issues, comments) is intentionally public, in line with the purpose of the service. Connection IP addresses are subject to the technical logs described in <a href="#logs">Section 2.3</a>.</p>
|
||||
|
||||
<h2 id="cookies">5. Cookies</h2>
|
||||
<p>The site sets a <strong>single language-preference cookie</strong>, <code>zektyc-lang</code>. It remembers the display language you choose or that is detected (French or English), so the right version of each page is served; it carries no unique identifier, holds no browsing data other than the language, is neither read nor used for tracking, and expires after one year. It is a first-party cookie. No third-party cookie and no tracker is used.</p>
|
||||
<p>Your language choice is also remembered on your device (in the browser's local storage, <code>localStorage</code>, key <code>zektyc-lang</code>) and can be changed at any time via the language selector at the top of every page. These preferences are kept locally on your device and are never transmitted or retained server-side beyond the visiting cookie described above.</p>
|
||||
<p>The website (public pages, excluding <code>/git/</code>) sets a <strong>single language-preference cookie</strong>, <code>zektyc-lang</code>. It remembers the display language you choose or that is detected (French or English), so the right version of each page is served; it carries no unique identifier, holds no browsing data other than the language, is neither read nor used for tracking, and expires after one year. It is a first-party cookie. No third-party cookie and no tracker is used. The Forgejo service (<code>/git/</code>) sets its own first-party session cookies, described in <a href="#forgejo">Section 4.1</a>.</p>
|
||||
<p>Your language choice is also remembered on your device (in the browser's local storage, <code>localStorage</code>, key <code>zektyc-lang</code>), as is the display theme — light or dark — (key <code>zektyc-theme</code>). Both preferences can be changed at any time via the language selector and the theme button at the top of every page. They are kept locally on your device and are never transmitted or retained server-side beyond the visiting cookie described above.</p>
|
||||
<p>The digital fingerprint test temporarily uses <code>sessionStorage</code> only when you launch the multi-round test, to preserve results between reloads. This storage is automatically cleared at the end of the test or when the tab is closed; it does not constitute a cookie or a tracker.</p>
|
||||
|
||||
<h2>6. Recipients and Sub-processors</h2>
|
||||
|
|
@ -135,7 +139,7 @@
|
|||
|
||||
<h2 id="transferts">7. Transfers Outside the European Union</h2>
|
||||
<p>Regarding the site and infrastructure: they are hosted in France and operated within the European Union. No data processed by the site is stored outside the European Union or the European Economic Area (Art. 44 et seq. GDPR).</p>
|
||||
<p>Regarding the clearnet channel: the tunnel making it accessible is provided by Tailscale, Inc., a company governed by US law. As explained in <a href="#canaux">Section 2.2</a>, this channel implies that the content transits in cleartext through this operator, which is its TLS termination point. Tailscale does not act as a processor within the meaning of Article 28 GDPR for this traffic, so this passage through a US entity is an accepted limitation of this access channel; it does not apply to the Tor hidden service, which remains end-to-end encrypted without a third-party intermediary.</p>
|
||||
<p>Regarding the clearnet channel: the tunnel making it accessible is provided by Tailscale, Inc., a company governed by US law. As explained in <a href="#canaux">Section 2.2</a>, this channel routes the encrypted (HTTPS) traffic through the operator's relays, which do not decrypt its content — the latter is only readable on our own infrastructure, where the TLS terminates. Connection metadata (source IP address, destination, volume, timestamps) nevertheless transit through a US entity; since Tailscale does not act as a processor within the meaning of Article 28 GDPR for this traffic, this passage is an accepted limitation of this access channel. It does not apply to the Tor hidden service, which remains end-to-end encrypted without a third-party intermediary.</p>
|
||||
<p>Regarding the email contact channel: Proton Mail is operated from Switzerland, a country that benefits from an adequacy decision by the European Commission.</p>
|
||||
<p>Regarding Signal and Discord: their servers may be located outside the European Union. Signal encrypts messages end-to-end, which Discord does not.</p>
|
||||
<p>Regarding the Discord bot: the audio to be transcribed and the texts processed by the bot are transmitted to Groq (United States), as part of the transcription and response generation service. Groq does not appear on the list of organisations certified under the EU-US Data Privacy Framework (DPF). The transfer is governed by the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914), incorporated into Groq's processing agreement (Data Processing Addendum), effective 15 October 2025 — Module 2 (controller to processor). Only the elements strictly necessary for the provision of the service are transmitted, and nothing is retained on our end.</p>
|
||||
|
|
@ -150,7 +154,8 @@
|
|||
<li>Discord bot data (messages, audio, identifiers, history): <strong>no persistent retention</strong>; session history (20 exchanges max) is in RAM only, reset on restart;</li>
|
||||
<li>Fingerprint test data: <strong>no data is transmitted to Zektyc</strong>; characteristics disappear when the tab is closed;</li>
|
||||
<li>Honeypot data (IP addresses): until manual deletion by an administrator;</li>
|
||||
<li>Administration sessions: 24-hour session tokens, in RAM only.</li>
|
||||
<li>Administration sessions: 24-hour session tokens, in RAM only;</li>
|
||||
<li>Forgejo accounts and repository content: kept until voluntary deletion of the account or repository by its owner; Forgejo session cookies: for the duration of the session, until expiry or sign-out.</li>
|
||||
</ul>
|
||||
|
||||
<h2>9. Security</h2>
|
||||
|
|
@ -163,7 +168,8 @@
|
|||
<li>sensitive path blocking (WordPress honeypot);</li>
|
||||
<li>data minimization and limited retention;</li>
|
||||
<li>administration passwords hashed with Argon2id (memoryCost: 65536, timeCost: 4);</li>
|
||||
<li>self-hosted infrastructure in France, without CDN or third-party service.</li>
|
||||
<li>Forgejo account passwords hashed and personal access tokens encrypted (by Forgejo);</li>
|
||||
<li>component-based, self-hosted infrastructure in France, without CDN; the only exception is the Tailscale clearnet access tunnel (described in <a href="#canaux">Section 2.2</a>), a US-law third party.</li>
|
||||
</ul>
|
||||
|
||||
<h2>10. Your Rights</h2>
|
||||
|
|
|
|||
Loading…
Reference in a new issue