Privacy policy

Information we use

We store your workspace name, email, role and password hash; tasks and assignments; uploaded videos and previews; revisions, comments, reviews and publication links; and workflow notifications and audit records.

If you connect a social account, we store the account or channel identity, granted permissions, encrypted access and refresh credentials, connection status, and view counts for eligible submitted posts. We do not receive your social account password. Your provider handles login and consent.

Why we use it and who can see it

We use this information to run the clip submission and review workflow, verify the publishing account, collect view counts, show performance reports, and maintain account security. Your team’s Admins and Staff can access workspace submissions and reports as permitted by their roles. Other Clippers cannot access your social credentials.

Authorized infrastructure operators may access stored data to maintain and troubleshoot the service. Credentials are encrypted in storage and are not displayed in reports. Connecting an account does not authorize Clipper to publish, edit or delete your social posts.

Social platforms and service providers

When enabled, Clipper uses Google/YouTube, TikTok and Meta/Instagram APIs to obtain authorized account information and post metrics. Availability depends on platform permissions and account eligibility. These providers process authorization and API requests under their own policies.

We do not sell your personal information or use connected-account data for advertising. We do not use Google user data to train generalized AI models. Clipper’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

The test app uses hosting, database and networking services to operate. When a Cloudflare testing tunnel is active, requests pass through Cloudflare. Technical logs may include request paths, timestamps, IP addresses and error information; credentials and OAuth codes must not be included in application logs.

Retention and disconnecting accounts

Workspace uploads and workflow records do not automatically expire. Contact your team Admin to request deletion. Disconnecting a social account stops collection and removes its stored metrics from active application data. Provider revocation and credential removal may finish in a background job. You can also revoke access directly with the platform.

When enabled and separately accepted, metric history retains observations for up to 28 days. YouTube current observations older than 30 days are removed by scheduled cleanup. Cleanup depends on background workers running. Non-sensitive audit records may remain after disconnection. Backups, if maintained by the operator, may retain data until their retention period ends; disconnection is not a promise of immediate backup erasure.

Use Social accounts → select the platform → Disconnect to remove a connection. Google and TikTok revocation is attempted automatically; Instagram may also require removing Clipper in Meta’s Connected apps settings.

Your choices and requests

Connecting social accounts is optional. You can disconnect them and turn off optional history. To request access, correction, deletion of workspace data, or help with a privacy concern, contact the team Admin who issued your Clipper account through your existing team contact channel. If you cannot sign in, use that same contact channel.

Clipper uses a session cookie to keep you signed in and browser storage for your theme preference. These support the app; the app does not include advertising trackers. Changes to this policy will appear here with an updated effective date.