Privacy & data handling
Where your data is processed, what leaves the browser, and how BYOK AI keeps your prompts private.
Core principle: Tempus is a local-first Chrome extension. Your Jira, Calendar and project data is processed in your browser. There is no central Tempus server that receives or stores it.
What stays in your browser
Jira issues, worklogs, calendar events and CRM fields are fetched directly from those services using your own authenticated session and processed locally. OAuth access tokens live in ephemeral session storage; refresh tokens are restricted to trusted extension contexts.
What leaves the browser, and when
| Destination | Data | When |
|---|---|---|
| Claude / Gemini (your key) | Selected project metrics for analysis | Only when you run an AI feature |
| Supabase | License key + anonymized device ID | License validation |
| Stripe | Payment details (Tempus never sees card data) | Checkout only |
BYOK: your AI, your key
AI analysis is bring-your-own-key. You connect your own Claude or Gemini API key and Tempus talks to that provider directly from your browser, so Tempus never sees your prompts or the responses.
For the full architecture, OAuth scopes, token storage and vulnerability reporting, see the Security Center.