Security statement
This security statement applies to the Cloud version of the HubSpot CRM Integration
Last updated
Was this helpful?
This security statement applies to the Cloud version of the HubSpot CRM Integration
Last updated
Was this helpful?
We are committed to improving our security posture. That’s why we created this page to answer basic questions about security in the HubSpot Integration app.
Architecture
is built on the platform. The app connects to Jira using . It’s written in React and TypeScript.
What does the data flow look like?
TBD
What customer data does the app process?
We process accountIds, email addresses, display name.
What data does the app store?
The app stores connection credentials to HubSpot, configuration settings, and custom field values.
Where are the data stored?
All data are stored on the Atlassian infrastructure. The app data is stored via .
What permission does the app require?
This app requires four permissions:
View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
View the profile details for the currently logged-in user.
Read and write to app storage service
Does the app encode all data in transit and at rest?
Yes.
Does the app support data residency?
Does the app have a data retention policy?
Does the app have a data backup policy?
Yes, thanks to using the Atlassian Forge platform. Here is the official announcement from Atlassian:
Yes. Appsvio and Atlassian will delete all End User Personal Data (including copies) upon written request. More information is available in .
Yes. More information is available in
Useful links and more information
If you have any questions about the security, e-mail