Addigy Third-Party Integrations


Data Privacy is a very important part of the Addigy Platform and we realize that some partners rely on third-party integrations. 

We have encouraged several of these integration partners and vendors to ensure GDPR compliance.

When enabled Addigy Third-Party Integrations can retrieve/send device data from the Addigy API. 

The following is a list of Addigy Integrations built by Addigy and what type of known data is collected.

Please review the Addigy Privacy Policy, Terms of Service, and any third-party corresponding legal documents prior to enabling a third-party integration and deploying it to your devices/configuration.

We have consolidated a list of our integration partners, the data that could be collected/retrieved, and currently available information about our integrators and partners concerning privacy and data security.


Addigy Multi-Factor Authentication (MFA)

Addigy developed its own internal Multi-Factor Authentication tool, which relies on data already provided in the Addigy Platform.

Data transmitted revolves around the User ID and the Phone Number tied to a User ID in order to validate a secure login to the platform.

Phone number, Account ID, and Tokens are the only requirements for this functionality.

Note: When validating Multi-Factor Authentication a text message or phone call may be received to the phone number provided.

This service relies on a third-party provider which is listed in Addigy's DPA.


Addigy Remote Control 

Addigy uses Pilixo's Remote Control 'Remo' to provide HTML5 based remote desktop access to Addigy Agents.

This requires data such as the OS Version, IP Address, Agent ID, and Device Name.

https://www.pilixo.com/legal/index.htm


ConnectWise Ticket Integration 

Addigy can integrate with ConnectWise Manage Ticketing platform to generate tickets.

Data Transmitted consists of Organization ID, Agent ID, Account ID, Platform, Status, Policy ID, Last Updated, Configuration Type ID, OS Type, OS Info, CPU, RAM, MAC Address, Serial Number, Device Name, Last Login Name. Configuration requires a ConnectWise API Key, Username, and Account URL.

https://www.connectwise.com/legal


ConnectWise Control (ScreenConnect)

The ConnectWise Control integration requires the ScreenConnectControlClient package installed on a device to leverage the remote control functionality.

Addigy does not explicitly send any information over to ConnectWise about the device information, aside from the application that is installed via Addigy.

For more information as to what the ConnectWise ScreenConnect ControlClient does - please refer to the following link.

https://www.connectwise.com/legal


AutoTask 

Addigy can integrate with AutoTask Ticketing platform to generate tickets.

Data Transmitted consists of Organization ID, Agent ID, Serial Number, Device Name, Device Model Name, TimeZone, Processor Type, Processor Speed, Hardware Model, macOS X version, Total Memory Ticket ID, Platform ID, Organization ID, Agent Name, Ticket Name, Severity Level, Ticket Subject, Ticket Description, Status, Creation Date, Requester ID. 

Configuration requires a ZenDesk API Key, Username, and Account URL.

http://www.autotask.com/eu-data-processing-faq


Addigy VPP 

Addigy Volume Purchase Program Intergration leverages Apples Volume Purchase Program as part of Apple MDM.

Data that can be managed via Apple Volume Purchase Program are available and published in the following links from Apple's Developer Resource:

VPP App Assignment

https://www.apple.com/legal/privacy/


Addigy DEP 

Addigy Device Enrollment Program Integration leverages Apples Device Enrollment Program as part of Apple MDM.

Data that can be managed via Apple Device Enrollment Programs are available and published in the following links from Apple's Developer Resource:

Device Enrollment Program

https://www.apple.com/legal/privacy/


Addigy MDM

Addigy Mobile Device Management Integration leverages Apples Mobile Device Management Protocols

This data resides in the same location for all Addigy data and is subject to the Information, Security, and Privacy policies dictated in the Addigy Information, Security, and Privacy Program.

Data that can be managed via MDM Protocols are available and published in the following links from Apple's Developer Resource:

Check-in Protocol

MDM Protocol

https://www.apple.com/legal/privacy/


ZenDesk  

Addigy can integrate with ZenDesk Ticketing platform to generate tickets.

Data Transmitted consists of Organization ID, Agent ID, Serial Number, Device Name, Device Model Name, Ticket ID, Platform ID, Organization ID, Agent Name, Ticket Name, Severity Level, Ticket Subject, Ticket Description, Status, Creation Date, Requester ID. 

Configuration requires a ZenDesk API Key, Username, and Account URL.

https://www.zendesk.com/company/customers-partners/eu-data-protection/


Freshdesk

Addigy can integrate with Freshdesk Ticketing platform to generate tickets.

Data Transmitted consists of Organization ID, Agent ID, Serial Number, Device Name, Device Model Name, Ticket ID, Platform ID, Organization ID, Agent Name, Ticket Name, Severity Level, Ticket Subject, Ticket Description, Status, Creation Date, Requester ID. 

Configuration requires a Freshdesk API Key and Freshdesk Account URL.

https://freshdesk.com/gdpr


DUO

Addigy developed a Multi-Factor Authentication Integration with DUO, which relies on data already provided in the Addigy Platform.

Data transmitted revolves around the User ID, Username, Realm, Status, Last Login, Phone Number, and Tokens.

Note: When validating Multi-Factor Authentication a text message or phone call may be received to the phone number provided.

https://duo.com/assets/pdf/gdpr-data-protection-addendum.pdf


Watchman Monitoring

Addigy can integrate with Watchman Monitoring.

Data Transmitted consists of Organization ID, Agent ID, Serial Number, Device Name, Device Model Name, Ticket ID, Platform ID, Organization ID, Agent Name, Ticket Name, Severity Level, Ticket Subject, Ticket Description, Status, Creation Date, Requester ID, and Custom Watchman Facts.

Configuration requires a WatchMan API Key and WatchMan Account URL.

https://www.watchmanmonitoring.com/privacy/


BrightGauge  

Built and Supported by BrightGauge, please reach out to BrightGauge to ascertain detailed information about what data is being collected specifically from the Addigy API.

https://www.brightgauge.com/data-processing-addendum/


ITGlue 

Built and Supported by IT Glue, please reach out to IT Glue to ascertain detailed information about what data is being collected specifically from the Addigy API.

https://itglue.com/controller-processor-addendum/


When applicable ensure that a Data Processing Agreement is in place with the integration partner if required. 

Should you have any further questions or comments, feel free to reach out to privacy@addigy.com.