Sub-processors
Last updated: 2026-05-13Version 1.1
Last updated: May 13, 2026
CargoParse LLC uses the following sub-processors to deliver the Service. Each sub-processor is bound by a data processing agreement or equivalent terms requiring appropriate security and confidentiality protections.
We will provide at least 30 days' advance notice of material changes to this list by updating this page and, for customers with an executed Data Processing Agreement, by email to the account on file.
Infrastructure and Platform
| Sub-processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Cloud infrastructure: compute (Lambda, Amplify), storage (S3), database (DynamoDB), queues (SQS), authentication (Cognito), email (SES, WorkMail), AI inference (Bedrock), OCR (Textract), DNS (Route 53), CDN/WAF | Account data, uploaded documents, extracted data, usage logs, authentication data | United States (us-east-1) |
| Anthropic, PBC (via Amazon Bedrock) | AI model inference for document classification and data extraction | Document content (transient processing only; not retained by the model provider after processing) | United States |
Payments
| Sub-processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Stripe, Inc. | Payment processing and subscription billing on the web app | Name, email, billing address, payment method token (CargoParse does not store card numbers) | United States |
| Apple Inc. | In-app purchase processing and subscription billing for the iOS app (StoreKit / App Store) | Subscription purchase events, receipt tokens, product identifiers, subscription state. Apple holds the user's payment method and Apple ID; CargoParse never sees those. | United States |
| Google LLC (Google Play Billing) | In-app purchase processing and subscription billing for the Android app | Subscription purchase events, purchase tokens, product identifiers, subscription state. Google holds the user's payment method and Google account; CargoParse never sees those. | United States |
Authentication and Identity
| Sub-processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Google LLC | Google OAuth sign-in (optional) | Name, email, profile information shared by user through OAuth | United States |
Mobile App Services
| Sub-processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Functional Software, Inc. (Sentry) | Crash reporting and error monitoring for the CargoParse mobile app | Crash stack traces, device model + OS version, app version, anonymized user identifier (no document contents or extracted data) | United States |
| Expo, Inc. | Push notification delivery (relays to Apple Push Notification Service and Firebase Cloud Messaging) and mobile build/update infrastructure | Device push tokens, app identifier, OS version (no document contents or extracted data) | United States |
Business Operations
| Sub-processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Google LLC (Google Workspace) | Business email, calendar, and internal document storage for CargoParse operations | Business correspondence, support communications | United States |
What Is a Sub-processor?
A sub-processor is a third-party service that processes personal information on our behalf to help us deliver the Service. Our agreements with sub-processors require them to:
- Process data only on our documented instructions
- Implement appropriate security measures
- Respect confidentiality obligations
- Assist with data subject rights requests
- Delete or return data at the end of the engagement
- Notify us of security incidents
Questions
For questions about our sub-processors, contact support@cargoparse.com.
---