This page lists the entities that process personal data on AdsPing’s behalf in connection with the Service. It supplements the Data Processing Agreement (Annex III) and the Privacy Policy (Section 5). AdsPing will provide at least thirty (30) days’ prior notice of any change to this list via the Service or by email to the customer contact on file.
1. Infrastructure subprocessors
These providers run the platform AdsPing operates on. They have no independent purpose for customer data and process it only on AdsPing’s instructions.
| Subprocessor | Service | Region |
|---|---|---|
| Railway Corp. | Application hosting and managed Postgres database | US / EU |
| Cloudflare, Inc. | CDN, DNS, TLS termination, DDoS protection | Global |
| Stripe, Inc. | Billing and payment processing | US / EU |
| Google LLC (Workspace) | Transactional and account email (via SMTP) | US / EU |
| Functional Software, Inc. (Sentry) | Application error monitoring | US |
2. Advertising platform recipients
When a customer wires an advertising platform as a destination on their pixel, conversion events are forwarded to that platform via the platform’s official Conversions / Events API. Each recipient is an independent controller of the data it receives in accordance with that platform’s own terms.
| Recipient | API used | Region |
|---|---|---|
| Google LLC — Google Ads | Google Ads API (Conversions API) — customers:uploadClickConversions | US |
| Google LLC — Google Analytics 4 | GA4 Measurement Protocol | US |
| Google LLC — Google Tag Manager (server-side) | Server-side container HTTPS endpoint (customer-hosted) | Customer-defined |
| Meta Platforms, Inc. | Meta Conversions API | US / EU |
| TikTok Pte. Ltd. | TikTok Events API | US / SG |
Customers control which destinations are connected at any time and can disconnect a destination from their dashboard, which stops forwarding immediately.
3. Data forwarded
The data fields forwarded to advertising platform recipients are determined by each platform’s API specification. AdsPing does not forward direct identifiers (email, phone) in plaintext to any recipient — identifiers used for matching are normalized and SHA-256 hashed prior to transit. Typical fields include:
- Event name and timestamp
- One or more click identifiers (gclid / gbraid / wbraid for Google Ads; fbc / fbp for Meta; ttclid for TikTok)
- SHA-256 hashed email and phone (Enhanced Conversions)
- Order ID (for cross-channel deduplication)
- Conversion value and currency code (when configured)
4. Changes
AdsPing will update this page when a subprocessor is added or replaced. Material changes are notified to customers as described above. The “Last updated” date at the top of this page reflects the most recent change.
5. Contact
For questions about subprocessors or the data we forward, email [email protected].