← Back to Tempus
Privacy Policy
Last updated: August 23, 2026
Tempus — AI Project Manager ("Tempus", "we", "our") is a Chrome browser extension that helps users track time and manage projects in Jira Cloud. This privacy policy explains what data Tempus accesses, how it is processed, and how it is protected.
Core principle: Tempus operates entirely within your browser. We do not operate backend servers that receive, store, or process your data. All data processing happens locally on your device.
1. Data We Access
Tempus accesses the following data through authorized APIs:
| Data type | Source | Purpose | Storage |
|---|
| Jira issues, worklogs, projects | Jira Cloud REST API | Display tasks, log time, generate reports | Browser only (chrome.storage.local) |
| Calendar events (read-only) | Google Calendar API | Display meetings alongside Jira worklogs to help users allocate time | In-memory only, never persisted |
| Tempo plans and allocations | Tempo REST API | Show capacity planning and compliance metrics | Browser cache with TTL |
2. How We Protect Sensitive Data
2.1 Google Calendar Data
Tempus uses the calendar.events.readonly scope exclusively. This means:
- Tempus can only read calendar events. It cannot create, modify, or delete events.
- Calendar data is processed entirely in your browser (client-side JavaScript). It is never transmitted to any external server operated by Tempus.
- Calendar events are held in memory only during the active browser session. They are not written to chrome.storage.local or any persistent storage.
- When you close the extension popup or browser tab, calendar data is discarded from memory.
- Calendar data is used solely to display your meetings alongside Jira worklogs, allowing you to see how your day splits between meetings and focused work.
2.2 Jira Data
Jira data (issues, worklogs, project metadata) is accessed via OAuth 2.0 with the user's explicit consent. This data is:
- Cached locally in chrome.storage.local (sandboxed per extension and Chrome profile — inaccessible to websites or other extensions).
- Never transmitted to servers operated by Tempus.
- Used exclusively for displaying project information, logging time, and generating analysis reports within the extension.
2.3 AI Analysis (Optional)
When users choose to send project data to an AI provider (Claude by Anthropic or Google Gemini) for analysis:
- This feature requires the user to provide their own API key (BYOK — Bring Your Own Key). Tempus does not provide or share API keys.
- Only aggregated project metrics are sent to the AI provider: issue keys, titles, status, logged hours, and team member names. Raw descriptions, comments, and attachments are never sent.
- The AI API call is made directly from the user's browser to the AI provider. Tempus has no server intermediary.
- Users are fully informed before any data is sent to an AI provider and must explicitly initiate the action.
2.4 Technical Protection Mechanisms
- Content Security Policy (CSP): The extension enforces
script-src 'self'; object-src 'self', preventing code injection.
- No inline scripts: All JavaScript executes from local files, not inline handlers.
- Input sanitization: All dynamic content is rendered through
escHtml() and escAttr() functions to prevent XSS attacks.
- OAuth 2.0 with PKCE: Jira authentication uses industry-standard OAuth 2.0 Authorization Code flow.
- Token storage: OAuth tokens are stored in chrome.storage.local (encrypted by Chrome's storage layer, inaccessible to web pages).
- Automatic token refresh: Access tokens are short-lived and refreshed automatically. Refresh tokens are stored securely in chrome.storage.local.
2.5 Google API Services Compliance
Tempus's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Limited Use: Tempus only uses Google Calendar data for the single purpose of displaying calendar events alongside Jira worklogs within the extension interface. This data is not used for advertising, market research, email campaigns, or any purpose unrelated to the extension's core functionality.
- No transfer to third parties: Google user data is never transferred, sold, or disclosed to any third party. When users optionally send project data to an AI provider, Google Calendar data is excluded from that transmission.
- No secondary use: Google user data is not used to build user profiles, train machine learning models, serve advertisements, or enrich other data sources.
- Security in transit and at rest: All communication with Google APIs occurs over HTTPS/TLS (encrypted in transit). Calendar data is held exclusively in volatile browser memory (not persisted to disk, databases, or chrome.storage.local), and is discarded when the extension popup closes. OAuth tokens stored in chrome.storage.local are encrypted by Chrome's storage layer and are inaccessible to web pages or other extensions.
- Minimal data access: Tempus requests only the
calendar.events.readonly scope — the narrowest scope that fulfills its functionality. It does not request write access, contact data, email content, or any other Google user data.
- User control: Users can revoke Tempus's access to their Google Calendar data at any time via Google Account Permissions. Upon revocation, the extension immediately loses access with no residual data retained.
3. Data We Do NOT Collect
- We do not collect analytics, telemetry, or usage statistics.
- We do not use cookies or tracking pixels.
- We do not serve advertisements.
- We do not sell, share, or transfer any user data to third parties.
- We do not operate backend servers that receive user data.
- We do not access email content (Gmail scope was deliberately removed).
4. Third-Party Services
Tempus communicates directly with the following services using credentials that the user explicitly provides:
| Service | Data exchanged | Authentication |
|---|
| Atlassian Jira Cloud | Issues, worklogs, projects | OAuth 2.0 (user consent) |
| Google Calendar | Calendar events (read-only) | Chrome Identity API (user consent) |
| Tempo (optional) | Plans, allocations, worklogs | API token (user-provided) |
| Anthropic / Google AI (optional) | Aggregated project metrics | API key (user-provided) |
| Atlassian Confluence (optional) | Published reports | Same OAuth as Jira |
| Supabase (license only) | License key, device ID | HTTPS |
Each of these services has its own privacy policy. Tempus does not control how these services process data once received.
5. License Validation
For Pro users, Tempus communicates with a Supabase edge function to validate license keys. The only data transmitted is:
- License key
- Device identifier (a randomly generated UUID, not linked to personal identity)
- Device type (e.g., "Windows", "macOS")
No Jira data, calendar data, or personal information is transmitted during license validation.
6. Data Retention and Deletion
- Local data: All extension data (cached issues, settings, tokens) is stored in chrome.storage.local. You can delete all data by uninstalling the extension or clearing extension data in Chrome settings.
- Calendar data: Never persisted. Exists only in browser memory during the active session.
- No server-side data: Since Tempus has no backend server, there is no server-side data to delete.
7. Your Rights
You can at any time:
- Revoke Google Calendar access: Go to Google Account Permissions and remove Tempus.
- Revoke Jira access: Go to your Atlassian account settings and remove the OAuth connection.
- Delete all local data: Uninstall the extension or go to Chrome → Extensions → Tempus → Clear data.
- Contact us: For any privacy questions, email hello@tempus-ai-pm.com.
8. Changes to This Policy
We may update this privacy policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of the extension after changes constitutes acceptance.
9. Contact
If you have questions about this privacy policy or how Tempus handles your data:
Email: hello@tempus-ai-pm.com
Website: www.tempus-ai-pm.com