Skip to content
ClutchReelVersion 2026-11-13

Data Processing Agreement

This template describes how the ClutchReel operator processes customer content. It is not legal advice. A production deployment must have counsel review it, insert the operating entity and contact details, and execute it with each customer. Accepting it in Settings records the workspace's assent to this version.

ResidencyUnited States only

Model trainingNever on customer content

Retention7d source · 30d exports

1. Parties and roles

The customer (the “Controller”) and the ClutchReel operator (the “Processor”) enter into this Data Processing Agreement for the processing of personal data submitted to the ClutchReel service.

The Controller is responsible for having a lawful basis to upload recordings, including the consent of people who appear in them. The Processor processes that data only to provide the service, secure it, and comply with law.

2. Scope and purpose

Processing covers video and audio ingestion, transcription, analysis, editing, rendering, storage and the features the Controller enables. The subject matter, duration, nature and purpose of processing are limited to delivering those features.

  • Data subjects: the Controller's team members and people visible or audible in submitted recordings.
  • Data categories: account identifiers, uploaded media, extracted audio, transcripts, sampled frames, generated clips and usage records.
  • Special categories: the Controller must not upload special-category data unless it has a documented lawful basis and has agreed additional safeguards with the Processor.

3. No training on customer content

The Processor does not use customer content, transcripts, frames, prompts or derived outputs to train, fine-tune or improve machine-learning models, and does not permit a subprocessor to do so.

Only providers on the deployment's allowlist may receive content. Each allowlisted provider is declared as no-training in the provider registry; a provider that reserves training rights is refused by the application before any content is sent.

4. Subprocessors

The Processor uses the subprocessors listed on this page. The Controller is notified before a new subprocessor that processes customer content is added, and may object on reasonable data-protection grounds.

  • OpenAI — transcription, analysis, vision, translation, tts, image; data: extracted audio, transcript text, sampled JPEG frames, prompts, thumbnail prompts (no source imagery); region: US / EU; No training on customer content.
  • Groq — transcription, analysis, translation, vision; data: extracted audio, transcript text, sampled JPEG frames, prompts; region: US; No training on customer content.
  • Cloudflare Workers AI — image; data: thumbnail prompts (no source imagery); region: US / EU; No training on customer content.
  • AssemblyAI — transcription; data: extracted audio; region: US / EU; No training on customer content.

5. Regional processing and residency

This deployment is pinned to United States. New workspaces can only be created in that region, and processing, object storage and database access are expected to remain inside it. A contradictory DATABASE_REGION, or an object-storage endpoint that is not scoped to this jurisdiction, is refused in strict mode rather than silently crossing the boundary.

Where multi-region operation is desired, it requires a separately deployed regional stack; the application does not route a single workspace's content between regions.

6. Security measures

The Processor applies ownership and workspace-scoped authorization, least-privilege provider scopes, encryption in transit, AES-256-GCM encryption of social OAuth tokens at rest, private object storage with short-lived signed URLs, and an append-only audit trail for security-relevant workspace actions.

Provider credentials and social tokens are never returned to the browser or written to logs. Audit metadata is redacted before storage.

7. Retention and deletion

Sources are retained for 7 days by default and exports for 30 days, unless the Controller deletes them sooner. Deleting a project revokes access immediately and schedules artifact removal.

Account deletion removes stored objects and cascades database rows. Backups and provider-side copies follow the retention stated by each subprocessor. The Processor confirms deletion in writing on request.

8. Assistance, breach notification and audits

The Processor assists the Controller with data-subject requests and impact assessments to the extent the service allows. The Processor notifies the Controller without undue delay after becoming aware of a personal-data breach affecting customer content.

On request, the Processor provides the information needed to demonstrate compliance with this agreement, subject to confidentiality and security constraints.

9. International transfers

Customer content stays in the deployment region. If a subprocessor or support activity requires a transfer outside that region, the Processor relies on an approved transfer mechanism and documents it before the transfer occurs.

10. Acceptance and versioning

This version is 2026-11-13. Acceptance is recorded per workspace with the signer's name, title, timestamp and the accepting account, and is written to the workspace audit log. A new version requires a new acceptance.

Provider allowlist

ProviderUseRegionsTraining
OpenAItranscription, analysis, vision, translation, tts, imageus / euNever on customer content
Groqtranscription, analysis, translation, visionusNever on customer content
Cloudflare Workers AIimageus / euNever on customer content
AssemblyAItranscriptionus / euNever on customer content
Local processingtranscription, analysis, vision, translationeu / usNever on customer content

Only allowlisted, no-training providers may receive content. An unlisted or training-reserving provider is refused before any audio, frame or text is sent.

Privacy · Accept in Settings · Terms