To support delivery of our services, Trackops may engage and use data processors with access to certain Service Data (each, a "Subprocessor"). This page provides important information about the identity, location and role of each Subprocessor. Terms used on this page but not defined have the meaning set forth in the applicable agreement between Customer and Trackops.
Prior to engaging any third party Subprocessor, Trackops performs diligence to evaluate their privacy, security and confidentiality practices and executes an agreement implementing its applicable obligations.
| Subprocessor | Purpose | Location(s) |
|---|---|---|
| Amazon Web Services | Infrastructure Hosting, Data Storage | AU, CA, US |
| Functional Software (Sentry) | Error Handling, Alerting | US |
| Here Technologies | Mapping, Geocoding | US |
| Imperva | Content Delivery / WAF | AU, CA, US |
| Mapbox | Mapping, Geocoding | US |
| New Relic | Application Performance Monitoring | US |
| Pipedrive | Customer Relationship Management | US |
| Recurly | Subscription Management | US |
| Sinch (Mailgun) | Email Delivery | US |
| Solarwinds (Loggly, Pingdom) | Log Aggregation, Uptime Monitoring | US |
| Zendesk | Customer Support | US |
The Subprocessors used by Trackops may change over time. Trackops will update this page with new or different Subprocessors as appropriate and necessary.