Subprocessors

About this page

This page lists the third parties that process content and personal data on SynC's behalf, where they process it, and what controls we apply to them.

This page states no promises. Our commitments about what we and our providers may do with your content are in the Terms of Service §5.3 and the Privacy Policy §4.1A. If this page and either of those ever disagree, they govern. This page records who is currently engaged; those documents record what they are permitted to do.

Providers change from time to time. Our obligations do not. Where a change would materially reduce the protections described in Terms of Service §5.3.3, we give at least thirty days' notice before it takes effect.

1. AI inference

The router. OpenRouter does not run the model itself. For each request it selects one of the hosts below from a set we specify. The operative data policy is therefore the selected host's, not the router's, which is why the hosts are listed individually.

Controls applied to every request:

• the router is instructed to exclude providers it classifies as logging on or training on submitted content, and that classification is the router's, reported to us;
• routing is restricted to the hosts listed below;
• automatic failover is disabled, so an outage produces a failed request rather than a reroute to a host we have not vetted;
• a minimum numeric-precision floor is set; and
• the request fails rather than proceeding if no host satisfies these constraints.

What the locations column means. Our configuration pins the provider, not the region: we choose which companies may serve a request, and the router offers no country or jurisdiction filter. The column below therefore gives each provider's own disclosed processing footprint — the set of places a request to that provider may be served — rather than the location of any individual request.

Hosts not on this list — including a model's first-party endpoint — are excluded by our configuration, and failover is disabled so that none can be selected.

2. Text embedding (semantic search)

To make content searchable by meaning rather than only by keyword, text is converted into numeric vectors by a third-party embedding service. The vectors are stored in our own database. This covers public SynC Standards content, customers' own standards and project specifications, and the search queries users type.

Controls applied to every request: the same set as §1 — logging and training excluded at the provider on the router's classification, routing restricted to the hosts below, automatic failover disabled, and fail-closed behaviour, so that search falls back to keyword matching rather than relaxing a constraint.

Search-query caching is first-party. Queries and their vectors are cached in our own database and are not shared with any processor. That cache carries no account identifier; see Privacy Policy §5.1 ("Derived Search Data").

3. Infrastructure, storage, email

4. Analytics and monitoring

What each of these receives, and what is withheld from it, is set out in Privacy Policy §4.1. They are listed here for completeness of the set.

5. Payments

No payment processor is engaged. This page will be updated before one is.

Changes to this page

This page was first published together with Terms of Service v1.7 and Privacy Policy v1.8; those documents carry the effective date. Changes made after that are recorded here.

Questions

privacy@synergyinconstruction.com — including if your engagement requires zero-data-retention processing or a restricted set of processing jurisdictions.