Sub-processors
PAID engages the third parties below to process personal and financial data on our behalf. This appendix supplements our privacy policy and merchant terms. This page is the list. Card payments through Stripe are the only payment method PAID offers today, so no other payment provider receives data.
Last updated: 2026-11-01
Notice of changes
We will provide at least 30 days' advance notice before engaging a new sub-processor that processes merchant or buyer personal data, except where an earlier change is required for security, legal compliance, or continuity of service. Notice is delivered by email to account owners and by updating this page. You may object on reasonable grounds relating to data protection; if we cannot resolve the objection, you may terminate the merchant agreement per the terms.
Current sub-processors
| Sub-processor | Purpose | Data categories | Region |
|---|---|---|---|
| Fly.io | Application and database hosting | All classification tiers processed by PAID | US |
| Cloudflare | Static frontend delivery and edge network | Request metadata (IP, user agent); no payment or identity data | US / global edge |
| Plaid | Merchant payout-bank verification only (Auth, Identity, Balance). Not used for buyer-side data. | Bank-link tokens via Plaid Link (stored encrypted) and the last four digits of the account; no raw bank credentials stored by PAID | US |
| Stripe | Card acceptance, Connect platform, and merchant KYB / representative KYC (custom connected accounts provisioned by PAID; identity submitted via Stripe's Persons and Files APIs from PAID's own UI) | Cardholder data (tokenized; PAN held by Stripe); merchant PII and government ID images collected during Connect verification (held by Stripe) | US |
| Sardine | Fraud-risk signals (optional; only where configured). Not a sanctions or PEP source — sanctions screening runs in PAID's own engine against public government lists. | Transaction and device risk attributes; risk scores returned to PAID | US |
Due diligence
Each sub-processor is subject to a documented data-processing agreement and annual review by our Security Lead. New integrations require policy approval before production traffic is routed.
Related documents
- Privacy policy — lawful bases, retention, data-subject rights
- Security model — encryption, access control, incident response
- Information security and data governance — the public editions of our policies
- Merchant exam packet — partner due-diligence index
Questions: privacy@trustfabric.ai or security@trustfabric.ai