Privacy policy

Consigliere Publisher · Last updated March 30, 2026

This policy describes how the Consigliere Publisher service (“the Service”) handles information. The Service is operated primarily for internal and authorized business use (hosting versioned HTML experiences and related assets). Some flows may be exposed more broadly when you publish content to a public URL.

What the Service is

The Service includes an admin web application, a backend API running on Google Cloud Run, Google Cloud Storage for uploaded files, and Firestore for metadata and access configuration. Static files may be delivered via Firebase Hosting. Sign-in uses Firebase Authentication with Google as the identity provider.

Information we process

Account and authentication. When you use “Sign in with Google,” we receive identifiers from Google that Firebase exposes to our application (including your email address) so we can verify your session and enforce access. Google’s processing is governed by Google’s terms and privacy policies.
Access control data (Firestore). We store configuration needed to grant access, such as email-domain rules, optional per-user overrides, brand labels, library folders, and records that describe artifacts (names, IDs, versions, who created or published them, and timestamps).
Content you upload (Google Cloud Storage). Uploaded HTML, ZIP archives, images, scripts, fonts, and other assets you choose to publish are stored under your project’s private bucket and served only through application-controlled URLs.
Public artifact URLs. When an artifact is published, anyone who knows or receives the public link may retrieve the published version of that content over HTTPS. Unpublished or non-current versions are not exposed through those public routes in the way the live site is.
Technical and security data. Our infrastructure providers log typical request, error, and operational data (for example in Cloud Run and Google Cloud) for reliability, abuse prevention, and support.

What we do not do in this codebase

The shipped admin application loads Firebase Authentication from Google’s CDN; it does not load Firebase Analytics in the client bundle. If your Google Cloud or Firebase project has other logging or analytics features enabled at the project level, those may apply under Google’s policies.

How we use information

We use the data above to:

Authenticate administrators and enforce brand access rules;
Store, version, publish, and delete artifacts you manage;
Operate, secure, and improve the Service;
Comply with law and respond to legitimate requests where required.

Sharing

We rely on Google Cloud and Firebase services to run the Service; data is processed on Google’s infrastructure under your or our administrative settings. We do not sell your personal information. We may disclose information if required by law or to protect rights and security.

Retention

We retain data for as long as needed to operate the Service and as configured in your environment. Deleting an artifact through the admin API removes associated stored files and metadata as implemented in the application. Operational logs are retained according to Google Cloud settings.

Security

Admin API routes require a valid signed-in session. The content bucket is private; public access is through controlled HTTP routes for published artifacts. Use strong Google account security and limit admin_domains / admin_users in Firestore to trusted parties.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, or restrict certain data. For requests about data processed through Google Sign-In, you may also use Google’s account tools. To exercise rights or ask questions about this deployment, contact the team responsible for the Service (see below).

Changes

We may update this policy from time to time. The “Last updated” date reflects the latest revision. Material changes may be communicated through your normal internal channels.

Contact

For privacy questions about this Service, contact the support email shown on the Google OAuth consent screen for this application, or your internal administrator.