TickerCue
Skip to content
Prepared-video beta · Frozen editorial facts · No live market feed · General information, not investment advice

Privacy

Privacy by restraint.

This draft describes the information currently handled by the public website and invited TickerCue app testing. It is intentionally narrower than a future full-product notice.

Pre-launch policy draft

This page documents the current product behavior, but it is not a final legal notice. Operator identity, launch geography, contact details and specialist legal review are still required before public beta.

Public website

Vercel hosts the website and can process technical request information needed to deliver and secure it. TickerCue has integrated Vercel Web Analytics for aggregate page-use measurement and Vercel Speed Insights for anonymous real-user performance measurement. Vercel states that these services do not associate their analytics or performance records with an identifiable visitor or reconstruct a browsing session.

Vercel Web Analytics privacy and compliance (opens in a new tab) · Vercel Speed Insights privacy and compliance (opens in a new tab)

On the canonical production website, TickerCue also uses PostHog for anonymous pageview and limited story-use measurement: story impressions, video completion milestones, panel opens, explicit story-action controls and outbound source opens. The configuration disables click and form autocapture, session replay, error and performance capture, surveys, person profiles and durable browser storage. Pageview and referrer URLs are reduced to their origin and path. Only constrained source, medium, campaign, content and term UTM labels are retained for attribution; advertising click identifiers and raw browser fingerprints are excluded. The same-origin relay removes TickerCue cookies, authorization headers and the browser's HTTP referrer header before forwarding a request.

PostHog privacy information (opens in a new tab)

Protected pages

Partner and internal-preview routes use a strictly necessary HTTP-only session cookie after successful access-code verification. The cookie is used to maintain access, not for advertising.

Invited app accounts

Sign in with Apple can provide an account identifier and, when Apple supplies them, a name and email address. Selected interests, story feedback and product interactions can be associated with that account. Supabase provides authentication and protected database services for the invited app beta.

Supabase Auth documentation (opens in a new tab)

Conversations and microphone audio

Public Live AI is disabled. The app is designed with saved conversation text off by default. If that feature is enabled later and a user deliberately turns saving on, encrypted question-and-answer text can be stored for that account. TickerCue's own database is designed not to persist raw microphone audio.

Retention and choices

Saved server-side question-and-answer records are configured with a 90-day expiry and may be cleared sooner. The app includes controls to clear saved text and request account deletion. Retention periods for support, security and analytics records still require final publication by data category.

Advertising and tracking

TickerCue does not currently implement advertising trackers or a personal-data sale mechanism. The current iOS privacy manifest declares no tracking. This wording still requires jurisdiction-specific legal review.

Security

Current controls include protected routes, account-level authorization, encrypted saved Q&A text, private app media storage and short-lived media links. No system can promise absolute security.