Document SSO authentication in Terms and Privacy Policy - #1153
Merged
Conversation
Co-authored-by: Niek Nijland <ngnijland@gmail.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
sso_session_codecookie, retention, and Auth0's role as authentication broker.Context
This replaces #952 by applying its approved intent to the current legal pages. The wording was refreshed to avoid coupling the policy to volatile token lifetimes or storage details, to cover the applicable GDPR basis when the subscribing customer is the user's organization, and to use the current Microsoft Entra ID product name.
Verification
npm run format:checknpm run lintnpm run typecheck(passes with four existing hints)npm run buildnpm test(7 tests passed)Co-authored with the original contributors from #952.