Data Privacy & Permissions
How Village Labs ensures data is handled and shared appropriately.
Overview
Village Labs is guided by three overarching policies relating to Data Privacy & Permissions:
1. Private data stays private
Village Labs respects the privacy of employees within an organization. By default, Village Labs will not process the contents of private conversations, such as 1:1 Slack messages, private documents that are not shared with all users within an organization.
Our default settings only process data in reports that is generally shared with your organization.
2. We respect primary data source permissions
By default, if a user in your organization does not have access to data in the source tool, they will not get access to that data in Village Labs. Please read the table below for more detail, as there is some nuance related to data in tools that is considered 'shareable with the organization' even though not all members of your organization may have access to that tool (eg. Jira or HubSpot).
The following table breaks down what information is processed by Village Labs reports (and therefore shared with those that have access to the Village Labs platform) on a Connector by Connector basis.
| Connector | Data Processed by Reports | Data Excluded |
|---|
| Default: Public Channels only. We can turn off this default if required so that only channels where Village Labs is manually added will be connected. Private Channels can be manually added (assuming their content is non-sensitive).
| Default: Private Channels (unless manually added).
|
| Documents, Sheets, Slides that have been shared with your organization (General Access: Your Organization, Anyone in this group with the link can view/comment/edit). Documents, Sheets, Slides that have been shared with 'Anyone with the link'
| Documents, Sheets, Slides that are either Restricted (shared only with you, or shared only with a subset of users.
|
| Only Pages (or nested Pages under these pages) that have had the Village Connector added to them. Note that if you add the Village Connector to a top-level page, Village will be connected to all nested Pages. The exception is if the Page is nested but set to 'Invite only'. These pages show as 'Restricted'.
| Pages that do not have the Village Connector added to them. 'Restricted' pages that are set to 'Invite only'
|
| Items that are set to 'Main' Privacy (Visible to everyone in your account) for the Workspace that Village has been granted access to.
| Items set to Private or Shareable with a subset of users.
|
| Spaces and content nested within those Spaces that are set to be shared with the Workspace that Village has been granted access to, unless those Spaces or underlying content have been set to Private.
| Spaces or Content that are not shared with your Workspace. Content that is set to Private.
|
| Data in the project that has been connected to Village Labs.
| |
| Data in the Repositories that have been connected to Village Labs.
| Data in the Repositories that have not been connected to Village Labs.
|
| Data in the Repositories that have been connected to Village Labs.
| Data in the Repositories that have not been connected to Village Labs.
|
| This depends on the Scopes that you granted the Village App permissions to. Default Scopes generally mean that data relating to Deal management (including Deal status, connected Contacts, Deal Notes, and any emails that are associated with the Deal through HubSpot's email integration will be accessible. The default Scopes are:
CRM
Settings
Standard
| HubSpot has many other read and write Scopes that Village Labs does not have access to.
|
| Data in the Workspace that you connected Village Labs to.
| Data in any other Workspaces that you did not connect to Village Labs.
|
3. Required business purposes only
We only allow Village Labs user access for required business purposes.
In alignment with Village Labs’s primary Data Access Policy, no member of the Village Labs team has access to client data of any type other than for clear business needs. For example, software developers working on external data pipelines will require some access to client data to deliver the work product to the customer at setup and during maintenance.
