Not training data
We don’t train AI models on your prompts, uploads or generations, and we don’t sell them. Our model providers process API data under terms that generally prohibit training on it.
Trust Center
What happens to your scripts, prompts and footage once they’re in ClipTap, who can see them, and how long we keep them. Where something isn’t in place yet, we say so.
We don’t train AI models on your prompts, uploads or generations, and we don’t sell them. Our model providers process API data under terms that generally prohibit training on it.
When you run a generation, or ask the Agent to, the prompt, its references and settings pass through our model gateway to the provider of the model chosen, and to no other model provider. The model is shown before you run it, and every take records which model and settings made it.
Uploads and generated takes are stored in Cloudflare R2. An Enterprise workspace can have its files kept in an EU-jurisdiction bucket instead; this covers files, while account data and the database stay with our hosting provider in the United States.
cn.cliptap.ai is a separate deployment with its own database, sign-in and storage inside mainland China. Accounts and workspaces are not shared between the two editions, and the global edition does not process content in mainland China.
Owner, admin, member, commenter, viewer and guest. Owners and admins manage people and settings; guests see only the projects they are invited to and none of the workspace’s settings or usage.
Each project sets what workspace members can do by default, and individual grants override it. Every request, including the Agent’s, the MCP server’s and the desktop drive’s, is checked against the caller’s access on the server.
A shot list can be shared with a review link that allows viewing and commenting only. Links can be protected with a password, and turning a link off invalidates its address for good.
Sign in with an email link, Google or a passkey (in the mainland China edition: password, SMS code or passkey). Passwords are stored only as salted hashes, and sessions live in HTTP-only cookies.
A deleted project or account leaves everyone’s view at once. We keep it for 30 days, when only our support team can restore it on request, and then permanently delete it, files included.
Copies in backups expire on their normal schedule, typically within a further 30 days.
Billing records are kept as long as tax law requires. Security and access logs are kept for a limited period, generally no more than 12 months.
Our servers, PostgreSQL database and Redis run on OVHcloud in the United States. Files are stored in Cloudflare R2, which also delivers them and sends our email. No other infrastructure provider holds customer data.
Every connection to ClipTap, including real-time collaboration, is encrypted with TLS.
Cloudflare R2 encrypts every stored file at rest.
Credentials for custom model connections are encrypted by our application (AES-256-GCM) before they are stored, and review-link passwords are stored only as hashes.
Card payments are handled by Stripe, a PCI DSS Level 1 service provider. Card numbers go to Stripe directly and never reach our servers.
Only staff who need it can reach production systems and the operator console, and operator actions such as restoring a project are recorded in an audit log.
Our servers send logs, metrics and traces through OpenTelemetry to an observability system we run ourselves, not a third-party analytics service. Prompts and Agent replies are left out of traces by default. Alert rules notify our team of error spikes, failing jobs and slow responses.
The third parties that process customer data for us, what each does and where. AI model vendors receive a prompt only when someone runs one of their models.
Last updated:
ClipTap is SOC 2 Type II ready and ISO 27001 ready: our controls are designed to meet both standards. We don’t have an audit report or a certificate to share yet.
We follow the GDPR’s requirements for the personal data we process: we act as processor for workspace content, publish our sub-processors and offer a Data Processing Addendum with Standard Contractual Clauses.
ClipTap isn’t built for protected health information, and we don’t sign HIPAA business associate agreements.
Read our Data Processing Addendum. To sign a countersigned copy, email [email protected]
How we handle personal data: Privacy Policy
Report a vulnerability or send us a security questionnaire at [email protected]. Our Security page explains responsible disclosure