Skip to content
Back to Home
Legal

DATA PROCESSING AGREEMENT

Last Updated: 08/2026

A Data Processing Agreement is available for signature for all customers who need one. Where you are a controller of personal data and PromptGuard processes it on your instructions, the DPA is the instrument that governs it.

Requesting it

Email sales@promptguard.co with your legal entity name and the jurisdictions involved, and we will send the agreement for review and signature. If your organisation requires its own DPA template rather than ours, send it and we will review it.

If you need it as part of a security review rather than a contract negotiation, security@promptguard.co can supply it alongside the rest of the diligence pack.

What it covers

  • Roles. You as controller, PromptGuard as processor, with processing limited to your documented instructions.
  • Subject matter, duration and purpose of the processing, and the categories of data and data subjects.
  • Technical and organisational measures. The controls described on our security page, including the retention behaviour and zero-retention option.
  • Subprocessors. The current list, advance notice of additions, and your right to object.
  • Confidentiality obligations on personnel with access to your data.
  • Personal data breach notification — our obligation to notify you without undue delay, and to assist your own notification duties.
  • Assistance with data subject rights — supported in the product by data export and deletion endpoints.
  • Deletion or return of data at the end of the engagement.
  • Audit and information rights sufficient for you to verify compliance.
  • International transfers — the transfer mechanism where personal data leaves its origin jurisdiction. Note that the hosted service runs in the United States; if that is unacceptable, the self-hosted and air-gapped deployments keep the data in your own infrastructure.
  • CCPA service-provider terms for customers who need them.

Two things worth knowing before you read it

Your prompt data is not used to train anything. No model training, no fine-tuning, no shared dataset. This is a property of the system rather than only a contractual promise — there is no code path from your traffic into a training set.

You can reduce what we process to almost nothing. Zero-retention mode stops content being stored, and a self-hosted or air-gapped deployment means we are not a processor of your prompt content at all. The cleanest way to satisfy a difficult data-protection requirement is usually to arrange for us never to receive the data.

Related