Privacy Policy
This policy explains how Clipping handles information when the operator connects a social account and processes or publishes a video.
Effective September 20, 2026
1. Information processed
Clipping may process source videos, audio, transcripts, draft clips, captions, titles, descriptions, thumbnails, job history, review decisions, error logs, and application-estimated API usage. When a social platform is connected, the application may also receive an account identifier, display name, granted permissions, access token, refresh token, token expiry, publishing status, and platform post identifier.
2. How information is used
Information is used to create draft clips, show processing status, support review decisions, connect an authorized social account, upload an explicitly selected clip, monitor publishing status, prevent duplicate posts, refresh authorization, and troubleshoot failures.
3. Local processing and storage
Video transcription and rendering run locally on the operator’s computer. Application records are stored in a local SQLite database. Credentials and platform tokens are kept in protected local configuration or encrypted storage and are not placed in source code or public logs.
4. External services
If OpenAI text analysis is enabled, Clipping may send transcript text, timestamps, and candidate metadata to OpenAI for clip ranking and metadata generation. It does not send raw video or full-resolution frames to OpenAI. When the operator confirms publishing, the selected video, caption, publishing settings, and necessary account identifiers are sent to the selected social platform.
5. Sharing and sale
Clipping does not sell personal information. Information is shared only with services selected by the operator as needed to provide text analysis or platform publishing, or when required by law.
6. Retention
Default local retention is two days for source videos, drafts, and approved outputs, and five days for failed-job artifacts and logs. Database history and connected-account records remain until removed, disconnected, or cleaned by the operator. Published posts remain subject to the destination platform’s retention controls.
7. Access, deletion, and revocation
The operator can disconnect a platform to revoke future access and can remove locally stored jobs and account records. Platform permissions can also be revoked through the connected platform’s account settings. To request help accessing or deleting application data, contact the address below.
8. Security
Clipping uses local access controls, authenticated dashboard access, restricted secret files, and limited API permissions. No security measure can guarantee absolute protection, so credentials should be rotated if exposure is suspected.
9. Children
Clipping is not directed to children and is not intended to collect personal information from children.
10. Changes and contact
This policy may be updated when application or platform behavior changes. Privacy questions and data requests may be sent to bertain.ai.18@gmail.com.