Security & Trust

All data is encrypted in transit with TLS 1.2+. Data at rest is encrypted with AES-256 across our database and object storage, using the default encryption provided by our infrastructure subprocessors (Supabase Postgres and Cloudflare R2).

Every customer-data table is protected by Postgres Row-Level Security (RLS). Access is scoped to your organization through database-enforced policies, so one tenant cannot read another tenant's rows even if application code is bypassed. Organization context is resolved fail-closed: a request without a valid organization is denied rather than defaulted.

Accounts sign in with email or Google OAuth. SAML single sign-on is available for Okta, Azure AD (Microsoft Entra ID), and Google Workspace on the Scale plan and above. When SSO is enforced for your domain, password access for managed accounts is blocked. Multi-factor authentication is available through your identity provider.

Members hold one of four roles — owner, admin, editor, or viewer. Permissions are enforced both in the application layer and at the database layer through organization role policies, so sensitive actions (billing, SSO configuration, member management) are restricted to owners and admins.

Security-relevant actions — API key creation and revocation, SSO configuration changes, membership changes, and billing events — are recorded to an append-only audit log with the acting user and organization. Audit records support incident investigation and access reviews.

Public API keys are stored only as salted hashes, are scoped to your organization and plan, and can be revoked at any time. Requests are subject to per-plan rate limits backed by distributed rate limiting. Webhook endpoints you configure must use HTTPS.

Data captured for video generation is automatically deleted 30 days after the video is generated, unless you choose to retain it. You can export your organization's data at any time for portability. You can request deletion of your account and associated data — see our Privacy Policy for details.

We run application error monitoring to detect and triage failures, and distributed rate limiting to protect against abuse. Spend controls cap automated AI and rendering usage to prevent runaway cost.

Clipus runs on Vercel (hosting and edge), Supabase (database, authentication, storage), and Cloudflare R2 (video and asset storage). Our core infrastructure providers maintain SOC 2 Type II reports. The full list of subprocessors that may process customer data is published on our Subprocessors page.

Clipus is built to support GDPR obligations: a Data Processing Addendum is available for customers (see DPA), data export supports portability, and we honor deletion requests. The Service is operated from the United States.

SOC 2: a SOC 2 Type II program is on our roadmap. Clipus is not yet SOC 2 certified. Enterprise customers can request our current security documentation and our readiness timeline.

If you believe you have found a security issue, please email security@clipus.io with details and steps to reproduce. We will acknowledge your report and keep you updated through resolution. Please do not publicly disclose an issue before we have addressed it.

Clipus, Inc.
1111B S Governors Avenue #44561
Dover, DE 19904, United States