Privacy Policy

This policy explains how RiftCut handles information when the user connects a Google/YouTube account.

Google data used

RiftCut requests limited YouTube OAuth access to view basic YouTube account/channel information and upload videos. It does not request access to Gmail, Google Drive, contacts, passwords, or unrelated Google services.

How data is used

YouTube account information is used only to confirm the connected channel. Upload permission is used only to send videos that the user has approved for upload.

Storage and sharing

OAuth client credentials and refresh tokens are stored on the user's own Mac used for the automation. Google OAuth tokens are not sold, used for advertising, or shared with data brokers. RiftCut may send user-created preview media, titles, and workflow status to the user's configured private review infrastructure or Discord server, but Google account credentials and OAuth tokens are not sent there.

Retention and deletion

The user can revoke RiftCut's Google access at any time from the Google Account permissions page. Local RiftCut OAuth credentials can also be deleted from the user's Mac to disconnect the service. Source clips are retained until the configured workflow completes successfully or the user removes them.

Security

RiftCut is designed to keep OAuth secrets local and to use encrypted HTTPS connections to Google APIs. No system can guarantee absolute security, but access is limited to the permissions required for the workflow.

Last updated: August 25, 2026