Disclaimer
A score is a prior, not a prediction. Here is everything the pipeline can get wrong, written down before you find it out.
1What a score is, and what it is not
The number next to a moment is a prior, not a forecast. The rubric behind it was distilled from real shorts that beat their own channel’s median views, so a high score means the passage has the shape of clips that travelled before. It does not mean this clip will travel.
- Nothing in the pipeline sees your audience, your posting time, your thumbnail, or the platform you will publish on — all of which move a clip more than its content does.
- The four pillars are judgements produced by a language model. Two runs over the same video can rank differently, and the model can be confidently wrong about a passage.
- A 90 that is all hook and no value is a different clip from a 90 spread evenly. The pillars are shown next to the total because the total on its own hides that.
Treat the moment list as a shortlist worth watching, not as a decision that has already been made. Nothing is cut until you approve it, which is the point at which your judgement is meant to enter.
2The transcript and the timecodes
- Transcription is automatic. Accents, crosstalk, jargon, names and poor audio all produce errors, and an error in the transcript can put a moment where there is not one.
- Clip boundaries are sentence boundaries taken from that transcript. If a sentence was detected in the wrong place, the cut is in the wrong place too.
- Intro detection is a heuristic. It usually removes the part where you say your own name; occasionally it removes something you wanted, or leaves something you did not.
- Check a clip before you publish it. That step is not optional.
3The renderer
- Speaker tracking follows whoever is talking. On busy footage, overlapping speech or an unusual shot, it can follow the wrong person or move when it should hold.
- The matte cut behind the “text behind the speaker” style is automatic. Fine hair, motion blur and low contrast against the background are where it shows its edges.
- Banner guard measures the footage and punches in only when it finds a baked-in lower third. It can miss one, or find one that is not there, and either way it costs framing.
- Stock b-roll used for cutaways comes from a third-party library under that library’s own licence. Check that licence covers what you are publishing.
4Not advice, and not a guarantee of results
Everything on this site and in the app — including guides, changelog entries and the reasoning attached to a moment — is provided for information. It is not legal, financial or professional advice, and it is not a promise of growth, views, revenue or reach.
Whether a clip performs depends on your material, your audience and the platform, none of which we control. We make no representation about any outcome.
5Your material, and your responsibility for it
You process only what you own or are licensed to use, and you are responsible for what you publish from the output — including any rights of the people who appear in it. The detail is in the acceptable use policy.
We do not review your footage before it is processed and we do not publish anything on your behalf. Neither the score nor the render is an assessment of whether you are allowed to use the material.
6Where this sits against the terms
This page explains the limits of the output; the legal position is in clause 11 of the terms and conditions, which is where warranties and liability are actually dealt with, and which prevails if the two ever read differently. Nothing here excludes liability that cannot lawfully be excluded under the law of Italy, including the statutory rights of a consumer. Questions to intheclips.business@gmail.com.
The contract: accounts, plans, billing, your content, and where our liability ends.
What is processed, why, on which legal basis, for how long, and your rights over it.
The four things stored in your browser, and which of them need consent.
What you may not run through the pipeline, and what happens if you do.
Every provider that can see customer data, what it sees, and where it runs.
For people we wrote to first: where the address came from, why it was yours, and how to make it stop.
Questions about any of this — including a request about your own data — go to intheclips.business@gmail.com.