Trust Center policy

TyriaCore Subprocessor List

Current subprocessor roster and subprocessor change notice process.

Back to Trust CenterBack to the Engine
Document type
Published policy
Public policy page
Last updated
May 31, 2026
Current published revision
Access
Public
No authentication required

TyriaCore Subprocessor List

Last Updated: May 31, 2026

This page lists third-party subprocessors Provider may use to provide the Subscription Services. Some subprocessors are used only if enabled/configured.

This Subprocessor List is incorporated by reference into the Agreement and/or DPA between Provider and Customer to the extent referenced or incorporated.

Order of precedence. If there is a conflict between this page and the DPA regarding Personal Data processing (including notice and objection rights), the DPA controls.

1. Scope and Stack Notes

This list covers Provider-operated production services and Provider-operated support/operations. Customer-managed systems, credentials, endpoints, or external databases that Customer connects to the Platform are Customer-directed integrations and are not Provider subprocessors solely because Customer configures the connection.

The current production product stack is AWS-hosted. The product application runs on AWS ECS Fargate behind an AWS Application Load Balancer, uses AWS RDS/PostgreSQL and RDS Proxy for production databases, AWS ElastiCache for Valkey for shared cache, AWS S3 with AWS KMS for file/PDF/audit storage, AWS Secrets Manager for runtime secrets, AWS CloudWatch for logs/alarms, and AWS EventBridge/SQS for scheduled operations. The dedicated PDF generator runs on AWS Lambda behind Amazon API Gateway.

Vercel is not core application hosting for the current production product stack, and Neon is not the current core production database. Legacy Vercel Blob object access or Neon-backed database environments may exist only for migration, legacy access, or customer-specific configurations.

2. Core Production Infrastructure

| Subprocessor | Purpose | Used When | |---|---|---| | Amazon Web Services (AWS) | Cloud hosting, production databases, object storage, key management, secrets management, cache, logs/monitoring, scheduled operations, container registry, static marketing hosting, and PDF rendering infrastructure | Core production hosting, storage, cache, logging, operations, and PDF generation |

3. Communications, Support, and User-Configured Integrations

| Subprocessor | Purpose | Used When | |---|---|---| | Google Workspace / Google APIs | Business support communications, Google OAuth sign-in, Google Calendar integration, and Google Sheets/data-connection integrations | Support communications; Google sign-in; if Customer or an authorized user enables a Google integration | | Twilio | SMS, MMS, voice, telephony webhooks, sender registration/compliance workflows, and related communications metadata | If messaging/voice features are enabled or configured | | Mailgun | Transactional email, authentication email, workflow email, payment emails, form/contract emails, and email template retrieval | If email delivery or Mailgun-backed workflow/email features are enabled or configured | | Browser/OS push service providers | Delivery of opted-in browser push notifications through the push service selected by the user's browser or operating system, such as Apple, Google, Mozilla, or Microsoft | If browser push notifications are enabled by Customer/user and the browser provides a third-party push endpoint |

4. Payments and Billing

| Subprocessor | Purpose | Used When | |---|---|---| | Juspay Hyperswitch | Payment orchestration, payment method tokenization/vaulting, hosted payment links, payment status reconciliation, refunds, chargebacks/disputes, and payment processor routing | If payment collection or Hyperswitch-backed payment features are enabled or configured | | Stripe | Platform billing, invoice collection, setup-mode Checkout Sessions, payment method summaries, Stripe Connect/destination-charge onboarding, Stripe webhooks, and Stripe connector routing through Hyperswitch | If Stripe billing, Stripe Connect, or a Stripe payment connector is enabled or configured |

5. AI Features

| Subprocessor | Purpose | Used When | |---|---|---| | OpenAI | AI-assisted generation, transformation, extraction, summarization, classification, or recommendation features | If AI functionality is enabled or configured |

6. Updates and Notice of Material Changes

Provider may update this list from time to time.

If a DPA applies, Provider will provide notice and an objection process for material subprocessor changes consistent with the DPA (including timelines and Customer's limited termination remedy, if applicable).

7. Contact

Questions: support@tyria.app