Subprocessors

Last updated: November 7, 2026

Nomad Engineers LLC DBA Syntaxia ("Syntaxia", "we", or "us") uses the third parties below to operate the Syntaxia platform at app.syntaxia.com when we process a customer's data.

Syntaxia does not publish a standalone data processing agreement. Data processing terms are part of the agreement we sign with each customer. Words on this page that are not defined here have the meaning given in that agreement. To request a copy, email [email protected].

We may add or remove subprocessors. We update this page when the list changes, and we give customers notice as their agreement requires.

Service providers for this website, such as hosting and form handling, are described in our Privacy Policy. They do not process customer data inside the platform.

Platform

SubprocessorNature and purposeLocation of processingAdditional information
DigitalOcean, LLCApplication servers and the production database.United States (New York)Trust center
Amazon Web Services, Inc.File storage, and the email that delivers sign-in links.United States (file storage in N. Virginia)Trust center
Fivetran, Inc.Syncs the data connections a customer turns on, such as Salesforce.United StatesSecurity

Problem reports

SubprocessorNature and purposeLocation of processingAdditional information
Linear OrbitIn-app problem reports, for an organization that uses them. We file the report, the reporter's name and work email, the page, and any screenshot they attach.United StatesSecurity

AI providers a customer connects

These are not Syntaxia subprocessors. A call leaves the platform only with a key saved on that organization, under that organization's agreement with the provider. The product has no Syntaxia-wide key for them. We do not use customer data to train models.

Language model. The organization connects Anthropic, OpenAI, or xAI. With a verified key, chat, conversation titles, report drafts, and Vantage analysis use it, and those prompts can include the organization's business data. CRM value mapping and deal-stage naming also use it. Mapping sends picklist words and field names, and deal stages send stage names, order, and deal types. Neither sends company records. A second look at company identity, and industry classification, stay off unless the organization turns them on.

Jev, from TypeSafe. The organization owner connects a separate TypeSafe key. Production asks Jev when that key is verified. The call sends business-identity evidence: names, websites, the work-email domain, the city, and the month of the first record. Chat does not use Jev.

LangSmith. The organization connects its own project and key. Tracing stays off until an owner turns it on. Then chat prompts and answers go to the region they chose, the United States or the European Union. Engine runs are not traced.