SUBPROCESSORS

Know which providers support Dryvn—and why.

This directory distinguishes providers used to deliver the Dryvn customer service from public-website and customer-initiated services. It explains the purpose, information, location approach, and configuration boundary for each.

Last reviewed: August 26, 2026

CURRENT DIRECTORY

No invisible provider relationship.

Dryvn uses providers where they are needed to operate, secure, bill, support, and improve the service. The role of each provider stays bounded to its declared function.

Customer Data processors and public-website services are different contexts. This directory keeps that distinction visible.

Customer-service subprocessors

Providers that may process Customer Data to deliver the contracted Dryvn SaaS service.

Google Cloud

Cloud infrastructure and managed AI inference

Provide core cloud hosting, managed databases and storage, networking and security services, monitoring and operational services, and managed Gemini inference through Google Cloud's AI platform.

Data categories: Customer Data stored or processed in Dryvn
Copilot prompts and selected authorized tenant context
Copilot outputs and usage metadata
Security and operational metadata
Processing location: Configured service region or jurisdictional endpoint, with customer-specific regional architecture where agreed. Not every Google service is represented as remaining in one country.
Safeguards and configuration: Tenant-aware access and private infrastructure controls
Copilot provider request-response logging disabled
Persistent provider interaction storage disabled
Customer data not used to train shared models without explicit permission
Regional and customer-managed architecture options under Enterprise
Use: Core hosting is required for the service. Copilot processing occurs only when an Authorized User initiates a Copilot task.
Last reviewed: 2026-08-26

Stripe

Subscription payment and billing

Process subscription payments, billing, payment authentication, and fraud prevention when a customer initiates a configured payment or billing flow.

Data categories: Card and payment details handled by Stripe
Billing identity and transaction information
Subscription and payment state returned to Dryvn
Processing location: Processed through Stripe's payment infrastructure according to the transaction and Stripe's service terms.
Safeguards and configuration: Loads only in payment or billing contexts
Dryvn receives billing identifiers and transaction state rather than card details needed only by Stripe
No Dryvn workforce records sent for payment processing
Use: Customer initiated; active only where Stripe payment functionality is configured.
Last reviewed: 2026-08-26

Public-website and customer-initiated services

Services used outside the workforce SaaS processing boundary or only when a visitor chooses the relevant public-site feature.

Google

Google Calendar Appointment Scheduling and Google Meet

Allow a prospective customer to schedule a Dryvn demo, receive calendar invitations, and generate a video-meeting link.

Data categories: Booking details entered in Google's scheduler
Appointment and meeting-confirmation information
Business contact information available to the meeting organizer
Processing location: Handled directly through Google's booking and meeting services.
Safeguards and configuration: Cross-origin iframe isolation
No Dryvn interception or duplication of scheduler fields
No scheduler-specific Dryvn analytics
External booking fallback remains available
Use: Customer initiated on /contact; the scheduler loads with the page under the current booking design.
Last reviewed: 2026-08-26

Google

Google Analytics

Understand public marketing-site navigation and performance so Dryvn can improve the site and understand marketing effectiveness.

Data categories: Public page path without query strings or fragments
Browser and site-usage information controlled by the analytics property
No Dryvn workforce records, prompts, booking fields, or authenticated HCM activity
Processing location: Processed through Google Analytics only after Analytics consent and only when a real Measurement ID is configured.
Safeguards and configuration: Consent controlled
Advertising storage and personalization remain denied
Not loaded in the authenticated HCM application by default
No advertising audiences or personalized advertising
Use: Optional; controlled through Cookie settings.
Last reviewed: 2026-08-26

TRUST

Need a specific regional or provider boundary?

Talk with Dryvn about customer-managed AI, regional processing, dedicated infrastructure, or procurement requirements.

Contact Dryvn Explore Copilot security