> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synheart.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sub-processors

> Third parties that process customer data on Synheart's behalf when you use Synapse

A sub-processor is a third party that Synheart uses to run Synapse, and that may process your data as a result. Synapse uses as few as possible. This list was built from Synapse's production code and infrastructure, checked in November 2026. Logging, metrics and secret storage run mainly on infrastructure Synheart hosts in its own AWS account; see the note on error alerting below.

## Sub-processors

| Sub-processor | Purpose | Data processed | Location |
| - | - | - | - |
| **Amazon Web Services, Inc.** | Hosting: compute (EKS), database (Aurora PostgreSQL), API gateway, load balancers, key management (KMS), secret storage, object storage, logs and backups | All Synapse customer data | United States (us-east-1) |
| **Amazon Web Services, Inc.** (Simple Email Service) | Sending service email, such as seat invitations | Recipient email address, inviter name, organization name | United States (us-east-1) |
| **DeepInfra, Inc.** | Turning text into embeddings (numeric vectors) for search, using the open model `intfloat/multilingual-e5-large-instruct`. No text is generated. | Text from knowledge sources, decisions and notes saved to organization memory, and search text: dashboard searches and the queries coding agents send (used for the search, then discarded) | United States |
| **Together AI** (Together Computer, Inc.) | Writing short plain-language explanations of team recommendations and investigations, and of a member's own coaching tips. Used **only when explanations are turned on for your organization**; they are off by default. Synheart's Syni service sends the request and stores no prompt or response. | Recommendation and investigation text with aggregate figures for the organization or a department, which can include team averages of human-state measures (for example cognitive load or fatigue). For coaching tips, only after the member opts in: their own tip text and their own meeting and focus shares. No member or department names, decisions or organization memory are sent. | United States |
| **Stripe, Inc.** | Subscriptions, checkout, invoices and payments | Billing contact name and email, organization and plan, seat and usage counts. Card details are entered directly with Stripe and never reach Synheart. | United States |

## Not sub-processors

**No language model for search or Ask.** The Search page returns cited excerpts found by search, and the Ask page lists decision records; no model writes an answer. The only model that writes text is the one behind explanations (Together AI, above), and only when explanations are turned on.

**Monitoring we checked and found off.** As of 2026-11-10 the dashboard's Sentry error reporting has no production key, so it sends nothing; no application log group forwards to Better Stack, which hosts only the public status page; and no metric stream to Grafana Cloud exists. Each would be added here before it is turned on.

**Identity providers you choose.** If people sign in with Google, GitHub or Apple, that provider confirms their identity to Synheart. These are your users' choice of sign-in, not services Synheart uses to process your data.

**Tools you connect.** GitHub, GitLab, Slack, Notion, Google Workspace (Calendar and Drive), Microsoft 365, Linear, Jira, Zoom, and AI vendors (Anthropic, OpenAI, Cursor, GitHub Copilot) are your own services. You authorize Synapse to read from them; Synheart doesn't send them your data. Synapse writes back only when you ask it to (for example, when an agent opens a pull request to record a decision), and in repositories where you install the Synapse GitHub App it posts a "Synapse decisions" check on pull requests. What Synapse reads from each is on the [Security overview](https://docs.synheart.ai/synapse/security.md#what-synapse-stores).

## Changes to this list

Synheart updates this page before a new sub-processor starts processing customer data. To be told about changes, or to ask about a sub-processor, email **[security@synheart.ai](mailto:security@synheart.ai)**. Your DPA sets the notice period and how to object.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.