Samplecut
Agents Open the app

Legal

Privacy policy

This policy covers everything called Samplecut: the website at samplecut.app, the API behind it, and the Samplecut browser extension for Chrome and Edge. It describes what we actually collect, why, and what you can do about it. Samplecut does not sell personal data and does not show ads.

Using Samplecut without an account

Extracting, cutting and downloading audio needs no account. When you paste a link, the link is sent to our API, which fetches the audio, prepares it for the editor and keeps the working files for about an hour before deleting them. We keep a record of each video that has been extracted — its platform, ID, title, length, a small waveform preview and, where available, the start of its captions — so it can have a public page on the site. That record is about the video, not about you: it is not tied to your account, IP address or analytics ID.

Analytics and session recordings

We use PostHog (hosted in the EU) to understand how Samplecut is used and where it breaks. On the website this includes:

The website passes that random ID to our API with each request, so a failed download can be matched to the session it happened in. Analytics is only switched on for the production site. You can block it with any common content blocker; the site keeps working.

Signing in with Google

You only need an account to publish cuts to the shared library. Sign-in is through Google; we never see your Google password. From Google we receive your name, email address and profile picture, and we store them with the username you choose and a session cookie that keeps you signed in. Your username is shown publicly next to cuts you publish. Once you are signed in, your analytics ID is linked to your account so that your events carry your username.

Published cuts

When you publish a cut, its source video, start and end times, label, waveform preview and your username become public in the library and on their own page, and may be shown to search engines.

Server logs

Our API keeps operational logs (requests, errors, timings) so we can keep it running. IP addresses are never written to these logs in readable form — only as a short one-way hash, which lets us tell whether repeated failures come from the same place without recording where that is. IP addresses are also used, in memory only, to rate-limit abuse. Logs are sent to PostHog.

The browser extension

The Samplecut browser extension adds download buttons to YouTube video pages. It works like this:

Who else handles data

To fetch a video's audio, our servers make requests to the video platform (YouTube, TikTok or Instagram), sometimes through a proxy provider. Those requests come from our servers, not your browser, and do not include information about you.

Your choices

Changes and contact

If this policy changes, the date at the top changes with it. Questions go to privacy@samplecut.app.