Sub-Processors

Effective Date: January 1, 2024
Last Updated: October 1, 2026

Querio uses the third-party vendors (sub-processors) below to run its service and manage customer relationships. Each entry lists what the vendor does, where it processes data, and what data it receives.

Customer Data

These sub-processors store or process data from your connected sources and your use of Querio.

Amazon Web Services

Purpose: Application hosting, compute, and file storage
Location: Germany (Frankfurt). Dedicated deployments may run in AWS GovCloud (USA).
Data: Name, email, and in-app behavior of Querio users; schema information and metadata from customer sources; results of queries run in Querio; files uploaded to Querio workspaces

Neon (a Databricks company)

Purpose: Managed PostgreSQL database
Location: Germany (Frankfurt)
Data: Name, email, and application data of Querio users, including conversations, notebooks, and workspace settings; schema information and metadata from customer sources

Postmark

Purpose: Delivery of scheduled report and automation emails
Location: USA
Data: Recipient email addresses and the contents of scheduled reports, including attachments

Large Language Model Providers (API)

These providers receive the context the Querio agent needs to answer a user's request. That includes schema information, the results of queries the agent runs, and the contents of files users upload.

Anthropic

Purpose: Large language model provider (API)
Location: USA
Data: Schema metadata, query results, and uploaded file contents as needed to answer a user's request

OpenAI

Purpose: Large language model provider (API)
Location: USA
Data: Schema metadata, query results, and uploaded file contents as needed to answer a user's request

Google (Gemini API)

Purpose: Large language model provider (API)
Location: USA
Data: Schema metadata, query results, and uploaded file contents as needed to answer a user's request

Amazon Bedrock

Purpose: Large language model hosting for dedicated deployments
Location: Same AWS region as the dedicated deployment
Data: Schema metadata, query results, and uploaded file contents as needed to answer a user's request

Querio User Data

These sub-processors handle data about Querio users (people who log in and use the platform). They do not receive data from your connected sources.

PostHog

Purpose: Product analytics and error tracking
Location: European Union
Data: Email, name, and in-app behavior of Querio users

Loops

Purpose: Account email delivery
Location: USA
Data: Email address of Querio users and message metadata for sign-in emails, such as email verification and password reset

Google

Purpose: Authentication (Sign in with Google)
Location: USA
Data: Name, email address, and authentication metadata of Querio users

Stripe

Purpose: Payment processing
Location: USA
Data: Name, email, and billing information of Querio users

Disify

Purpose: Disposable email detection at signup
Location: Latvia (European Union)
Data: Email address entered at signup

Burner Bouncer

Purpose: Disposable email detection at signup
Location: Germany
Data: Email address entered at signup

Cal.com

Purpose: Scheduling calls with prospective customers and Querio users
Location: USA
Data: Name, email, and booking details of people who schedule a call with Querio

Clarify

Purpose: Customer relationship management (CRM)
Location: USA
Data: Name and email of Querio users

Slack

Purpose: Internal company communication and shared customer channels
Location: USA
Data: Email of Querio users who share a Slack channel with Querio

Sprinto

Purpose: SOC 2 compliance automation
Location: USA
Data: Name, email, and access metadata of Querio users