|
| 1 | +<script lang="ts"> |
| 2 | + import env from "$lib/env"; |
| 3 | + import { t } from "$lib/i18n/translations"; |
| 4 | + |
| 5 | + import SectionHeading from "$components/misc/SectionHeading.svelte"; |
| 6 | +</script> |
| 7 | + |
| 8 | +<section id="general"> |
| 9 | +<SectionHeading |
| 10 | + title={$t("about.heading.general")} |
| 11 | + sectionId="general" |
| 12 | +/> |
| 13 | + |
| 14 | +політика конфіденційності кобальту проста: ми не збираємо і не зберігаємо нічого |
| 15 | +про вас. те, що ви робите, є винятково вашою справою, а не нашою чи когось |
| 16 | +іншого. |
| 17 | + |
| 18 | +these terms are applicable only when using the official cobalt instance. in |
| 19 | +other cases, you may need to contact the instance hoster for accurate info. |
| 20 | +</section> |
| 21 | + |
| 22 | +<section id="local"> |
| 23 | +<SectionHeading |
| 24 | + title={$t("about.heading.local")} |
| 25 | + sectionId="local" |
| 26 | +/> |
| 27 | + |
| 28 | +tools that use on-device processing work offline, locally, and never send any |
| 29 | +processed data anywhere. they are explicitly marked as such whenever applicable. |
| 30 | +</section> |
| 31 | + |
| 32 | +<section id="saving"> |
| 33 | +<SectionHeading |
| 34 | + title={$t("about.heading.saving")} |
| 35 | + sectionId="saving" |
| 36 | +/> |
| 37 | + |
| 38 | +when using saving functionality, cobalt may need to proxy or remux/transcode |
| 39 | +files. if that's the case, then a temporary tunnel is created for this purpose |
| 40 | +and minimal required information about the media is stored for 90 seconds. |
| 41 | + |
| 42 | +on an unmodified & official cobalt instance, **all tunnel data is encrypted with |
| 43 | +a key that only the end user has access to**. |
| 44 | + |
| 45 | +encrypted tunnel data may include: |
| 46 | +- origin service's name. |
| 47 | +- original URLs for media files. |
| 48 | +- internal arguments needed to differentiate between types of processing. |
| 49 | +- minimal file metadata (generated filename, title, author, creation year, |
| 50 | + copyright info). |
| 51 | +- minimal information about the original request that may be used in case of an |
| 52 | + URL failure during the tunnelling process. |
| 53 | + |
| 54 | +this data is irreversibly purged from server's RAM after 90 seconds. no one has |
| 55 | +access to cached tunnel data, even instance owners, as long as cobalt's source |
| 56 | +code is not modified. |
| 57 | + |
| 58 | +media data from tunnels is never stored/cached anywhere. everything is processed |
| 59 | +live, even during remuxing and transcoding. cobalt tunnels function like an |
| 60 | +anonymous proxy. |
| 61 | + |
| 62 | +if your device supports local processing, then encrypted tunnel info includes |
| 63 | +way less info, because it's returned to client instead. |
| 64 | + |
| 65 | +see the [related source code on |
| 66 | +github](https://github.com/imputnet/cobalt/tree/main/api/src/stream) to learn |
| 67 | +more about how it works. |
| 68 | +</section> |
| 69 | + |
| 70 | +<section id="encryption"> |
| 71 | +<SectionHeading |
| 72 | + title={$t("about.heading.encryption")} |
| 73 | + sectionId="encryption" |
| 74 | +/> |
| 75 | + |
| 76 | +temporarily stored tunnel data is encrypted using the AES-256 standard. |
| 77 | +decryption keys are only included in the access link and never |
| 78 | +logged/cached/stored anywhere. only the end user has access to the link & |
| 79 | +encryption keys. keys are generated uniquely for each requested tunnel. |
| 80 | +</section> |
| 81 | + |
| 82 | +{#if env.PLAUSIBLE_ENABLED} |
| 83 | +<section id="plausible"> |
| 84 | +<SectionHeading |
| 85 | + title={$t("about.heading.plausible")} |
| 86 | + sectionId="plausible" |
| 87 | +/> |
| 88 | + |
| 89 | +we use [plausible](https://plausible.io/) to get an approximate number of active |
| 90 | +cobalt users, fully anonymously. no identifiable information about you or your |
| 91 | +requests is ever stored. all data is anonymized and aggregated. we self-host and |
| 92 | +manage the [plausible instance](https://{env.PLAUSIBLE_HOST}/) that cobalt uses. |
| 93 | + |
| 94 | +plausible doesn't use cookies and is fully compliant with GDPR, CCPA, and PECR. |
| 95 | + |
| 96 | +if you wish to opt out of anonymous analytics, you can do it in [privacy |
| 97 | +settings](/settings/privacy#analytics). if you opt out, the plausible script |
| 98 | +will not be loaded at all. |
| 99 | + |
| 100 | +[learn more about plausible's dedication to |
| 101 | +privacy](https://plausible.io/privacy-focused-web-analytics). |
| 102 | +</section> |
| 103 | +{/if} |
| 104 | + |
| 105 | +<section id="cloudflare"> |
| 106 | +<SectionHeading |
| 107 | + title={$t("about.heading.cloudflare")} |
| 108 | + sectionId="cloudflare" |
| 109 | +/> |
| 110 | + |
| 111 | +we use cloudflare services for: |
| 112 | +- ddos & abuse protection. |
| 113 | +- bot protection (cloudflare turnstile). |
| 114 | +- hosting & deploying the statically rendered web app (cloudflare workers). |
| 115 | + |
| 116 | +all of these are required to provide the best experience for everyone. |
| 117 | +cloudflare is the most private & reliable provider for all mentioned solutions |
| 118 | +that we know of. |
| 119 | + |
| 120 | +cloudflare is fully compliant with GDPR and HIPAA. |
| 121 | + |
| 122 | +[learn more about cloudflare's dedication to |
| 123 | +privacy](https://www.cloudflare.com/trust-hub/privacy-and-data-protection/). |
| 124 | +</section> |
0 commit comments