Data privacy is a very important part of the Addigy platform, and we recognize 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 and send device data from the Addigy API. The inventory below lists the integrations and the type of known data collected for each.
- What this covers: The integrations listed below, the data each can transmit, and the configuration credentials each requires.
- Who it's for: Data Controllers, and the compliance or privacy teams who support them, evaluating an Addigy integration.
Note: Review the Addigy Privacy Policy, the Addigy Terms of Service, and any corresponding third-party legal documents before you enable a third-party integration and deploy it to your devices or configuration.
For the data collected by the Addigy Agent and the Addigy platform itself, rather than by an integration, see Addigy GDPR Data Audit.
Integration Data Inventory
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.
- Data transmitted: 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 at the phone number provided. This service relies on a third-party provider, which is listed in Addigy's DPA.
ConnectWise Ticket Integration
Addigy can integrate with the ConnectWise Manage ticketing platform to generate tickets.
- Data transmitted: 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.
- Vendor legal reference: https://www.connectwise.com/legal
AutoTask
Addigy can integrate with the AutoTask ticketing platform to generate tickets.
- Data transmitted: 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, Agent Name, Ticket Name, Severity Level, Ticket Subject, Ticket Description, Status, Creation Date, Requester ID.
- Configuration requires: AutoTask API credentials and an Account URL.
- Vendor legal reference: http://www.autotask.com/eu-data-processing-faq
Addigy VPP
The Addigy Volume Purchase Program integration leverages Apple's Volume Purchase Program as part of Apple MDM.
- Data transmitted: The data that can be managed via the Apple Volume Purchase Program is published by Apple in Apple's Device Management documentation.
- Vendor legal reference: https://www.apple.com/legal/privacy/
Addigy DEP
The Addigy Device Enrollment Program integration leverages Apple's Device Enrollment Program as part of Apple MDM.
- Data transmitted: The data that can be managed via Apple Device Enrollment Programs is published by Apple in Apple's Device Management documentation.
- Vendor legal reference: https://www.apple.com/legal/privacy/
Addigy MDM
The Addigy Mobile Device Management integration leverages Apple's Mobile Device Management protocols. This data resides in the same location as all other Addigy data and is subject to the Information, Security, and Privacy policies dictated in the Addigy Information, Security, and Privacy Program.
- Data transmitted: The data that can be managed via MDM protocols, including the Check-in Protocol and the MDM Protocol, is published by Apple in Apple's Device Management documentation.
- Vendor legal reference: https://www.apple.com/legal/privacy/
Zendesk
Addigy can integrate with the Zendesk ticketing platform to generate tickets.
- Data transmitted: Organization ID, Agent ID, Serial Number, Device Name, Device Model Name, Ticket ID, Platform 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.
- Vendor legal reference: https://www.zendesk.com/company/customers-partners/eu-data-protection/
DUO
Addigy developed a Multi-Factor Authentication integration with DUO, which relies on data already provided in the Addigy platform.
- Data transmitted: User ID, Username, Realm, Status, Last Login, Phone Number, and Tokens.
- Vendor legal reference: https://duo.com/assets/pdf/gdpr-data-protection-addendum.pdf
Note: When validating Multi-Factor Authentication, a text message or phone call may be received at the phone number provided.
Watchman Monitoring
Addigy can integrate with Watchman Monitoring.
- Data transmitted: Organization ID, Agent ID, Serial Number, Device Name, Device Model Name, Ticket ID, Platform 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.
- Vendor legal reference: https://www.watchmanmonitoring.com/privacy/
BrightGauge
Built and supported by BrightGauge. Contact BrightGauge to ascertain detailed information about what data is being collected specifically from the Addigy API.
- Vendor legal reference: https://www.brightgauge.com/data-processing-addendum/
IT Glue
Built and supported by IT Glue. Contact IT Glue to ascertain detailed information about what data is being collected specifically from the Addigy API.
- Vendor legal reference: https://itglue.com/controller-processor-addendum/
Data Processing Agreements
Where applicable, ensure that a Data Processing Agreement is in place with the integration partner if one is required.
Frequently Asked Questions
Does this article cover the data Addigy itself collects?
No. This article covers third-party integrations only. For the data collected by the Addigy Agent and the Addigy platform, see Addigy GDPR Data Audit.
Is data sent to an integration that is not enabled?
Addigy third-party integrations can retrieve and send device data from the Addigy API when they are enabled.
Why do some entries not list the data transmitted?
BrightGauge and IT Glue build and support their own integrations against the Addigy API. Contact those vendors directly for detail on what they collect.
Who do I contact with a privacy question?
Email privacy@addigy.com.