Privacy

Counterpose is designed to collect the minimum operational data needed to run and improve the public beta.

Analytics never includes your decision text. Questions, context, evidence, transcripts, provider URLs, API keys, Google email/name, raw IP addresses, and raw user-agent strings are excluded from analytics events.

First-party analytics

Counterpose records a small allowlist of product events such as page views, mode selection, sign-in outcomes, debate starts/completions, failures, and result exports. Safe dimensions are limited to hosted/BYOK mode, a coarse device category, bounded queue or generation duration, remaining hosted allowance, and a normalized error class.

Signed-in events use Counterpose’s random internal user ID—not your Google identity. Anonymous events use only a hash of a random, HttpOnly analytics cookie that expires after 24 hours. Counterpose does not fingerprint visitors.

Analytics is stored in the operator’s Google Cloud project. Access is restricted by Google Cloud IAM. Individual analytics logs use a 30-day retention period; aggregate log-based metric points used by the dashboard are retained for six weeks.

Google sign-in

Google supplies an ID token used once to verify your identity. Counterpose stores Google’s stable account identifier, email address, and display name for account administration, then issues its own revocable session. It does not request access to Google Drive, Gmail, or other Google APIs.

Debates and BYOK credentials

Signed-in debates are attached to your private Counterpose account. Anonymous BYOK debates are protected by a high-entropy browser-session capability. BYOK API keys are kept only for the active request/job and are never written to debate storage, analytics, or browser local storage.

Your controls

The account panel lets you log out, revoke every Counterpose session, or delete your account and its hosted debates. Analytics expires through the logging retention policy and is not used for advertising or sold to third parties.

Changes

This notice describes the public beta as of 12 August 2026. Material changes to collection or retention will be reflected here before they are enabled.