MSP TARGET LEGAL
Third-Party Data & Integrations Policy
This Policy describes how MSP Target handles information and services originating outside MSP Target.
Provenance and verification
Third-party information may include supplier and TSD directory facts, public contacts, services, logos, MSP Trigger pipeline stages, assigned/status timestamps, estimated ARR, and suggested-provider relationships. Where material, MSP Target preserves source attribution and labels estimates and suggestions as unverified third-party information. Users must verify current accuracy before acting.
HubSpot
A workspace owner or administrator may authorize MSP Target through HubSpot’s OAuth process. MSP Target does not receive the user’s HubSpot password. Authorization tokens are encrypted and scoped to the workspace. MSP Target performs a user-directed, one-way push for supported contacts, companies, and deals; it writes only configured fields and does not promise two-way reconciliation. Users must select an appropriate HubSpot pipeline and remain responsible for duplicates, field mappings, permissions, retention, and HubSpot-side changes.
MSP Trigger
MSP Target is independent from MSP Trigger. Users elect whether they have an MSP Trigger account and may import copied information. MSP Target preserves source pipeline context and provenance but does not independently verify MSP Trigger estimates, findings, statuses, or suggested providers. MSP Trigger access and data remain subject to MSP Trigger’s own terms.
Email and infrastructure providers
MSP Target may use SendGrid or another provider to transmit approved communications and receive delivery events. Hosting, monitoring, payment, and security vendors may process limited information necessary to provide their services under appropriate agreements.
Supplier and TSD systems
Links, contacts, services, supplier rosters, portals, registration rules, and credentials may change without notice. A listed relationship does not establish authorization to transact. Users must confirm their own agreements, commissions, territories, certifications, and registration rights directly with the supplier or TSD.
User responsibility and disconnecting
You must comply with third-party terms and have authority to connect accounts or transmit records. You may disconnect supported integrations, but third parties may retain data already received under their own policies. MSP Target is not responsible for third-party outages, account restrictions, data loss, API changes, or decisions.