cloudflare / wildebeest

Wildebeest is an ActivityPub and Mastodon-compatible server
Other
2.05k stars 399 forks source link

Feature request: Privacy Policy Page #281

Closed nthomasgsy closed 1 year ago

nthomasgsy commented 1 year ago

Please can I suggest the need to have a privacy policy that is displayed on the root page. This is required for GDPR compliance in Europe and we are in a grey area of legality without it. This should be admin editable and if possible should tie in to the Cloudflare cookie policy where Cloudflare services are enabled, such as analytics.

UK ICO Guidance on how to write a Privacy Notice

(I had suggested this on Discord server but was told to raise an issue).

celso commented 1 year ago

Hi @nthomasgsy, thanks for your message.

The Wildebeast code has been released by Cloudflare under the Apache 2.0 license. You are free to use, modify and deploy the Wildebeast code in accordance with such open source license.

Wildebeast is not provided by Cloudflare as a managed service so we don't have Cloudflare-specific terms or a privacy notice that applies to this open sourced code.

If you choose to deploy the Wildebeast code yourself in Cloudflare Workers using D1, R2, Images or other APIs, your use would be subject to Cloudflare's Terms of Service, Supplemental Terms, and Privacy Notice.

https://www.cloudflare.com/terms/

https://www.cloudflare.com/supplemental-terms/#cloudflare-developer-platform-cloudflare-workers-cloudflare-pages-workers-kv-durable-objects-and-r2

https://www.cloudflare.com/privacypolicy/

You are responsible for including appropriate privacy notices and acceptable use policies for your end users' use of Wildebeest.

nthomasgsy commented 1 year ago

Hi, to clarify, this is not a request to formulate a policy on my behalf. But to have a way to provide a link to a static web page from the server home page in the main branch code. On a similar basis, there should be cookie opt in functionality for those browsing the server homepage. This is GDPR Privacy By Design and a legal requirement in Europe.

Get Outlook for Androidhttps://aka.ms/AAb9ysg


From: Celso Martinho @.> Sent: Monday, February 13, 2023 10:37:27 PM To: cloudflare/wildebeest @.> Cc: Nathan Thomas @.>; Mention @.> Subject: Re: [cloudflare/wildebeest] Feature request: Privacy Policy Page (Issue #281)

Hi @nthomasgsyhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnthomasgsy&data=05%7C01%7C%7Cb0d98ce76cbe4d46bca508db0e12e345%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638119246512471950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JiM1dbsCcceSDDSoJWoH%2BfuxSsEJGWMQesPecawG9C8%3D&reserved=0, thanks for your message.

The Wildebeast code has been released by Cloudflare under the Apache 2.0 license. You are free to use, modify and deploy the Wildebeast code in accordance with such open source license.

Wildebeast is not provided by Cloudflare as a managed service so we don't have Cloudflare-specific terms or a privacy notice that applies to this open sourced code.

If you choose to deploy the Wildebeast code yourself in Cloudflare Workers using D1, R2, Images or other APIs, your use would be subject to Cloudflare's Terms of Service, Supplemental Terms, and Privacy Notice.

https://www.cloudflare.com/terms/https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cloudflare.com%2Fterms%2F&data=05%7C01%7C%7Cb0d98ce76cbe4d46bca508db0e12e345%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638119246512471950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iAeo%2F7ykHRz2mf7mfhEKZ20vfJyVatHCYUvFcd3Vh1k%3D&reserved=0

https://www.cloudflare.com/supplemental-terms/#cloudflare-developer-platform-cloudflare-workers-cloudflare-pages-workers-kv-durable-objects-and-r2https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cloudflare.com%2Fsupplemental-terms%2F%23cloudflare-developer-platform-cloudflare-workers-cloudflare-pages-workers-kv-durable-objects-and-r2&data=05%7C01%7C%7Cb0d98ce76cbe4d46bca508db0e12e345%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638119246512471950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4%2Ff%2FRXA6bCaJt3E2hsRIcXh6AQUTU5RCv45G9pi0Oms%3D&reserved=0

https://www.cloudflare.com/privacypolicy/https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cloudflare.com%2Fprivacypolicy%2F&data=05%7C01%7C%7Cb0d98ce76cbe4d46bca508db0e12e345%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638119246512471950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=a%2Fit42Amk9IeQY5Lp2Drfe%2Bw2C2nVoT1ssCo4J48dnE%3D&reserved=0

You are responsible for including appropriate privacy notices and acceptable use policies for your end users' use of Mastodon.

— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcloudflare%2Fwildebeest%2Fissues%2F281%23issuecomment-1428795354&data=05%7C01%7C%7Cb0d98ce76cbe4d46bca508db0e12e345%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638119246512471950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OkLKQRK2AVItfyuiHuL3VbI1Q0D2o83ZG%2F4ZU2kWlQ8%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZKEG4DKF7CEX6HAVEYWNO3WXKZSPANCNFSM6AAAAAAU2SL3WU&data=05%7C01%7C%7Cb0d98ce76cbe4d46bca508db0e12e345%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638119246512628182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QFpTISZOxSSCcJ552MnprODJGeWhj%2BvU2CIP6E%2BmvJA%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>

celso commented 1 year ago

I understand now, sorry for the confusion. Wildebeest has no cookies, but having an optional link to a policy page makes sense, we'll look into that.