Sub-Processors

Effective Date: January 1, 2024
Last Updated: March 7, 2026

Querio uses a set of third-party vendors (sub-processors) to operate its services and manage relationships with customers. These sub-processors help run the product infrastructure and process various aspects of Querio's business—but they do not have access to your end users' data.

Data About Querio Users

These sub-processors handle data related to Querio users (people who log in and use the platform). They support core business operations.

PostHog (with DPA)

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

Loops (with DPA)

Purpose: Transactional email delivery
Location: USA
Data: Email address of Querio users and transactional message metadata (such as password reset and invitation emails)

Google (with DPA)

Purpose: Authentication (OAuth)
Location: USA
Data: Name, email address, and authentication metadata of Querio users

Stripe (with DPA)

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

Clarify (with DPA)

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

Slack (DPA available on request)

Purpose: Internal company communication
Location: USA
Data: Email of Querio users

Notion (with DPA)

Purpose: Internal documentation
Location: USA
Data: Name and email of Querio users

Sprinto (with DPA)

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

Note: These sub-processors apply only to Querio user data (the people who use the product), not to your end users' Customer Data.

Data About Your Operations

These sub-processors support customer data processing and operational functionality.

Amazon Web Services (AWS) (with DPA)

Purpose: Hosting and real-time data processing provider
Location: Germany
Data: Email, name, in-app behavior of Querio users, plus schema information and metadata from customer sources

Vercel (with DPA)

Purpose: Frontend hosting and edge network
Location: USA (edge nodes globally)
Data: Request metadata and session information of Querio users

Neon / Databricks (with DPA)

Purpose: Managed PostgreSQL database
Location: European Union
Data: Email, name, application data of Querio users, query data caching, plus schema information and metadata from customer sources

Large Language Model Providers (API)

OpenAI

Purpose: Large language model provider (API)
Location: USA
Data: General schema metadata only. No explicit customer data is shared with this sub-processor.

Anthropic

Purpose: Large language model provider (API)
Location: USA
Data: General schema metadata only. No explicit customer data is shared with this sub-processor.

Google (Gemini / Generative AI)

Purpose: Large language model provider (API)
Location: USA
Data: General schema metadata only. No explicit customer data is shared with this sub-processor.

Let your team and customers work with data directly