Subprocessors

Last updated: July 17, 2026 SynapsAI Technologies Inc. (“SynapsAI”) uses the subprocessors listed below to operate SynapsAI Cloud and our public marketing website. This list supplements our Privacy Policy, Data Policy, and Data Processing Agreement. Your API inference payloads (prompts, inputs, outputs, embeddings, audio, images, and video) are not shared with subprocessors for marketing, analytics, model training, or resale. Infrastructure subprocessors receive only what is technically necessary to execute your workload, route traffic, or operate the platform, under contractual data-protection obligations. We will update this page when we add or replace a subprocessor that materially affects how personal data or platform data is handled. Enterprise customers subject to our DPA may object to new subprocessors as described in the DPA.

Platform & infrastructure subprocessors

These providers support the SynapsAI Cloud platform (APIs, deployments, dashboards, and authenticated services).

Subprocessor	Role	Categories of data	Typical location
Nebius	Primary AI cloud infrastructure — GPU compute, execution environments, and related hosting for model deployments and inference workloads	Model weights and compilation artifacts (tenant-scoped); ephemeral inference payloads during job execution; deployment and workspace metadata necessary to run compute	Per Nebius datacenter region used for your workloads (United States only during the beta period)
Cloudflare	Network edge — DNS, DDoS mitigation, CDN, and TLS termination for public endpoints	IP addresses, HTTP request metadata (method, path, status, timestamps, request size); TLS session data. Does not receive prompt text, model inputs, or generated outputs by design	Global edge network; traffic may be processed in multiple regions
Better Stack	Incident management, uptime monitoring, log aggregation, and alerting for platform reliability	Operational metadata — aggregated error diagnostics, health-check results, monitoring alerts, and redacted infrastructure logs. Does not receive raw inference payload content	United States and European Union (per Better Stack service configuration)
Stripe	Payment processing infrastructure (configured; not used for charges during beta)	When billing is enabled post-beta: billing contact details, transaction identifiers, and payment instrument data handled directly by Stripe. SynapsAI does not store raw card numbers or CVVs	Per Stripe’s regional processing

Marketing website subprocessors

These providers apply only to the public marketing site at synapsai.cloud when you consent to analytics cookies. They never receive SynapsAI Cloud API inference data.

Subprocessor	Role	Categories of data	Consent required
Google Analytics (Google LLC)	Website usage measurement	Pages visited, device/browser type, approximate region, referral source, session metrics (measurement ID `G-2MTV9WDCRQ`)	Yes
Microsoft Clarity (Microsoft Corporation)	Session recordings, heatmaps, and behavioral analytics	Clicks, scrolls, navigation paths, device/browser info (project ID `xcmetdaiuc`)	Yes

See our Cookie Policy for cookie names, durations, and how to withdraw consent.

Beta note

During the SynapsAI Cloud beta period, the platform is provided without billing or sales. Stripe is listed because payment infrastructure may be connected for a future commercial launch; no payment instruments are collected or charged during beta unless we announce otherwise in advance.

Contact

Questions about subprocessors or data handling: [email protected]

Getting started

Guides

Examples

Manage

Platform

Resources

Support

Legal

Platform & infrastructure subprocessors

Marketing website subprocessors

Beta note

Contact

​Platform & infrastructure subprocessors

​Marketing website subprocessors

​Beta note

​Contact

Platform & infrastructure subprocessors

Marketing website subprocessors

Beta note

Contact