Fix/issue 2361 anonymize pii analytics#2368
Open
Prateek2007-cmd wants to merge 7 commits into
Open
Conversation
…event OOM DOS attacks
… and HttpOnly cookie storage
… ML analytics to enforce GDPR compliance
|
@Prateek2007-cmd is attempting to deploy a commit to the janavipandole's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Resolves Issue #2361 (Raw IP Storage in Analytics / GDPR Violation).
The
track_feedbackAPI endpoint, responsible for collecting user telemetry for the ML recommendation engine, was permanently recording rawuser_idstrings (which dynamically fallback to raw IP addresses or identifiable session tokens on the frontend) directly into the database. This constituted a severe data compliance liability under GDPR and CCPA.This PR implements mandatory cryptographic PII anonymization for all telemetry ingestion.
Changes Made
hashliband securely wrapped the incominguser_idstring through aSHA-256hashing function.SECRET_KEYas a cryptographic salt. This prevents reverse-engineering via rainbow tables while maintaining deterministic consistency for the Faiss Vector index and Collaborative Filtering algorithms.Type of Change