admin/cobalt
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

web/about: revise text on all pages & improve readability

Browse Source 
all information is way easier to read and understand. i also added info about new features and explained some concepts in a better language.
This commit is contained in:
wukko
2025-05-23 15:57:33 +06:00
parent 4d29bca13b
commit be84f66dff
5 changed files with 117 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
web/i18n/en/about/privacy.md
View File

@@ -11,9 +11,11 @@
sectionId="general"
/>
cobalt's privacy policy is simple: we don't collect or store anything about you. what you do is solely your business, not ours or anyone else's.
cobalt's privacy policy is simple: we don't collect or store anything about you.
what you do is solely your business, not ours or anyone else's.
these terms are applicable only when using the official cobalt instance. in other cases, you may need to contact the hoster for accurate info.
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.
</section>
<section id="local">
@@ -22,7 +24,9 @@ these terms are applicable only when using the official cobalt instance. in othe
sectionId="local"
/>
tools that use on-device processing work offline, locally, and never send any data anywhere. they are explicitly marked as such whenever applicable.
tools that use on-device processing work offline, locally,
and never send any processed data anywhere.
they are explicitly marked as such whenever applicable.
</section>
<section id="saving">
@@ -31,9 +35,33 @@ tools that use on-device processing work offline, locally, and never send any da
sectionId="saving"
/>
when using saving functionality, in some cases cobalt will encrypt & temporarily store information needed for tunneling. it's stored in processing server's RAM for 90 seconds and irreversibly purged afterwards. no one has access to it, even instance owners, as long as they don't modify the official cobalt image.
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.
processed/tunneled files are never cached anywhere. everything is tunneled live. cobalt's saving functionality is essentially a fancy proxy service.
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](https://github.com/imputnet/cobalt/tree/main/api/src/stream)
to learn more about how it works.
</section>
<section id="encryption">
@@ -42,7 +70,10 @@ processed/tunneled files are never cached anywhere. everything is tunneled live.
sectionId="encryption"
/>
temporarily stored tunnel data is encrypted using the AES-256 standard. decryption keys are only included in the access link and never logged/cached/stored anywhere. only the end user has access to the link & encryption keys. keys are generated uniquely for each requested tunnel.
temporarily stored tunnel data is encrypted using the AES-256 standard.
decryption keys are only included in the access link and never logged/cached/stored anywhere.
only the end user has access to the link & encryption keys.
keys are generated uniquely for each requested tunnel.
</section>
{#if env.PLAUSIBLE_ENABLED}
@@ -52,13 +83,18 @@ temporarily stored tunnel data is encrypted using the AES-256 standard. decrypti
sectionId="plausible"
/>
for sake of privacy, we use [plausible's anonymous traffic analytics](https://plausible.io/) to get an approximate number of active cobalt users. no identifiable information about you or your requests is ever stored. all data is anonymized and aggregated. the plausible instance we use is hosted & managed by us.
we use [plausible](https://plausible.io/) for anonymous traffic analytics,
to get an approximate number of active cobalt users.
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 doesn't use cookies and is fully compliant with GDPR, CCPA, and PECR.
[learn more about plausible's dedication to privacy.](https://plausible.io/privacy-focused-web-analytics)
if you wish to opt out of anonymous analytics, you can do it in [privacy settings](/settings/privacy#analytics).
if you opt out, the plausible script will not be loaded at all.
[learn more about plausible's dedication to privacy](https://plausible.io/privacy-focused-web-analytics).
</section>
{/if}
@@ -68,9 +104,15 @@ if you wish to opt out of anonymous analytics, you can do it in [privacy setting
sectionId="cloudflare"
/>
we use cloudflare services for ddos & bot protection. we also use cloudflare pages for deploying & hosting the static web app. all of these are required to provide the best experience for everyone. it's the most private & reliable provider that we know of.
we use cloudflare services for:
- ddos & abuse protection.
- bot protection (cloudflare turnstile).
- hosting & deploying the statically rendered web app (cloudflare pages).
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 is fully compliant with GDPR and HIPAA.
[learn more about cloudflare's dedication to privacy.](https://www.cloudflare.com/trust-hub/privacy-and-data-protection/)
[learn more about cloudflare's dedication to privacy](https://www.cloudflare.com/trust-hub/privacy-and-data-protection/).
</section>