Context One Google OAuth Disclosure
Production-readiness package · October 6, 2026
Application: Context One
Homepage: https://phuonggroup.com/context-one.html
Privacy: https://phuonggroup.com/context-one-privacy.html
Authorized domain: phuonggroup.com
Redirect URI: https://phuonggroup.com/api/context-one/google/callback
Requested native scope
https://www.googleapis.com/auth/calendar.events.readonly
Purpose: read Calendar events so Context One can derive metadata-only work signals such as timing, duration, recurrence and attachment presence. No Calendar write scope is requested.
Scopes intentionally not requested
gmail.metadata— held because it is a restricted scope.drive.metadata.readonly— held because it is a restricted scope.- Calendar write, ACL and settings scopes — not needed.
Callback architecture
The verified-domain callback forwards only OAuth code, state or error parameters to the Context One backend. The PHUONG GROUP callback proxy does not exchange, persist or log Google access or refresh tokens.
Data flow
- User enables Calendar metadata consent.
- Google redirects to the verified-domain callback.
- The callback forwards the authorization response to Context One's backend.
- Context One exchanges the code server-side using the same verified redirect URI.
- Tokens are encrypted with AES-256-GCM in a per-user vault.
- Calendar API calls use a field mask; raw event records are not retained as an archive.
- Derived work patterns are presented for user review.