Privacy Policy for Files of Ba Sing Se

Files of Ba Sing Se ("we", "our", or "the Application") is an open-source, client-side web application designed to allow creative media professionals, video editors, and engineering teams to browse, inspect, and stream digital media assets directly from Google Cloud Storage (GCS) to their local workstations.

We are deeply committed to protecting your privacy, personal information, and cloud security. This Privacy Policy details how the Application interacts with Google APIs, what information is accessed, how that information is handled, and the strict technical safeguards in place.

1. Architectural Foundation: Zero-Backend Processing

Files of Ba Sing Se is built on a Zero-Backend Architecture:

• Direct Client-to-Google Communication: All interactions with Google services occur directly between your web browser runtime and Google's official API endpoints (storage.googleapis.com, cloudresourcemanager.googleapis.com, cloudbilling.googleapis.com, serviceusage.googleapis.com, and accounts.google.com).
• Zero Intermediary Servers: We do not operate an intermediary application server, proxy server, or custom backend.
• Zero Telemetry / Zero Tracking: The Application does not employ third-party analytics trackers, tracking cookies, advertising beacons, or telemetry logging services (including Firebase Analytics, Google Analytics, or external monitoring networks).

2. Information Accessed & Scopes of Authorization

When you sign in using Google Identity Services (OAuth 2.0), the Application requests access to specific permissions according to the Principle of Least Privilege:

A. Base Non-Sensitive Permissions (Default Sign-In)

• User Identity (openid, .../auth/userinfo.email, .../auth/userinfo.profile): Retrieves your name, email address, and avatar image to display your active session identity in the application header and verify authorized bucket access.
• Google Cloud Storage Read-Only Access (https://www.googleapis.com/auth/devstorage.read_only): Enables the Application to list GCS bucket folders, inspect object technical metadata (sizes, Content-Types, CRC32c checksums), and stream media file contents directly to your local workstation.

B. Optional Step-Up Administrative Permissions (On-Demand)

• Google Cloud Platform Access (https://www.googleapis.com/auth/cloud-platform): Requested strictly on-demand only if you explicitly choose to use the automated GCP project discovery, 1-click project auto-provisioning, or billing account linkage verification features. If you manually enter your existing GCP Project ID, this permission is never requested.

3. Client-Side Data Storage, Session Persistence & Security Boundaries

• Client-Side Session Persistence: Active OAuth 2.0 access tokens, granted scopes, and user session profile details are stored in your browser's local web storage (localStorage under basingse-app-session and sessionStorage under basingse-tab-session) to maintain session continuity across page reloads and enable real-time cross-tab synchronization.
• Zero Third-Party Credential Transfer: All credentials and session data remain strictly within your local browser environment. We operate no backend servers and never transmit your tokens, keys, or credentials to third-party endpoints.
• Persistent Workspace Preferences: Non-sensitive operational preferences (such as your chosen UI theme, saved bucket name, and project ID label) are saved in localStorage (basingse-media-client-prefs) to preserve your workspace configuration.
• Storage Boundary Security & Auditing: The Application actively enforces storage boundary constraints, prohibiting the storage of private keys, client secrets, or raw service account credentials in web storage.
• Complete Session Purge & Revocation: Clicking "Sign Out" or "Disconnect Session" immediately wipes all session entries from localStorage and sessionStorage, flushes runtime state, and invokes Google's OAuth 2.0 token revocation endpoint.

4. Third-Party Data Sharing & Disclosure

We do not sell, rent, monetize, trade, or transfer your personal data, Google credentials, or storage data to any third party. Your files and metadata are never uploaded to, cached on, or processed by any third-party infrastructure.

5. Google API Services User Data Policy Compliance (Limited Use)

Specifically:

• Human agents do not read your storage data or profile information.
• Information retrieved via Google APIs is used solely to provide user-facing media browsing and downloading features within your own browser.
• Data obtained through Google APIs is not used for serving advertisements or training machine learning models.

6. User Rights, Session Management & Revocation of Access

You maintain complete control over your Google credentials, session preferences, and authorizations:

• In-App Sign Out & Session Purge: Clicking "Sign Out" or "Disconnect Session" in the Application header or GCP Configuration Center instantly invokes Google's OAuth 2.0 token revocation endpoint (https://accounts.google.com/o/oauth2/revoke), flushes runtime state, and clears all session data and configuration hints from localStorage and sessionStorage.
• Session Continuity Controls: You can enable, disable, or adjust automatic session restoration settings at any time within the GCP Configuration Center.
• Google Account Permissions Dashboard: You can review and revoke authorization at any time directly through your Google Account Permissions.

7. Security Safeguards

• Content Security Policy (CSP): Strict HTTP/meta headers restrict outbound connections exclusively to authenticated Google Cloud endpoints.
• Cryptographic Checksum Verification: Every streamed file is validated against hardware-accelerated Castagnoli CRC32c checksums to prevent bit rot and data tampering.
• Automated Boundary Auditing: In-browser runtime scanners continuously verify storage hygiene and ensure no private keys or tracking beacons are present.

8. Contact & Inquiries

For technical questions, privacy inquiries, or security reports, please contact the maintainers:

• Maintainer: Max Paulson
• Project Repository: https://github.com/maxpaulson/files-of-ba-sing-se
• Email: privacy@basingse.dev