| Stores your data outside Atlassian? | No | No: tokens, sync progress and its message ledger are in Forge storage. The add-ins keep a pairing token in your own mail account, and the Gmail add-on caches the card it shows for up to 10 minutes |
| Processes your data outside Atlassian or your browser? | No | Yes: mail and calendars are read from your own Google Workspace (or, in Gambit Mail Sync Beta, Microsoft 365), and the Gmail add-on runs on Google Apps Script. Data: names, email addresses, the record fields shown in the sidebar and message content |
| Logs your data? | Yes: Atlassian account IDs, the cloud ID, site host and record keys, in Atlassian's Forge logs only; never names, email addresses, subjects, bodies, file names, field values, prompts or AI output | Same |
| Logs your data outside Atlassian? | No: app logs stay in Atlassian's Forge logs. Error reports go to Sentry with the error type, an error message stripped of names, addresses and content, stack frames, a scrambled site ID, the import run ID and scrambled row references, never a person, name, email address or record content | Same |
| Shares logs with third parties? | No logs that include your data: Sentry receives error reports with the error type, an error message stripped of names, addresses and content, stack frames, a scrambled site ID, the import run ID and scrambled row references, never record content; admins switch them off in Atlassian's admin controls | Same |
| Exposes remote APIs? | Yes: one web endpoint with fixed replies that accepts signed messages from Gambit Mail Sync only, authenticated with a per-site shared secret: capture status and settings, blocked addresses, "keep this thread private" requests, threads logged from the Gmail sidebar (or, in Gambit Beta, the Outlook sidebar), company logos, connection checks and activity-history notes. The two apps pair through Jira, not through this endpoint | Yes: one web endpoint for the Gmail add-on and, in Gambit Mail Sync Beta, the Outlook add-in, authenticated by per-user pairing tokens, and the sign-in return page for connecting mailboxes |
| Shares your data with third parties? | No: AI runs on Atlassian-hosted Forge LLM. Usage analytics (PostHog) carry pseudonymous IDs and no record content; error reports (Sentry) carry the error type, a scrubbed error message, stack frames, a scrambled site ID, the import run ID and scrambled row references, never record content | Google (and, for Gambit Mail Sync Beta, Microsoft), acting for you; logo.dev receives a company's web domain only; PostHog and Sentry as for Gambit. From January 2027, only when your admin turns each on: Salesforce, HubSpot and Pipedrive imports, Apollo and People Data Labs enrichment on your own key, the European Central Bank's exchange rates and SAM.gov. In a later release, only when your admin connects your own account or key: Slack and Microsoft Teams alerts, Zapier and Make automations, Brave Search web search, and Anthropic, OpenAI or Microsoft Azure AI (Azure OpenAI or Azure AI Foundry) AI on your own key |
| Data residency | Yes: the app stores your data only in Atlassian products and services that support data residency | No: what it keeps in Forge storage (its mailbox connections and tokens, sync progress, the capture ledger and the messages and files waiting to be written) and the captured email and meetings in your Jira work items follow your site's region, but Mail Sync isn't pinned to a location, because it reads mail and calendars through Google's services (and, for Gambit Mail Sync Beta, Microsoft's) |
| Keeps data after uninstall? | Your records and captured email with its files stay in Jira as work items, with their Jira fields, comments, attachments and properties. Gambit's own fields (Account, People, Revenue impact, Health) keep their values in each work item's properties, and Jira restores the fields if you reinstall within 30 days. The app's Forge storage is deleted by Atlassian after its recovery period; Atlassian can reconnect it to a reinstall requested within 21 days | When you uninstall Gambit Mail Sync, capture stops and Mail Sync revokes the Google sign-in tokens of people who connected their own Google mailbox, most recently used first. Atlassian deletes the app's Forge-hosted data 28 days after uninstall; a reinstall requested within 21 days can be relinked to that data. Reconnect mailboxes after a reinstall |
| Custom retention on request? | Yes: on Advanced, admins choose how long activity history is kept | No |
| Privacy-enhancing technologies? | Yes: payment card numbers and US Social Security numbers are masked before storage wherever Gambit writes text (imports, Gambit's forms and AI output; not attached files, file names, images or text typed directly in Jira's own screens); every screen shows a record only to people Jira lets see it | Yes: card and Social Security numbers in captured and logged email and calendar events are masked in place before they are written (attached files, file names and images are not scanned); each person's never-log list and the admin's block lists, by address or domain, keep every message with a listed person out; Private threads (Jira Standard and above); pseudonymous analytics IDs, and one-way hashes for the capture ledger, pairing tokens and erased people |
| Data controller under GDPR? | No, processor | No, processor |
| Trust centre | https://gambit.humanr.ai/trust | Same |
Gambit