google_photos README: publishing needs Branding first; add a Privacy section - #140
Merged
Merged
Conversation
…sters, and a Privacy section
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.
Found during the first real setup on 2026-09-23. Google greys out Publish app until the Branding page has an app name, a support email, a home page URL and a privacy policy URL, so "publish to Production" isn't one click. Step 2 now says so, and names the Error 403 access_denied an unlisted Testing account gets. The new Privacy section is what the privacy-policy URL points to. It says what's stored (three local files), which hosts are contacted (Google only; the QR code is drawn locally), and how to revoke access.