Subprocessors.
These are the third parties Embrasure uses to host, secure, and operate the Service and that may process Customer Data. Each is bound by a written agreement with data protection terms at least as protective as our Data Processing Addendum.
Infrastructure
| Amazon Web Services, Inc. | Cloud hosting for the application, API, workers, and managed warehouse storage and query engines; content delivery; transactional email; and backups. Data: All Customer Data stored in or processed by the Service. Location: United States |
|---|---|
| Supabase, Inc. | Application database, user authentication, and file storage. Data: Account and workspace data, catalog metadata, saved content, conversation history, and encrypted connector credentials. Location: United States |
| Temporal Technologies, Inc. | Workflow orchestration for syncs, agent runs, and scheduled jobs. Data: Workflow inputs and results, which can include identifiers, metadata, and bounded query results. Location: United States |
| ProperMotion (Virgo Observe) | Performance tracing for agent runs, used to find and fix reliability problems. Data: Technical timing, model, token-usage, and request-status information with opaque account identifiers. Prompts, Slack messages, and answers are excluded from traces sent since October 4, 2026. Location: United States |
AI models
| Amazon Web Services, Inc. (Amazon Bedrock) | Hosted AI models used by Embrasure's agents. Data: Prompts, schema metadata, query context, and selected result rows needed for a task. Location: United States |
|---|---|
| OpenAI, LLC | AI models and text embeddings for search and recall. Data: Prompts, schema metadata, query context, selected result rows, and text indexed for search. Location: United States |
| OpenRouter, Inc. | Routes requests to the AI model selected for a task. Data: Prompts, schema metadata, query context, and selected result rows needed for a task. Location: United States |
We use commercial API terms that do not allow these providers to train on Customer Data, and we enable zero data retention where it is available.
Business operations
| Stripe, Inc. | Subscription billing and payment processing. Data: Billing contact, workspace plan, and payment details. Embrasure does not receive full card numbers. Location: United States |
|---|---|
| PostHog, Inc. | Session replay on the Embrasure homepage and in the signed-in product, used to find and fix usability problems. Data: Masked recordings of page layout and interactions, and the signed-in user's ID, name, and email. In the product, text, inputs, images, and data values are masked. Location: United States |
| Google LLC (Google Workspace) | Business email and documents for support and customer communications. Data: Contact details and the content of support requests. Location: United States |
Integrations you enable
These services process data only when a workspace administrator connects them, and only as directed through that connection. Each is governed by the customer's own agreement with its provider.
| Slack | Delivers Ember questions, answers, and alerts in the workspaces and channels you choose. |
|---|---|
| GitHub | Reads repositories you select, runs dbt projects, and opens pull requests you approve. |
| Directory sync, Google Sheets imports, and Cloud SQL onboarding you authorize. | |
| Data sources | Databases and business applications you connect, such as Postgres, Snowflake, Salesforce, and HubSpot. |
Changes to this list
We update this page before a new subprocessor begins processing Customer Data and change the date above. Under the Data Processing Addendum, we notify workspace owners by email at least 15 days in advance, and customers may object. To receive these notices at another address, email privacy@embrasure.ai.