Snapshot 46224
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Skip to main content
StopWatch for HubSpot has been Certified by HubSpot since July 2024. According to HubSpot, “app certification involves the HubSpot Ecosystem Quality team reviewing and confirming that your listed app meets these requirements for security, privacy, reliability, performance, usability, accessibility, and value”.
This page provides an overview of our approach to data security, highlights the permissions that are required by our apps and demonstrates our apps’ data flows (including examples). If you have any questions about our approach to data security, please feel free to submit a support request.
Dependent Systems
Dependent Systems
All of our apps currently rely on just 2 reputable, security-conscious systems:
HubSpot
HubSpot Security, Privacy and Control
Google Cloud Platform (GCP)
Google security overview
In short, when you interact with our apps, secure HTTP requests are initiated from HubSpot to our app backend systems (hosted on GCP). Our systems then process these requests and respond accordingly.
Top of section
Top of page
System Access
System Access
Only Thread Integrations has access to systems relied on by our apps
Access is never provisioned to any 3rd parties
2-factor authentication (2FA) is always enabled and enforced on all systems relied on by our apps
We use an industry-standard password manager to store all passwords, keys and any other sensitive information
All passwords are secure and unique
Top of section
Top of page
App Permissions
App Permissions
When you install our apps, you are required to grant the given app permission to access certain data in your HubSpot Portal. We only request app permission scopes that our apps absolutely need in order to provide our features and services.
StopWatch for HubSpot
Utilities for HubSpot
Below are the required permission scopes requested by StopWatch for HubSpot at the time of install.
Below are the required permission scopes requested by Utilities for HubSpot at the time of install.
Top of section
Top of page
Data Flows & Storage
Data Flows & Storage
We store minimal data on our systems, the great majority of which is retained for a maximum of 30 days (for issue identification and resolution purposes). Our HubSpot app design philosophy ensures as much data as possible is stored directly in HubSpot.
App Cards
Example HubSpot Request
Example Request Body
{
"crm": {
"objectId": 1234567890, // crm record id
"objectTypeId": "0-1" // crm object type id
},
"location": "crm.record.sidebar", // location of app card
"extension": {
"appId": 123456, // hubspot app id
"appName": "StopWatch", // hubspot app name
"cardTitle": "StopWatch" // app card title
},
"user": {
"id": 987654, // hubspot user id (person accessing the app card)
"emails": [
"jane.doe@example.com.au", // hubspot user email(s)
"jane.doe+example@example.com.au"
],
"email": "jane.doe@example.com.au", // primary hubspot user email
"firstName": "Jane", // hubspot user first name
"lastName": "Doe", // hubspot user last name
"roles": [],
"teams": [],
"locale": "en-au" // hubspot user language setting
},
"portal": {
"id": 1122334455, // hubspot portal id (aka hubid)
"timezone": "Australia/Brisbane", // hubspot portal timezone setting
"dataHostingLocation": "eu1" // hubspot portal hosting location
}
}
Custom Workflow Actions
Example HubSpot Request
Example Request Body
{
"callbackId": "ap-1122334455-1234567890-2-0",
"origin": {
"portalId": 1122334455,
"userId": null,
"actionDefinitionId": 999999,
"actionDefinitionVersion": 1,
"actionExecutionIndexIdentifier": {
"enrollmentId": 1234567890,
"actionExecutionIndex": 1
},
"extensionDefinitionId": 999999,
"extensionDefinitionVersionId": 1
},
"context": {
"workflowId": 987654321,
"actionId": 2,
"actionExecutionIndexIdentifier": {
"enrollmentId": 1234567890,
"actionExecutionIndex": 1
},
"source": "WORKFLOWS"
},
"object": {
"objectId": 998877665544,
"propertyValues": {
"hubspot_owner_id": {
"name": "hubspot_owner_id",
"value": "987654",
"timestamp": 1739059581911,
"sourceId": "userId:987654",
"source": "CRM_UI",
"sourceVid": [],
"requestId": "123abc-123abc-123abc-123abc-123abc",
"updatedByUserId": 987654,
"useTimestampAsPersistenceTimestamp": true
}
},
"properties": {
"hubspot_owner_id": "987654"
},
"objectType": "TICKET"
},
"fields": {
"workflowTimeLog": "FALSE",
"timeLogOwner": "987654"
},
"inputFields": {
"workflowTimeLog": "FALSE",
"timeLogOwner": "987654"
},
"typedInputs": {
"workflowTimeLog": {
"value": "FALSE",
"type": "STRING"
},
"timeLogOwner": {
"value": "987654",
"type": "STRING"
}
}
}
Webhooks
Example HubSpot Request
Example Request Body
{
"appId": "123456", // hubspot app id
"attemptNumber": "1", // webhook request number
"changeSource": "CRM_UI", // data change source
"eventId": "1234567890", // webhook event id
"isSensitive": false, // whether the request relates to a sensitive property
"objectId": "9876543210", // hubspot crm record id
"objectTypeId": "0-1", // hubspot crm object type id
"occurredAt": "1761054076119", // timestamp
"portalId": "1122334455", // hubspot portal id
"propertyName": "example_property", // hubspot property name
"propertyValue": "example property value", // hubspot property value
"sourceId": "userId:987654", // webhook source id
"subscriptionId": "332211", // webhook subscription id
"subscriptionType": "object.propertyChange" // webhook subscription type
}
StopWatch API
See StopWatch API documentation for more information
Top of section
Top of page
Top of page