Jira AI Bridge — Privacy Policy

1. Information We Collect

Data	How Collected	Purpose
Installation ID (UUID)	Generated automatically on first load, synced via chrome.storage.sync	Uniquely identifies your extension installation for subscription and trial management
Google email address	Extracted from your Google OAuth token when you sign in	Links your identity to your subscription entitlement
Subscription metadata	Created when you subscribe via Stripe	Tracks your plan status (trial, pro, expired), Stripe customer ID, subscription ID, and billing period dates
Jira board data (issue keys, summaries, assignees, statuses, comments)	Read from your Jira instance via your existing browser session	Displayed in the extension side panel and exported to AI services. Not sent to or stored on our servers.
Extension settings (field mappings, export toggles, UI preferences)	Saved by you in the extension	Persisted locally in chrome.storage.sync. Not sent to or stored on our servers.

2. How We Use Your Information

• Installation ID + email: used to manage your subscription, trial period, and entitlement status.
• Jira data: displayed locally in the extension panel. When you choose to export, issue text is sent directly from your browser to the AI service you selected (NotebookLM, ChatGPT, or Claude). Jira data is never sent to our servers.
• Error data: anonymous error reports (stack traces only) are sent to Sentry for debugging. All personally identifiable information is stripped before transmission.

3. Data Storage

Location	Data Stored	Retention
Your browser (chrome.storage.sync)	Installation ID, field mappings, export settings	Until you uninstall the extension
Your browser (in-memory)	Jira board data. Not sent to or stored on our servers.	Discarded when you close or navigate away from the tab
Our server (prod.jirabridgeai.com)	Email, installation ID, Stripe customer/subscription IDs, plan status, trial and billing period dates	Retained for the lifetime of your subscription; deleted upon request
Our server (audit log)	Terms/Privacy acceptance records: installation ID, version accepted, timestamp	Retained indefinitely for legal compliance

4. Third-Party Services

Service	Data Shared	Purpose
Stripe	Email, installation ID (sent via our backend)	Payment processing and subscription management
Sentry	Anonymous error reports (stack traces, extension version, environment tag)	Error tracking and debugging. User identity is removed before sending.
Google OAuth	Email address (via userinfo.email scope)	Identity verification for subscription entitlement
Atlassian Jira	None — uses your existing browser session. No Jira data is sent to or processed by our servers.	Reading board and issue data
Google NotebookLM	Jira issue text you choose to export — sent directly from your browser, not through our servers	Uploading text sources to your notebooks
OpenAI ChatGPT	Jira issue text you choose to export — sent directly from your browser, not through our servers	Uploading files to your ChatGPT projects
Anthropic Claude	Jira issue text you choose to export — sent directly from your browser, not through our servers	Uploading files to your Claude projects

Jira, NotebookLM, ChatGPT, and Claude are accessed using your own authenticated sessions. No data from these services is relayed through our backend.

5. What We Do NOT Collect

• Jira credentials, passwords, or session tokens
• AI service credentials or chat/conversation history
• Browsing history or activity outside of supported sites
• Payment card numbers or billing details (handled entirely by Stripe)
• Cookies (the extension does not set any cookies)

6. Your Rights

• Data deletion: contact jirabridgeai@gmail.com to request deletion of all server-side data associated with your account.
• Stop collection: uninstall the extension to immediately stop all data collection.
• Revoke Google access: remove the extension's OAuth permission in your Google Account settings.

7. Changes to This Policy

We may update this privacy policy from time to time. The "Last updated" date at the top of this page will be revised accordingly. Continued use of the extension after changes constitutes acceptance of the updated policy.