Subprocessors

MyTravelPeace uses third-party service providers (“subprocessors”) to operate the Service. This list reflects processors currently integrated in the product architecture.

It should be read with the Privacy Policy. We do not list secrets, API keys, or internal connection strings here.

Role: Authentication provider and application database platform.

Purpose: Account authentication, session support, storage of application data such as trips, collaborators, subscription projections, AI usage metering, and Admin operational tables.

General data categories: Account identifiers and emails (via Auth), Customer Content, subscription fields, operational logs and aggregates as implemented.

Role: Payment processor / Merchant of Record where applicable.

Purpose: Checkout, recurring billing, invoices/taxes as configured, customer portal sessions, and webhook events used to update local subscription state.

General data categories: Billing customer and subscription identifiers, transaction and subscription events, tax-related checkout data processed by Paddle. Full card numbers are handled by Paddle, not stored as PAN data in MyTravelPeace application databases.

Role: AI model provider.

Purpose: Generate AI Assistant and Public Radar responses from prompts and structured request inputs you submit.

General data categories: Prompts, filters, and related request context needed for inference; usage outcomes reflected in product metering and aggregates.

Role: Application hosting and edge delivery when the Service is deployed on a hosting platform such as Vercel.

Purpose: Serve the web application and API routes.

General data categories: Request metadata and application traffic as processed by the host to deliver the Service. Exact hosting vendor depends on deployment configuration.

MyTravelPeace does not currently operate a configured first-party transactional email delivery integration in the Admin Settings sense (email delivery is not configured as a product email pipeline).

Authentication-related emails (for example verification or recovery), if sent, are typically handled by the authentication provider (Supabase Auth) according to that provider’s configuration—not by a separate MyTravelPeace SMTP product integration.

This list does not include advertising networks, marketplace processors, or booking suppliers, because those products are not part of MyTravelPeace.

We may add or replace subprocessors to operate and improve the Service. Material updates will be reflected on this page with a revised document version when practicable.

Subprocessors may process data in the United States and other countries where they operate. Transfer safeguards are addressed in the Privacy Policy and remain subject to counsel confirmation where required.

Questions about this document may be directed to MyTravelPeace through the support channel designated by the operator.

Pending Legal Review — this section requires counsel confirmation for jurisdiction-specific wording.

Related documents: Privacy Policy, Terms of Service, and other pages linked from the Service footer.