Repository navigation
The model names Google as a way for a reader to sign in - #292
Merged
Merged
Conversation
id.blust.ch is about to offer Sign in with Google, as zitadel/google.tf in robertblust/id-blust-ch sets it up: a reader the owner has invited may sign in with a Google account whose verified address is the invited one, and Google opens no account, since creation, auto-creation and registration are off. Signing a reader in now names what that adds: the link id.blust.ch keeps with the reader's account, the Google account's id and email address, kept until the link or the account is removed, and Google as a recipient that learns of the sign-in only when the reader chooses it. The legal basis stays legitimate interests, which the owner confirmed. Google is a page of its own beside Google Cloud rather than a second role on it. The contract is another, the Google APIs Terms of Service with Google LLC under Google's controller-controller terms, not the Cloud addendum with Google Cloud EMEA Limited; the countries are another, wherever Google chooses rather than Zurich; and Google keeps the sign-in for a purpose of its own, so legal-name, countries, processing and the transfer could not be written for both on one page. Its transfer from Switzerland rests on the Swiss-U.S. Data Privacy Framework, under which Google LLC is certified, and it lists no sub-processors, since it is a controller for what it keeps. The landscape gains a SaaS kind and the system Sign in with Google, which id.blust.ch connects to over OpenID Connect. Verified: npx github:companygraph/meta-model#v0.94.0 check, sh conventions/conventions-check, sh conventions/conventions-sync check, and the companygraph-validate pass by hand against meta/core/CONVENTIONS.md and the schemas' writing rules, since the skill does not load in a session rooted outside this repository. Process: Delivery Phase: Implement Track: Code Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 25, 2026
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.
id.blust.ch is about to offer Sign in with Google, as zitadel/google.tf in robertblust/id-blust-ch sets it up: a reader the owner has invited may sign in with a Google account whose verified address is the invited one, and Google opens no account, since creation, auto-creation and registration are off. Signing a reader in now names what that adds: the link id.blust.ch keeps with the reader's account, the Google account's id and email address, kept until the link or the account is removed, and Google as a recipient that learns of the sign-in only when the reader chooses it. The legal basis stays legitimate interests, which the owner confirmed.
Google is a page of its own beside Google Cloud rather than a second role on it. The contract is another, the Google APIs Terms of Service with Google LLC under Google's controller-controller terms, not the Cloud addendum with Google Cloud EMEA Limited; the countries are another, wherever Google chooses rather than Zurich; and Google keeps the sign-in for a purpose of its own, so legal-name, countries, processing and the transfer could not be written for both on one page. Its transfer from Switzerland rests on the Swiss-U.S. Data Privacy Framework, under which Google LLC is certified, and it lists no sub-processors, since it is a controller for what it keeps. The landscape gains a SaaS kind and the system Sign in with Google, which id.blust.ch connects to over OpenID Connect.
The same entries go into the other two models in companygraph/mental-model#143 and guestgraph/mental-model#85.
Verified: npx github:companygraph/meta-model#v0.94.0 check, sh conventions/conventions-check, sh conventions/conventions-sync check, and the companygraph-validate pass by hand against meta/core/CONVENTIONS.md and the schemas' writing rules, since the skill does not load in a session rooted outside this repository.
🤖 Generated with Claude Code