Add Cookie Policy #63

Closed
opened 2026-10-04 22:58:54 +02:00 by adam · 11 comments
Owner

I think it will be a good ideea to add cookie policy disclaimer on webpage with ability to edit the disclaimer from a .text document

I think it will be a good ideea to add cookie policy disclaimer on webpage with ability to edit the disclaimer from a .text document <!-- github-sync-id:3517520582 -->
adam closed this issue 2026-10-04 22:58:54 +02:00
Author
Owner

How i see it

Context
• Site name: [Your Site Name]
• Domain: [your-domain.com]
• Contact email: [privacy@your-domain.com]
• Jurisdictions to cover: EU (GDPR + ePrivacy), UK GDPR, and California (CPRA).
• Consent UI: we show a banner with Accept all, Deny all, and Customize; users can toggle Analytics and Marketing (Necessary always on). If a user denies all, the app currently redirects to https://www.google.com.

How i see it Context • Site name: [Your Site Name] • Domain: [your-domain.com] • Contact email: [privacy@your-domain.com] • Jurisdictions to cover: EU (GDPR + ePrivacy), UK GDPR, and California (CPRA). • Consent UI: we show a banner with Accept all, Deny all, and Customize; users can toggle Analytics and Marketing (Necessary always on). If a user denies all, the app currently redirects to https://www.google.com. <!-- github-comment-id:3406355587 -->
Author
Owner

I know we are legally required to have this but I really hate the idea of having a cookie banner.

Let's think about a way to do it as minimalist as possible and as non-intrusive as possible.

If this is a concern, we can also just remove the cookie - we only use it for dark/light theme and we might be able to do without cookie at all.

I know we are legally required to have this but I really hate the idea of having a cookie banner. Let's think about a way to do it as minimalist as possible and as non-intrusive as possible. If this is a concern, we can also just remove the cookie - we only use it for dark/light theme and we might be able to do without cookie at all. <!-- github-comment-id:3407932952 -->
Author
Owner

If you are not collecting data from the user, why would you need cookie consent?

If you are not collecting data from the user, why would you need cookie consent? <!-- github-comment-id:3414559288 -->
Author
Owner

I looked into it and it seems we do not need a cookie policy as we do not track or collect user data.

However, we could add a note to the info screen explaining what the cookie does and how long it lasts.

Also, additionally, we could add a link to an external privacy policy or imprint somewhere.

I looked into it and it seems we do not need a cookie policy as we do not track or collect user data. However, we could add a note to the info screen explaining what the cookie does and how long it lasts. Also, additionally, we could add a link to an external privacy policy or imprint somewhere. <!-- github-comment-id:3414849306 -->
Author
Owner

Can you please make this on/off from an environment var? I wouldn't bother viewers on our instance with unnecessary red tape to be honest, so I'd prefer if I can easily turn it off 😕

Can you please make this on/off from an environment var? I wouldn't bother viewers on our instance with unnecessary red tape to be honest, so I'd prefer if I can easily turn it off 😕 <!-- github-comment-id:3415824984 -->
Author
Owner

The cookie or the policy?

The cookie or the policy? <!-- github-comment-id:3415948315 -->
Author
Owner

I'm at this point inclided to remove the cookie alltogether and just default to the dark theme. I really don't like the bureaucracy involved.

I'm at this point inclided to remove the cookie alltogether and just default to the dark theme. I really don't like the bureaucracy involved. <!-- github-comment-id:3415954048 -->
Author
Owner

The cookie or the policy?

Well, both. Cookies don't really need a notification, since, as you found out, you are not collecting/tracking users. There's no legal obligation to notify users if you don't track/collect data.

Regarding the privacy policy, I'm not sure whose privacy you want to apply the document to? If it's node owners - you have their implicit consent to share data, because it's already emitted into the air i.e. they made it public already. If it's web visitor privacy - I don't really know how the web visitor's privacy is impacted if you don't collect their data at all.

> The cookie or the policy? Well, both. Cookies don't really need a notification, since, as you found out, you are not collecting/tracking users. There's no legal obligation to notify users if you don't track/collect data. Regarding the privacy policy, I'm not sure whose privacy you want to apply the document to? If it's node owners - you have their implicit consent to share data, because it's already emitted into the air i.e. they made it public already. If it's web visitor privacy - I don't really know how the web visitor's privacy is impacted if you don't collect their data at all. <!-- github-comment-id:3415968235 -->
Author
Owner

Agreed

Agreed <!-- github-comment-id:3416039530 -->
Author
Owner

This is not for node owners, if you use mesh witout encryption then you agree to share data.
But if you are a web visitor, IP address is data collection, i open this post because one of my local user ask me abouth this.

This is not for node owners, if you use mesh witout encryption then you agree to share data. But if you are a web visitor, IP address is data collection, i open this post because one of my local user ask me abouth this. <!-- github-comment-id:3416399146 -->
Author
Owner

You can tell them, we are not collecting IP addresses. In fact, we are not collecting anything from the internet, only from the radio mesh.

You can tell them, we are not collecting IP addresses. In fact, we are not collecting anything from the internet, only from the radio mesh. <!-- github-comment-id:3416713852 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/potato-mesh#63