langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Refactor/Chore] Analytics and Tracking #20973

New Issue
Closed
opened 2026-02-21 20:10:04 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:10:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Dec 11, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Description

In Europe, a website has to show a cookie / data policy that the user can accept or decline, without limiting the software functionality if the policy is declined.

Dify shows a cookie policy:

Image

Which incorrectly uses some sort of template:

Image

The Privacy Policy should list all the third parties tracking softwares that you use and that you shares data with.

Dify uses both Google Analytics and Amplitude Analytics:

Image

It never checks the user consent before starting to trace or send tracking events:

Image Image

Motivation

Under EU GDPR, tracking after user consent requires that consent be freely given, specific, informed, and unambiguous, meaning users must actively opt-in for each purpose (e.g., analytics, marketing) before trackers activate, and it must be as easy to reject as to accept, with clear information provided about what's being tracked (cookies, pixels, fingerprinting). Websites must use Consent Management Platforms (CMPs) to document choices, respect withdrawals, and avoid "cookie walls" or nudging users towards acceptance, ensuring transparency and granular control over their data.

Additional Context

No response

Originally created by @DavideDelbianco on GitHub (Dec 11, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for refactors or chores; if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Description In Europe, a website has to show a cookie / data policy that the user can accept or decline, without limiting the software functionality if the policy is declined. Dify shows a cookie policy: <img width="705" height="304" alt="Image" src="https://github.com/user-attachments/assets/3e6cb10b-ba91-429f-aabd-297291d9b35c" /> Which incorrectly uses some sort of template: <img width="1319" height="214" alt="Image" src="https://github.com/user-attachments/assets/56978fec-b323-49ac-bae6-f148d4b19ee5" /> The Privacy Policy should list all the third parties tracking softwares that you use and that you shares data with. Dify uses both Google Analytics and Amplitude Analytics: <img width="697" height="435" alt="Image" src="https://github.com/user-attachments/assets/8efff11d-3e0e-4e3d-a331-830e8286731b" /> It never checks the user consent before starting to trace or send tracking events: <img width="651" height="505" alt="Image" src="https://github.com/user-attachments/assets/9f2680b5-15f9-485a-b647-f49ce7be720a" /> <img width="891" height="589" alt="Image" src="https://github.com/user-attachments/assets/29b2196f-a441-4b10-b008-0d5fdaccfb18" /> ### Motivation Under EU GDPR, tracking after user consent requires that consent be freely given, specific, informed, and unambiguous, meaning users must actively opt-in for each purpose (e.g., analytics, marketing) before trackers activate, and it must be as easy to reject as to accept, with clear information provided about what's being tracked (cookies, pixels, fingerprinting). Websites must use Consent Management Platforms (CMPs) to document choices, respect withdrawals, and avoid "cookie walls" or nudging users towards acceptance, ensuring transparency and granular control over their data. ### Additional Context _No response_
yindo closed this issue 2026-02-21 20:10:04 -05:00
yindo commented 2026-02-21 20:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@CodingOnStar commented on GitHub (Dec 11, 2025):

Okay, thanks for the issue. We will handle it as soon as possible.

@CodingOnStar commented on GitHub (Dec 11, 2025): Okay, thanks for the issue. We will handle it as soon as possible.
yindo commented 2026-02-21 20:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 29, 2025):

We have updated our Cookie Policy to the latest version, which now explicitly discloses the use of Amplitude as an analytics cookie. You can opt out of Amplitude data collection via the 'Customize' button. Thank you for your suggestion.

@crazywoola commented on GitHub (Dec 29, 2025): We have updated our Cookie Policy to the latest version, which now explicitly discloses the use of Amplitude as an analytics cookie. You can opt out of Amplitude data collection via the 'Customize' button. Thank you for your suggestion.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20973
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?