Subprocessor List

This page lists all third-party subprocessors that OSQR engages to process customer data on our behalf. We publish this list in the interest of transparency and to fulfill our obligations under the General Data Protection Regulation (GDPR) and our Data Processing Agreement (DPA).

This list is referenced by the Data Processing Agreement available at /dpa. If you have executed a DPA with OSQR, the terms of that agreement govern the use of these subprocessors. Enterprise and DPA customers will receive advance notice before any new subprocessor is engaged.

01AI Model Providers

OSQR uses multiple large language model providers to power its AI capabilities. Queries, conversation context, and document excerpts are transmitted to these providers to generate responses. No provider retains this data for model training under our agreements.

Anthropic

AI model provider powering the Claude family of models (Claude Opus, Sonnet, Haiku). Used for primary reasoning, Quick mode, Forge, Council, and agentic tasks.

Data: Queries, context, document excerptsLocation: United States

OpenAI

AI model provider powering GPT-4o. Used for Forge and Council modes, image analysis, blueprint vision, embroidery digitization, and DM vision.

Data: Queries, context, document excerpts, image analysisLocation: United States

Google (Vertex AI)

AI model provider powering Gemini 2.0 Flash Pro. Used for Forge and Council modes as a deliberating voice.

Data: Queries, context, document excerptsLocation: United States

xAI

AI model provider powering Grok 2. Used as a deliberating voice in Forge and Council modes.

Data: Queries, context, document excerptsLocation: United States

Groq

AI inference provider running the Llama 3.3 70B model. Used for fast inference on select task types.

Data: Queries, contextLocation: United States

02Infrastructure & Hosting

These providers host the infrastructure that runs OSQR. All customer data at rest and in transit passes through one or more of these systems.

Vercel

Application hosting and serverless function execution. All web requests and API calls are processed through Vercel's edge and serverless infrastructure.

Data: Application data, request metadataLocation: United States

Neon (PostgreSQL)

Primary database hosting via serverless PostgreSQL with pgvector. Stores all structured application data including accounts, workspaces, vault documents, and conversation history.

Data: All structured application dataLocation: United States

Amazon Web Services (AWS)

Underlying cloud infrastructure used by Vercel and Neon. Customer data may transit or rest on AWS infrastructure as part of those hosted services.

Data: All data in transit and at rest (via Vercel/Neon)Location: United States

03Payment Processing

OSQR does not store payment card data directly. All payment processing is handled by PCI-DSS compliant providers.

Stripe

Payment processing and subscription management. Handles billing, payment method storage, invoicing, and subscription lifecycle for all OSQR plans and add-ons.

Data: Billing info, payment method, subscription statusLocation: United States

04Communications

These providers handle outbound and inbound communications on behalf of OSQR users who have enabled the relevant features.

Twilio

SMS messaging and phone line provisioning for the OSQR VA phone line add-on. Used to send and receive SMS messages on behalf of users who have activated the feature.

Data: Phone numbers, SMS content, delivery statusLocation: United States

Convertio

File format conversion used by the embroidery digitization feature. Converts embroidery design files between formats (e.g., DST to PES, JEF, VP3). Files are submitted for conversion and not retained.

Data: Uploaded design filesLocation: European Union

Note: User Email Providers

OSQR connects to users' own email accounts via IMAP/SMTP (e.g., Gmail, Outlook, custom domains). OSQR does not use a third-party bulk email sending service for user emails. Email content is processed through the user's own email provider, which the user has independently contracted with. Those providers are not listed here as they are not engaged by OSQR on the user's behalf.

05Search & Data

These providers supply external data that OSQR retrieves on behalf of users during research and estimating tasks.

Brave Search API

Web search results provider used when OSQR performs web searches on behalf of users. Search queries are transmitted to retrieve relevant results.

Data: Search queriesLocation: United States

1build

Construction cost data provider used by the Construction Estimating add-on. Quantity descriptions and location data are transmitted to retrieve cost estimates. No personally identifiable information is sent.

Data: Quantity descriptions, locations (no PII)Location: United States

06Changes to This List

→OSQR will update this page when subprocessors are added or removed. The "Last updated" date at the top of this page reflects the most recent change.
→Enterprise and DPA customers will be notified via email at least 30 days before a new subprocessor is engaged, giving you the opportunity to object in accordance with your DPA.
→If you have questions about our subprocessors or their data processing practices, contact us at privacy@osqr.app.

Stay Notified of Subprocessor Changes

To receive email notifications whenever this list is updated, send an email to privacy@osqr.app with the subject line Subprocessor Notifications. We will add you to the notification list and contact you when changes occur.