Third-Party Data & Integrations Policy

Version 1.3 · Effective October 20, 2026

This Policy describes how MSP Target handles information and services originating outside MSP Target.

Provenance, uncertainty, and correction

Third-party information may include supplier and TSD directory facts, public contacts, services, logos, MSP Trigger stages, timestamps, estimated ARR, and suggested-provider relationships. MSP Target preserves source attribution where material and distinguishes observed, user-entered, third-party, inferred, and approved records. Missing information remains unknown; it is not evidence that a capability, relationship, or customer condition does not exist. Estimates and suggestions require human verification before action. A publicly available source does not transfer ownership of protected material or imply that the referenced organization participates in, endorses, or is affiliated with MSP Target.

HubSpot

A workspace owner or administrator may authorize MSP Target through HubSpot OAuth. MSP Target does not receive the user’s HubSpot password. Tokens are encrypted and scoped to the workspace. The current integration performs a user-directed, one-way push for supported contacts, companies, and deals and writes only configured fields; it does not provide two-way reconciliation. Users remain responsible for pipeline selection, field mappings, duplicate handling, permissions, retention, and later 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, analytics, maps, and infrastructure

MSP Target may use SendGrid or another provider to transmit approved communications and receive delivery events; Plausible for limited cookieless public-page analytics; mapping services where a map feature is used; and hosting, backup, monitoring, security, and support vendors to operate the Service. A payment processor will process payment details if checkout becomes available; MSP Target should not receive complete card credentials. Each provider processes information under its own terms and the permissions required for the enabled feature.

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.

Commercial routes and external systems

A supplier may be available through one or more TSDs, another channel route, or directly. A route recorded in MSP Target is descriptive commercial context—not transaction authority. Confirm current agreements, eligibility, pricing, territory, registration rights, commissions, incentives, and payment terms with the applicable party.

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 a third party may retain information already received under its own policies. MSP Target does not control third-party availability, security, account restrictions, API changes, data retention, or business decisions.