Analytics

What we track

Event	Properties	Why
app_started	—	Measures how many people actively use Glimpse.
app_exited	uptime, transcription_count	Shows session length and overall usage volume.
transcription_completed	mode, model, llm_cleanup_used	Reveals which models and features people actually use.
transcription_failed	failure_stage, reason	Helps diagnose and fix failures faster.
model_downloaded	model_name	Shows which models are most popular so support can be prioritized.
onboarding_completed	—	Measures how many users complete setup.

Each event is associated with a random install ID — not your name, device, or IP address. All data is stored in the EU via PostHog EU.

What we never track

• Transcripts or audio
• API keys or prompts
• Any personally identifiable information

Opting out

Analytics can be disabled at any time in Settings → Advanced. The change takes effect after restarting Glimpse.

Why analytics matter

Building Glimpse means constantly making decisions: what to build next, what to improve, and — just as importantly — what to cut. Analytics help make those decisions based on what people actually use.

A good example: Glimpse once supported Moonshine models on the transcribe-rs backend. After about a month, the data showed they'd been used exactly once — by me (LegendarySpy). That's the kind of signal that saves everyone time. Without it, features can linger long past their expiration date.

Privacy is important — for many people, it's the main reason they use Glimpse. So a final reassurance: when analytics are enabled, they are fully anonymous and GDPR compliant. The data is only accessible to the Glimpse team and is used strictly to improve the app. Your data will never be sold. This applies to cloud mode as well.

your data is yours, not ours to share.