Legal — Privacy & Terms

Heads up. If you have a specific legal question right now — especially around a commercial use case, paid-clipper program, or data residency — email [email protected] and we'll answer in writing.

Privacy

What Segue collects

• Free tier (no account): No personal information is collected. Mixes are encoded into the URL itself (the #... hash on segue.video/m/<slug>), which never leaves your browser as a server request. We don't store mixes, identifiers, or anything tied to anonymous use beyond the analytics described below.
• Pro tier (signed-in account): Email address (via Clerk), payment information (handled by Stripe — we never see card numbers), and your saved mixes.
• Telemetry: Standard, anonymized request logs (IP address, user-agent, response status) for operational debugging and abuse prevention. No advertising cookies.
• Product analytics (PostHog): Event-level usage data for funnel analysis (which features get used, where people drop off). Behaviour depends on your region:
  • EU / UK / EEA / Switzerland: cookieless by default — in-memory session state only, no cookies, no localStorage, no IP collection, no session replay, no pageview pings. Within-session funnel events still fire so product issues remain debuggable; cross-session attribution is intentionally weaker for this region. A consent banner offers the option to upgrade to standard cookied analytics — declining keeps the cookieless default.
  • Rest of world: standard cookied analytics (UUID distinct_id in localStorage, IP collection on, 5%-sampled session replay with all input fields masked, 100%-sampled session replay on errors). A passive Settings opt-out path is available.
• Error monitoring (Sentry): Stack traces, breadcrumb timelines, and replays sampled around errors. Sentry's default PII redaction is active and we run an additional explicit denylist on top — emails, payment IDs, auth tokens, and other identifying fields are stripped from event payloads before transport. Inputs are masked in any replays.
• Web Vitals: Anonymous performance metrics (LCP, INP, CLS, FCP, TTFB) per route, piped into PostHog and used to identify slow pages.
• Operational logs: Server-side application logs (currently emitted to Railway's standard log capture; Better Stack log shipping coming soon) — these carry the same correlation IDs that tie a request together but pass through a denylist that strips authorization headers, cookies, email fields, and Stripe customer IDs at the logger boundary.

What Segue does not do

• No video re-hosting. Every clip plays via YouTube's official IFrame Player, streamed directly from YouTube. We never download, re-encode, or store video files.
• No selling of user data. Segue doesn't sell, rent, or share account information with third parties beyond the operational vendors required to run the service: Clerk (auth), Stripe (billing), PostHog (product analytics), Sentry (error monitoring), Better Stack (uptime + log shipping — forthcoming), Cloudflare R2 (OG-image cache), Railway (infrastructure), Postgres (saved-mixes database).
• No creator-side scraping. Segue doesn't crawl, scrape, or maintain a database of YouTube videos. The only YouTube data we touch is whatever URL you paste into the studio at the moment you paste it.

Your rights

Pro account holders can export or delete their account and all associated saved mixes at any time. Self-service deletion is available via the Delete account flow described below.

Free-tier users have nothing to delete — the mix lives in the share URL itself, and we never had a copy.

Account deletion

You can delete your Segue account and every record we hold for it from any signed-in session. Open your My Segue page (from the user/account menu) and follow the prompt to delete your account and data. Deletion is permanent: your saved mixes are removed and their public share URLs (segue.video/m/<slug>) stop working, and any active subscription is cancelled so there are no future charges.

If anything goes wrong, or you need a deletion the self-service flow can't reach (e.g. backups outside the live system), email [email protected] and we'll handle it manually.

Free-tier users have no account, no profile, no saved mixes — there's nothing to delete.

Terms

What Segue is for

Segue is a tool for sharing curated moments from publicly-available YouTube videos in a workflow that gives the original creator full view-count and analytics credit. Permitted uses include personal sharing, editorial commentary, podcast/highlight clipping, and creator-side promotion of your own content.

What Segue is not for

• No clipping content the original creator has disabled embedding for. If embedding is disabled on a YouTube video, the IFrame Player can't load it — Segue can't override that, and you shouldn't try to work around it.
• No commercial re-distribution that bypasses YouTube's monetization. Segue exists to redirect viewers to the original embed, with attribution; using it to strip out ads or undermine the source channel's monetization is exactly the abuse pattern that gets tools like this killed.
• No automated scraping or bulk creation of mixes for resale, training data, or aggregation services without prior written permission.

We reserve the right to revoke access (or de-publish specific share URLs) for accounts found to be violating these constraints. The remediation is always proportional and we'll explain in writing before taking action where practical.

Liability

Segue is provided "as is." We do our best to keep the service running and the share URLs working, but we can't guarantee that YouTube's IFrame Player API will continue to behave the same way forever (the deprecation that created the need for Segue is itself a reminder of how fast platform features can change). If a share URL stops working because of an upstream YouTube change, we'll do our best to migrate it; we can't guarantee we'll always succeed.

Pro Lifetime purchases include a 14-day refund window, no questions asked. After that, refunds are handled case-by-case via [email protected].

Changes

When this page changes materially, we'll note the date of the most recent revision at the bottom and (for Pro account holders) send a one-line email summary. We won't change pricing on existing Pro Annual subscriptions mid-cycle or on Pro Lifetime accounts ever.

Acceptable Use

The Terms above (Permitted, Prohibited) describe what Segue is and isn't for. This section names a few additional things that are universally off-limits regardless of plan or account status:

• No content that depicts or sexualises minors. Reports go to NCMEC and law enforcement; the account is terminated immediately.
• No targeted harassment, doxxing, or threats — including assembling clips designed to identify, dox, or coordinate harassment of a specific person.
• No impersonation of another creator, public figure, or organisation in a way intended to deceive viewers about who made the mix.
• No mass automation — bulk creation of share URLs, programmatic clip generation, or scripted view-count inflation. Rate limits enforce this technically; trying to circumvent them is itself a violation.
• No use of Segue to distribute malware, phishing pages, or scam content.
• No content that violates applicable law in the jurisdiction where the mix is created or shared (e.g. content infringing copyright outside of fair use, content prohibited by export control, etc.).

Violations result in removal of the offending mix and, for repeated or severe cases, termination of the account. We err toward writing to the account holder before taking action where the situation allows it.

DMCA & Takedown

Segue respects copyright. Did a mix use your work without your permission? You can ask us to take it down, and we will act on your request.

First, check whether the use counts as fair use or another exception. If it does, the law may allow it.

Filing a notice

To report a mix, email [email protected] with the subject line "DMCA Notice". The law (17 U.S.C. § 512(c)(3)) says your email must include all six things below:

1. The work that was copied. Tell us which of your works was used. A link to the original is fine. If it was never published, describe it well enough that we can tell what it is.
2. The mix that uses it. Give us the full Segue link (https://segue.video/m/<slug> or https://segue.video/watch#…).
3. How to reach you. Your full legal name, mailing address, phone number, and email.
4. A good-faith statement. Say that you honestly believe the copyright owner, their agent, and the law did not allow this use.
5. A statement under penalty of perjury. Say that your notice is true and that you are allowed to act for the copyright owner. ("Under penalty of perjury" means you could face legal trouble if you lie.)
6. Your signature. You can sign by hand or type your name.

We handle complete notices within 3 business days. Most of the time we hide the mix from the public and tell the account holder. If your notice is missing something, we send it back and tell you what to add — we do not just ignore it.

Counter-notice

Did we take down a mix of yours by mistake? Maybe it was fair-use commentary, material you had a license for, or it was mixed up with something else. You can ask us to put it back.

Email [email protected] with the subject line "DMCA Counter-Notice" and include:

1. The removed mix. Name it and give the link where it used to be.
2. A statement under penalty of perjury. Say you honestly believe the mix was taken down by mistake or mix-up.
3. How to reach you, plus your consent to the court. Give your contact info. Agree that a court can settle any dispute — the federal court for your area, or the federal court in San Francisco, California if you live outside the U.S.
4. Your signature. Sign by hand or type your name.

We send a valid counter-notice to the person who complained. If they do not take you to court within 10 to 14 business days, we put the mix back.

Repeat infringers

The law (17 U.S.C. § 512(i)) says we must close the accounts of people who break copyright over and over. We use a three-strikes rule for clear copyright breaks within any 12-month period. For very bad single cases — like uploading a whole pirated film as a "mix" — we may close the account right away.

Security Disclosure

Found a security issue? Please report it to [email protected] with the subject line "Security Report".

• Scope: production segue.video, api.segue.video, the /m/<slug> share-shell origin, and the embed iframe surface (when it ships).
• Out of scope: rate-limit avoidance proofs of concept, clickjacking on static legal/marketing pages, missing security headers absent a demonstrable exploit, third-party services we depend on (Clerk, Stripe, PostHog, Sentry, Cloudflare R2 — report those upstream).
• Disclosure window: we ask for a 90-day responsible-disclosure window from the date you contact us. We'll acknowledge inside 3 business days and aim to resolve high-impact issues inside the window.
• Safe harbour: acting in good faith under this policy will not be treated as a violation of our Terms — we won't pursue or support legal action against researchers who follow it.

We don't currently run a paid bug bounty. We do publicly credit (or anonymise, your call) every researcher whose report results in a fix.

Last meaningful update: May 9, 2026. Questions: [email protected].