Skip to content

Publish a privacy policy so the Drive upload sign-in never expires - #13

Merged
rune-gh merged 1 commit into
mainfrom
docs/google-drive-privacy
Nov 20, 2026
Merged

rune-gh merged 1 commit into
mainfrom
docs/google-drive-privacy

Conversation

@rune-gh

@rune-gh rune-gh commented Nov 20, 2026

Copy link
Copy Markdown
Owner

The hub uploads its trace archive to Google Drive through our own Google OAuth client. Google won't move an External OAuth app from Testing to In production until it has a public privacy policy. While the app stays in Testing, Google expires its refresh tokens every 7 days, which would silently stop the daily uploads.

This adds docs/google-drive-privacy.md, the URL we'll give Google. It states that the client uses only the drive.file scope, uploads age-encrypted segments to the owner's own Drive, and shares nothing with third parties. It's a docs-only change.

Created with Claude Opus 5.5 in T3 Code.

🤖 Generated with Claude Code

Google requires a public privacy policy before an External OAuth app can
be published. Unpublished apps get refresh tokens that expire after
7 days, which would stop the hub's daily Drive uploads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@rune-gh
rune-gh merged commit 6eed773 into main Nov 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant