Trust Center
Last updated: June 10, 2026
Clipus reads your real product data to generate and publish marketing videos. That access is a responsibility. This page collects the facts in one place: how rendering works, what we collect and what we don't, what you control, and where our compliance work stands.
Every claim links to the document or page that backs it. We describe what is shipped — not aspirations. Work in progress is labeled as in progress.
How rendering works
Videos render in your browser with WebCodecs. If a browser can't render, a server fallback uses the same data already stored for your campaign.
See the data flow →Data we collect — and don't
DOM text, screenshots you confirm, and page metadata. Network capture is off by default and redacted when you turn it on.
See the full list →Your controls
Captured data deletes automatically after 30 days. You can export or delete your data, and cap automated spend per organization.
See your controls →Compliance status
SOC 2 readiness is in progress — we are not yet certified. A DPA and subprocessor list are published and kept current.
See where we stand →Intellectual property
The rendering and localization pipeline is covered by a U.S. provisional patent application with 40 claims.
See the filing facts →Trust documents
Security overview, Privacy Policy, DPA, subprocessors, and methodology — the source documents behind this page.
Browse documents →How rendering works
Clipus uses edge-first rendering: by default, your videos render in your own browser using WebCodecs, with hardware acceleration when your device supports it. There is no render farm in the default path — the pixels are composed and encoded on your machine. The finished MP4 then uploads over a signed URL to encrypted object storage, where it stays until you delete it.
Your browser
Renders and encodes the video (WebCodecs)
Encrypted storage
Holds the video until you delete it
Fallback:if a browser can't render (unsupported codec or hardware), the same campaign data already stored for your project — blueprint, screenshots, voiceover — is rendered server-side instead. No additional data is collected for a fallback render.
To be precise about what this does and does not mean: the data that goes into a video (the screenshots and text you confirmed at capture) is already stored for your campaign, and the finished video is uploaded so you can review and publish it. Edge-first rendering means the rendering work itself happens on your device — it is not a claim that video data never reaches Clipus.
Capture scope and storage are documented in the Privacy Policy; encryption and storage providers in Security & Trust.
Data we collect — and don't
When you create a campaign from a page, the Chrome extension captures the visible DOM text, element positions and dimensions, page metadata (title, domain), and the screenshot evidence you confirm. The screenshot is uploaded only when you confirm campaign creation — preview happens before anything is sent.
Network capture is off by default. If you enable it, captured responses are redacted before ingest: authentication headers (Authorization, Cookie, API keys), sensitive JSON fields (passwords, tokens, session identifiers, emails), and URL query secrets are removed.
What we don't do: the extension does not record video or audio of your browsing, does not read your cookies, bookmarks, or browser history, and does not sell captured content to third parties.
No training on your data: we do not use your content to train AI models without your explicit consent, as stated in our Privacy Policy.
The full collection list, including integrations, is in the Privacy Policy (sections 2–3).
Your controls
Data captured for video generation is deleted automatically 30 days after the video is generated, unless you choose to retain it. You can export your organization's data at any time, and you can request deletion of your account — associated data is permanently removed within 30 days.
Per-organization spend controls cap automated AI and rendering usage, so an agent working on your behalf cannot run away with your budget.
Retention periods and deletion rights are in the Privacy Policy (sections 6–7); spend controls and deletion are described in Security & Trust.
Compliance status
SOC 2: readiness in progress. Clipus is not yet SOC 2 certified. A SOC 2 Type II program is on our roadmap, and enterprise customers can request our current security documentation and readiness timeline. Our core infrastructure providers (Vercel, Supabase, Cloudflare) maintain SOC 2 Type II reports.
Clipus is built to support GDPR obligations: a Data Processing Addendum with Standard Contractual Clauses is published, our subprocessor list is public and updated before changes, and data export and deletion are available in-product. Every customer-data table is protected by Postgres Row-Level Security, so tenant isolation is enforced at the database layer.
Details in Security & Trust, DPA, and Subprocessors.
Intellectual property
Clipus filed a U.S. provisional patent application covering the edge rendering and DOM localization pipeline — 40 claims (11 independent, 29 dependent). A non-provisional filing is in preparation.
Trust documents
Security & Trust
Encryption, tenant isolation, SSO, RBAC, audit logging, and vulnerability reporting.
Privacy Policy
What we collect, how we use it, your rights, and retention periods — in full detail.
Data Processing Addendum
GDPR Article 28 processor terms, international transfers, and breach notification.
Subprocessors
Every third party that may process customer data, what it does, and where it runs.
Methodology
How Clipus reads a product page and turns it into a marketing video.
Questions about anything on this page? Email security@clipus.io. To report a vulnerability, see Security & Trust.