IssueLinker only reads HubSpot ticket data (subject, description, notes, pipeline stage) for tickets your team explicitly links or creates a Jira issue for via the IssueLinker card. We do not crawl, index, or store data from other tickets.

For linked tickets, IssueLinker syncs the following in real time via HubSpot and Jira webhooks:

• Ticket subject and description → Jira issue (one-time, on creation)

• HubSpot notes → Jira comments (whenever a new note is added)

• Jira comments → HubSpot notes (whenever a new comment is added)

• Jira issue status → HubSpot "Jira Issue Status" custom property (whenever the status changes)

• HubSpot ticket closed → Jira issue transitioned to Done (whenever the pipeline stage changes to closed)

What IssueLinker stores: an installation record per HubSpot portal (portal ID, OAuth tokens, Jira site ID), and a link record per ticket↔issue pair (HubSpot ticket ID and Jira issue key). We do not store the contents of

tickets, issues, comments, or notes. Those live in HubSpot and Jira and are read on demand.

Data is stored in an encrypted Postgres database (Neon, US region). Access is restricted to IssueLinker's serverless functions running on Vercel. We never share, sell, or repurpose your data. On uninstall, all installation and link records for your portal are deleted within 30 days.