Zero data retention

Some organizations operate under rules that forbid a third-party service from storing their code or prompts at all, even transiently beyond the moment of processing. Zero data retention is the arrangement that meets that bar. Under it, the prompts Syntic Code sends and the responses Amara returns are used to serve the request and then not persisted, so there is no stored copy to retain, review, or expose later.

What the guarantee means

With zero data retention in effect, the content of your requests is processed to generate a reply and is not written to durable storage afterward. This closes the gap that a data-protection reviewer worries about most: not the encrypted transit, which is always protected, but whether anything lingers on the far side once the answer has been returned. It is the strongest data posture available and is aimed at regulated industries and teams handling especially sensitive source.

Enabling it for your organization

Zero data retention is configured at the account level with Syntic AI rather than toggled per machine, because it is a property of how your organization’s traffic is handled upstream. Arrange it through your account and confirm which credentials and endpoints it covers, then make sure every path your developers use, direct, through a gateway, or through a self-hosted endpoint, resolves to that account so no traffic slips onto a different, retaining path. Pin the base URL and credentials through server-managed settings so the guarantee cannot be bypassed by a misconfigured machine.

Tradeoffs and complementary controls

Because nothing is retained, features that would depend on stored history across the boundary are necessarily limited, so plan for the agent to carry context only within a live session. Zero data retention governs the model side; it does not by itself constrain what the agent does locally. Continue to enforce permissions, sandboxing, and scoped tasks so the local footprint is controlled too, and document the arrangement for your auditors alongside the data-usage details they will ask about.