feat: establish product analytics with privacy budgets#302
Merged
kryputh merged 2 commits intoJun 16, 2026
Conversation
4 tasks
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
2 participants
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.
What was done
Defined the minimum event model for tracking product analytics in src/services/analytics.ts.
Implemented a PrivacyAnalytics service that strictly filters out plaintext contents (e.g. bodies, subjects, keys, correspondents).
Assigned and enforced a privacy budget per event (e.g. epsilon limits) to prevent deanonymization.
Defined a TTL retention schedule which automatically expires logged events.
Added an "Analytics" tab to the DemoAdminDashboard to view real-time activation and reliability signals (e.g., Weekly Retained Mailboxes, Send Success Rate).
Added UI functionality to pause/disable analytics collections globally.
Why it was done
The team needs verifiable activation and reliability evidence to monitor product health without reconstructing communication graphs or compromising user privacy.
How it was verified
Verified that event payloads containing forbidden plaintext keys throw validation errors.
Verified that analytics can be completely disabled via the dashboard state.
Verified that the UI displays non-relational metric summaries for activation and reliability.
Closes #50