Privacy Policy

Recut turns long podcasts and videos into short clips with captions for each social platform. This policy explains what happens to your data when you use it. In short: Recut has no accounts and no database. Your projects stay in your own browser, and we only send data to the services needed to do what you ask.

What Recut stores, and where

Your projects (transcripts, clips, captions), Brand Memory rules, performance learnings, content calendar and settings are saved only in your browser (IndexedDB and local storage). They are not uploaded to or kept on our servers. You can delete all of it at any time in Settings → Clear all my data, or by clearing your browser's site data.

Media you upload

Audio is extracted from your file inside your browser. To transcribe it, the audio is sent in short pieces to Groq, either through our server (when using the app's shared key) or directly from your browser (when you add your own Groq key). Transcripts, and text needed to pick clips and write captions, are sent to Groq's AI models in the same way. Our server passes these requests through and does not store or log their contents. Your original video or audio file never leaves your device.

Voice briefs

If you use the in-app Record button, the recording is sent to Groq for transcription in the same way as uploads. If you dictate with Wispr Flow, that happens in Wispr Flow under its own privacy policy; Recut only receives the text it types.

Google Calendar

If you choose Connect Google Calendar, Recut asks for permission to manage events in your calendar (calendar.events). It uses that permission only to create, update and delete the events for posts you schedule in Recut, so your Google Calendar matches Recut's calendar. Recut does not read, copy or change any other events.

Sign-in uses Google Identity Services in your browser. The access token is kept in your browser, expires after about an hour, and is never sent to our server. You can disconnect in Recut at any time, and revoke access at myaccount.google.com/permissions.

Recut's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data, use it for advertising, or use it to train AI models.

Hosting, logs and cookies

Recut is hosted on Vercel, which keeps standard request logs (such as IP address and time) for security and operations. We use your IP address briefly to apply a fair-use limit on the shared AI key. Recut uses no advertising or tracking cookies and no analytics.

Sharing

We don't sell or share your data. It goes only to the processors named above (Groq for AI, Google if you connect your calendar, Vercel for hosting), and only to provide the features you use. When you post to a social network from Recut, you do that on the network's own site under its terms.

Children

Recut is not directed at children under 13, and we don't knowingly collect their data.

Changes and contact

If this policy changes, we'll update the date above. Questions or requests: open an issue at github.com/Ultranmus/recut/issues.