cobalt/web/i18n/fr/about/privacy.md

<script lang="ts"> import env from "$lib/env"; import { t } from "$lib/i18n/translations"; import SectionHeading from "$components/misc/SectionHeading.svelte"; </script>

la politique de confidentialité de cobalt est simple : nous ne collectons ni ne stockons rien à votre sujet. ce que vous faites est uniquement votre affaire, pas la nôtre ni celle de quelqu'un d'autre.

these terms are applicable only when using the official cobalt instance. in other cases, you may need to contact the instance hoster for accurate info.

tools that use on-device processing work offline, locally, and never send any processed data anywhere. they are explicitly marked as such whenever applicable.

when using saving functionality, cobalt may need to proxy or remux/transcode files. if that's the case, then a temporary tunnel is created for this purpose and minimal required information about the media is stored for 90 seconds.

on an unmodified & official cobalt instance, all tunnel data is encrypted with a key that only the end user has access to.

encrypted tunnel data may include:

• origin service's name.
• original URLs for media files.
• internal arguments needed to differentiate between types of processing.
• minimal file metadata (generated filename, title, author, creation year, copyright info).
• minimal information about the original request that may be used in case of an URL failure during the tunnelling process.

this data is irreversibly purged from server's RAM after 90 seconds. no one has access to cached tunnel data, even instance owners, as long as cobalt's source code is not modified.

media data from tunnels is never stored/cached anywhere. everything is processed live, even during remuxing and transcoding. cobalt tunnels function like an anonymous proxy.

if your device supports local processing, then encrypted tunnel info includes way less info, because it's returned to client instead.

see the related source code on github to learn more about how it works.

les données de tunnel stockées temporairement sont cryptées en utilisant la norme AES-256. les clés de déchiffrement ne sont incluses que dans le lien d'accès et ne sont jamais enregistrées/mises en cache/stockées nulle part. seul l'utilisateur final a accès au lien et aux clés de chiffrement. les clés sont générées de manière unique pour chaque tunnel demandé.

{#if env.PLAUSIBLE_ENABLED}

we use plausible to get an approximate number of active cobalt users, fully anonymously. no identifiable information about you or your requests is ever stored. all data is anonymized and aggregated. we self-host and manage the plausible instance that cobalt uses.

plausible n'utilise pas de cookies et est entièrement conforme au RGPD, au CCPA et au PECR.

if you wish to opt out of anonymous analytics, you can do it in privacy settings. if you opt out, the plausible script will not be loaded at all.

learn more about plausible's dedication to privacy.

{/if}

we use cloudflare services for:

• ddos & abuse protection.
• bot protection (cloudflare turnstile).
• hosting & deploying the statically rendered web app (cloudflare workers).

all of these are required to provide the best experience for everyone. cloudflare is the most private & reliable provider for all mentioned solutions that we know of.

cloudflare est entièrement conforme au RGPD et à la HIPAA.

learn more about cloudflare's dedication to privacy.