The services we rely on.

Inscendo uses a commercial API tier under which the provider is contractually prohibited from using customer data for AI-model training. This covers data Inscendo sends to the provider. An AI application your organization connects to Inscendo under its own subscription with that provider is governed by your own agreement with the provider, not by ours (Data Processing Addendum § 6.2, Terms § 4.9).

Used under an API tier that does not train on submitted data by default.

Engaged through the AI gateway below, under Vercel's agreements with it. TypeSafe AI states that it hosts its service in the United States, but it is not limited by contract to the United States: the gateway does not pin the region in which the model runs, and a request a provider flags for abuse or safety review may be handled outside the United States. Zero data retention is requested on every request: it keeps the text no longer than needed to produce the answer, except where its legal obligations require, and does not use it to train models. Never receives text from a workspace whose AI Security setting is Sealed, or whose setting cannot be determined. In use from November 12, 2026 (Data Processing Addendum § 11.2).

Deletes the request and the answer once the request completes and does not use them to train models; a request it flags for abuse or safety review may be kept under its own policies. It may receive and process a request in its data centers outside the United States before forwarding it, and Inscendo cannot restrict this step to the United States, which is why Data Processing Addendum § 11.2 is an exception to the United States commitment in § 11.1. In use from November 12, 2026.

Every customer gets a dedicated database and a per-tenant storage container, with credentials held in a managed, tenant-scoped secrets vault. Logical separation reduces, but does not absolutely eliminate, cross-tenant risk.

Handles platform-generated email; the recipient address is processed only to deliver the message.

Backup email path used if the primary provider is unavailable; the recipient address is processed only to deliver the message.

Receives only the destination phone number, the code, the delivery channel, and whether the code was later used, never Customer Data. Inscendo generates and checks every code itself; Twilio only delivers it.

Inscendo receives tokenized card references only: we never see raw card numbers, expiration dates, or CVVs.

Provides authoritative DNS for the domains Inscendo operates. Used and/or reserved to restrict inbound traffic from the EEA, UK, Switzerland, China, Russia, and OFAC-sanctioned regions in support of the U.S.-only eligibility requirement.

Hosts Inscendo's platform source and build pipelines, not customer configurations, which are stored in each tenant's own per-tenant storage. Does not process Customer application data in the ordinary course.

Registrar only: authoritative DNS is provided by Cloudflare. Does not process Customer application data.

Holds an encrypted, write-once copy of each tenant's backups outside Azure so a failure there cannot reach it. Each copy is kept for a fixed period of no more than ninety (90) days and cannot be deleted earlier by anyone, including Inscendo. Listed on August 29, 2026, before any Customer Data is stored with this subprocessor (DPA § 6.3).