Where is Join hosted?
What information does Join collect?
What is Join’s policy on cyber incident awareness?
Join runs an internal cybersecurity employee awareness program led by the Join CISO. Risk and vulnerability assessments are conducted with every incremental code review. In the event of a cyber incident, Join will notify our customers within five (5) business days or less upon being made aware of a cyber incident.
How does Join handle access control?
Join uses a third-party authentication provider (Auth0) for access control and enforcing pre-authentication risk checks. The system identifies users and data access is limited by a Role-Based Access Control layer. Join retains logs for end-user authentication for two (2) days for user login and seven (7) days for user actions ensuring the actions of individual users can be uniquely traced.
How does Join protect data at rest or in transit?
Join encrypts all data at rest and utilizes TLS for all data-center to client-side communications.
Does Join support Single Sign-on?
Join currently offers Single Sign-on (SSO) for the following identity providers or protocols:
- Microsoft Azure AD
- Google Workspace
If you want to get SSO set up for your organization, read our SSO Setup Guide.
Is Join GDPR compliant?
What is Join's data backup strategy?
The Join data storage strategy was designed for a high level of availability and substantial disaster protection. There are two types of data in Join: relational data which is stored in a SQL database (most data) and blob storage (uploaded images, etc.) are stored in AWS Storage Service (S3). The SQL database is backed up daily, and the restoration process is exercised at least weekly to ensure that it functions properly. Join retains these backups for seven (7) days. S3 provides replication across multiple data centers to ensure availability in case of failure or data center loss.
What domains does Join require access to in order to function correctly?
Does your organization have networking rules in place to block access or requests from certain websites? If so, we recommend working with your company's IT department to adjust your network's allowed list to ensure that Join functions correctly from within your environment.
Join recommends both Core Functionality and Extended Analytics domains be added to your allowed list. However, if your environment blocks access to Core Functionality domains then Join may not function as expected for your users.
Note: Domains marked with an asterisk (*) do not require you to add each sub-domain.
How do I ensure my team receives Join's communications?