Legal
Datacrow Sub-processors
On this page6 sections
This page lists the sub-processors that Datacrow engages to provide the service. We notify merchants at least 30 days before adding or replacing a sub-processor, and merchants have the right to object as set out in our Data Processing Agreement.
How to read this list
Sub-processors fall into three groups:
- Destination APIs — third parties that receive event data forwarded at the merchant's direction. Each is only used when the merchant enables the corresponding destination in Datacrow. A merchant who only enables Klaviyo, for example, will not have their data sent to Meta or Google.
- Infrastructure — providers we use to host the application, store data, queue jobs, and ship logs. Used for every merchant.
- Operational — providers we use internally for billing, email, support, and observability. Not all are always engaged.
1. Destination API sub-processors
Engaged only when the corresponding destination is enabled by the merchant.
| Sub-processor | Function | Data shared | Geographic location | Privacy policy |
|---|---|---|---|---|
| Meta Platforms, Inc. | Meta Conversions API destination — forwards conversion events for ads attribution | Hashed email, hashed phone, hashed customer ID, raw IP + user-agent, event metadata, commerce data | United States | https:// |
| Google LLC | Google Analytics 4 Measurement Protocol — forwards events for analytics reporting | Pseudonymous client ID, hashed customer ID (when present), event metadata, commerce data | United States (with global processing) | https:// |
| Google LLC | Google Ads Enhanced Conversions / Customer Match — forwards conversion data for ads attribution | Hashed email, hashed phone, hashed first/last name, hashed address, gclid, gbraid, wbraid | United States (with global processing) | https:// |
| Klaviyo, Inc. | Klaviyo Events API — forwards events for email/SMS marketing flows | Email, phone, customer ID, event metadata, commerce data (unhashed per Klaviyo's spec — Klaviyo is the customer engagement system and requires plaintext identifiers to match profiles) | United States | https:// |
| TikTok Pte. Ltd. / ByteDance | TikTok Events API — forwards conversion events for ads attribution | Hashed email, hashed phone, raw IP + user-agent, ttclid, event metadata, commerce data | United States and Singapore | https:// |
| Pinterest, Inc. | Pinterest Conversions API — forwards conversion events for ads attribution | Hashed email, hashed phone, hashed external ID, raw IP + user-agent, event metadata, commerce data | United States | https:// |
| Microsoft Corporation | Microsoft Advertising UET Conversions API: forwards conversion events for ads attribution | Hashed email, hashed phone, hashed external ID, Microsoft click ID (msclkid), UET visitor ID, raw IP + user-agent, event metadata, commerce data | United States | https:// |
| Snap Inc. | Snap Conversions API: forwards conversion events for Snapchat ads attribution | Hashed email, hashed phone, hashed first/last name, hashed city, state, zip and country, hashed external ID, raw IP + user-agent, Snap click ID (ScCid), Snap cookie (_scid), event metadata, commerce data | United States | https:// |
| Reddit, Inc. | Reddit Conversions API: forwards conversion events for ads attribution | Hashed email, hashed phone, hashed external ID, raw IP + user-agent, Reddit click ID (rdt_cid), Reddit cookie (_rdt_uuid), event metadata, commerce data | United States | https:// |
| OpenAI OpCo, LLC | ChatGPT Ads Conversions API: forwards conversion events for ChatGPT ads attribution | Hashed email, hashed external ID, hashed first/last name, raw city, region, postal code and country, raw IP + user-agent, ChatGPT click ID (oppref), OpenAI cookie (__obref), event metadata, commerce data. Phone is not sent | United States | https:// |
| Attentive Mobile Inc. | Attentive eCommerce API: forwards product views, add-to-carts and purchases for SMS and email marketing flows | Email, phone, product details (name, variant, price, image and page link), event metadata, commerce data (unhashed per Attentive's spec: Attentive is the merchant's own messaging system and requires plaintext identifiers to match subscriber profiles, like Klaviyo) | United States | https:// |
2. Infrastructure sub-processors
Used for every merchant.
| Sub-processor | Function | Data stored/ | Geographic location | Privacy policy |
|---|---|---|---|---|
| Railway Corp. | Application hosting (compute) | All application code and runtime data | United States (US-West, Oregon) | https:// |
| Railway-managed PostgreSQL | Primary database: stores canonical events, delivery logs, copies of failed deliveries, merchant config, encrypted credentials | All data we collect (see Privacy Policy §3–§5) | United States (same region as application) | Same as Railway |
| Railway-managed Redis | Queue + ephemeral cache: BullMQ job state, identity dedup cache, OAuth bridge state | Canonical event payloads of queued jobs, kept while a job waits or runs and for at most 24 hours after it completes or 7 days after it fails; an hourly cleanup removes them before then. A failed delivery's payload is removed from Redis once the database has recorded the failure. Short-lived state tokens | United States (same region as application) | Same as Railway |
| Vercel, Inc. | Marketing + legal website hosting (www.datacrow.app) | Public web pages only; standard request logs (IP, user-agent). No merchant or shopper account data. | United States | https:// |
3. Operational sub-processors
Used internally; engagement depends on configuration.
| Sub-processor | Function | Data shared | Geographic location | Privacy policy |
|---|---|---|---|---|
| Shopify Inc. | App distribution + billing (charges merchants on our behalf) | Merchant identifiers, subscription state, billing history (no shopper data) | Canada and United States | https:// |
| Axiom, Co. | Log aggregation and observability | Operational logs (filtered to exclude shopper PII); contains merchant IDs, error messages, request IDs | United States | https:// |
| Resend.com, Inc. | Transactional email delivery (e.g., billing notifications, security alerts to merchants) | Merchant email address, message content | United States | https:// |
| Google LLC (Google Workspace) | Business email — receives correspondence sent to our support / privacy aliases | Merchant email address + message content | United States | https:// |
| GitHub, Inc. | Source code hosting + CI | No production shopper data; contains code that processes shopper data | United States | https:// |
| AI / LLM providers (none engaged) | We do not use any AI/LLM provider to process merchant or shopper data. This row is included to commit publicly: if we ever do, it will be opt-in only and disclosed here 30 days in advance. OpenAI is listed in section 1 for a different reason: it runs ChatGPT Ads, and a merchant who enables that destination has their conversion events sent to OpenAI for ads attribution, the same way Meta or Pinterest receive them. Datacrow does not run OpenAI's models, or any other AI model, on that data. | N/A | N/A | N/A |
Notes on cross-border transfers
For merchants located in the European Economic Area, the United Kingdom, or Switzerland, data is transferred to the United States and processed there. We rely on the EU Standard Contractual Clauses (2021/914) Module 2 (Controller-to-Processor) and the UK International Data Transfer Addendum (IDTA) as the lawful basis for these transfers. These are incorporated by reference into our Data Processing Agreement.
Sub-processors that have certified under the EU-US Data Privacy Framework (DPF) — including Meta and Google — provide an additional transfer mechanism. We do not currently rely on DPF certification ourselves; Datacrow as a US indie operates under the SCCs directly.
Change log
| Date | Change |
|---|---|
| June 26, 2026 | Initial published list |
| June 28, 2026 | Corrected infrastructure list — removed Cloudflare (not used); added Vercel (website hosting) and Google Workspace (business email) |
| October 13, 2026 | Database row lists copies of failed deliveries; Redis row says how long queued jobs keep event payloads |
| October 18, 2026 | Added five destination sub-processors: Microsoft (Microsoft Ads), Snap (Snapchat), Reddit, OpenAI (ChatGPT Ads) and Attentive. Each receives a merchant's data only once that merchant enables it. The AI/LLM provider row now says how it relates to the ChatGPT Ads destination |
Last reviewed by Milo on October 18, 2026. Material changes are emailed to active merchants and reflected here within 24 hours.