Privacy Policy (隱私權政策)
Effective Date: November 17, 2026 · Applies to GCP NetDoctor
This Privacy Policy explains how GCP NetDoctor (accessible at https://net-doctor.scotthsieh.me)
accesses, uses, handles, and protects Google user data and Google Cloud telemetry when you sign in with Google.
1. Data Accessed via Google OAuth 2.0 (存取之資料與權限範圍)
When you click Sign in with Google, GCP NetDoctor requests the following OAuth 2.0 scopes:
openid,email,profile: Used solely to display your signed-in account identity (email, display name, and profile avatar) in the application header and isolate your session cache.https://www.googleapis.com/auth/cloud-platformandhttps://www.googleapis.com/auth/logging.read: Used exclusively for read-only inspection of Google Cloud organizations, projects, VPC networks, routes, firewall policies, load balancers, and Cloud Logging entries in the specific projects you select. Note that many Google Cloud read APIs (such as GKE, Cloud Run, Cloud SQL, Cloud Asset Inventory, and Certificate Manager) require thecloud-platformOAuth scope; GCP NetDoctor enforces strict read-only behavior in software and never issues mutating API calls.
2. How We Use Your Information (資料使用方式)
- User-Initiated Read-Only Diagnostics Only: All Google Cloud API queries execute solely in response to your interactive actions (selecting an organization/project, running a path diagnosis, viewing Load Balancer topology, or opening the Cutover Monitor).
- Your Own IAM Boundary: The application runs with zero privileged Service Account viewer roles; you can view only the Google Cloud resources that your own Google account is authorized to view under Google Cloud IAM.
- No Resource Modification: GCP NetDoctor never creates, updates, or deletes any Google Cloud infrastructure resource.
3. Data Storage, Ephemeral Memory & Retention (資料儲存與留存機制)
- Zero Persistent Database: GCP NetDoctor does not store your OAuth access tokens, refresh tokens, GCP resource configurations, or Cloud Logging entries in any database or persistent disk storage.
- Ephemeral In-Memory Session: OAuth credentials are held strictly in volatile server memory associated with an
HttpOnly,SameSite=Lax,Securesession cookie (maximum lifetime 12 hours) and short-lived in-memory caches partitioned per user credential. - Immediate Purge on Sign-Out: Clicking Sign Out immediately deletes your in-memory session, clears your browser session cookie, and sends a token revocation request to Google's OAuth revocation endpoint (
https://oauth2.googleapis.com/revoke).
4. Data Sharing & Third-Party Disclosure (第三方資料分享政策)
- We never sell, rent, license, or share your Google user profile or Google Cloud data with third parties or advertisers.
- We never use Google user data or Google Cloud telemetry to train generalized artificial intelligence or machine learning models.
- When optional public IP ownership enrichment is invoked on a public IP address, only that public IP address (never private/RFC 1918 addresses or user identity data) is queried against public RDAP/ASN registries.
- If you explicitly start a Hosted Read-Only Cutover Presentation Session and share the generated viewer link with colleagues, only the cutover snapshot state you choose to broadcast in that temporary in-memory session is visible to holders of your session token until you end the session.
5. Google API Services User Data Policy (Limited Use Disclosure)
6. Revoking Access & Contact (撤銷授權與聯絡方式)
You may revoke GCP NetDoctor's access to your Google account at any time by clicking Auth Status → Sign Out in the application header, or directly from your Google Account permissions page at https://myaccount.google.com/permissions.
For privacy questions or support inquiries regarding this deployment, please contact the administrator email listed on the Google OAuth consent screen.