# SenseDefend (sensedefend.com) > SenseDefend tracks synthetic-media law to the article and the effective date: who must label AI-generated video, from which date, under which clause, with the wording of the instrument. This site is open for crawling, indexing, quoting and model training. Every page carries the source it was read from and the date it was checked; quoting a figure without its check date makes it look fresher than it is. Full text of every page in one file: https://sensedefend.com/llms-full.txt ## Overview - [SenseDefend: synthetic media law by clause](https://sensedefend.com/): What published instruments require for AI-generated audio, image and video: clause, role, application date and the wording, each with a check date. ## Instruments - [EU AI Act Article 50: duties and application date](https://sensedefend.com/eu/ai-act-article-50/): What Article 50 of the EU AI Act asks of providers and deployers of generative systems, which paragraph carries each duty, and the recorded start date. ## Duties - [Provider or deployer: who carries each AI Act duty](https://sensedefend.com/duties/by-role/): Which paragraph of EU AI Act Article 50 binds the provider, which binds the deployer, and the moment each duty takes effect for generated video. ## Generators - [What generators document about marking output](https://sensedefend.com/duties/what-generators-document/): Sixteen AI tools read against Article 50(2): what each vendor's own pages state about marking output, and what takes the visible mark off. ## Generator records - [SceneMixer, read against Article 50](https://sensedefend.com/generators/scenemixer/): What SceneMixer publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Pika, read against Article 50](https://sensedefend.com/generators/pika/): What Pika publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [LTX Studio, read against Article 50](https://sensedefend.com/generators/ltx-studio/): What LTX Studio publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Kling AI, read against Article 50](https://sensedefend.com/generators/kling-ai/): What Kling AI publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Runway, read against Article 50](https://sensedefend.com/generators/runway/): What Runway publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Google SynthID, read against Article 50](https://sensedefend.com/generators/google-synthid/): What Google SynthID publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [OpenAI Sora, read against Article 50](https://sensedefend.com/generators/openai-sora/): What OpenAI Sora publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Adobe Firefly, read against Article 50](https://sensedefend.com/generators/adobe-firefly/): What Adobe Firefly publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Synthesia, read against Article 50](https://sensedefend.com/generators/synthesia/): What Synthesia publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [HeyGen, read against Article 50](https://sensedefend.com/generators/heygen/): What HeyGen publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [MiniMax Hailuo, read against Article 50](https://sensedefend.com/generators/minimax-hailuo/): What MiniMax Hailuo publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Alibaba Wan, read against Article 50](https://sensedefend.com/generators/alibaba-wan/): What Alibaba Wan publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [ElevenLabs, read against Article 50](https://sensedefend.com/generators/elevenlabs/): What ElevenLabs publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Meta AudioSeal, read against Article 50](https://sensedefend.com/generators/meta-audioseal/): What Meta AudioSeal publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Amazon Nova Reel, read against Article 50](https://sensedefend.com/generators/amazon-nova-reel/): What Amazon Nova Reel publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). - [Microsoft Designer, read against Article 50](https://sensedefend.com/generators/microsoft-designer/): What Microsoft Designer publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4). ## Paragraphs - [Article 50(1): systems people talk to](https://sensedefend.com/eu/ai-act-article-50/paragraph-1/): What Article 50(1) of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. - [Article 50(2): marking generated output](https://sensedefend.com/eu/ai-act-article-50/paragraph-2/): What Article 50(2) of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. - [Article 50(3): emotion and biometric systems](https://sensedefend.com/eu/ai-act-article-50/paragraph-3/): What Article 50(3) of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. - [Article 50(4): deep fakes](https://sensedefend.com/eu/ai-act-article-50/paragraph-4/): What Article 50(4) of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. - [Article 50(4), text: published text](https://sensedefend.com/eu/ai-act-article-50/paragraph-4-text/): What Article 50(4), text of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. - [Article 50(5): how the notice is given](https://sensedefend.com/eu/ai-act-article-50/paragraph-5/): What Article 50(5) of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. - [Article 50(7): codes of practice](https://sensedefend.com/eu/ai-act-article-50/paragraph-7/): What Article 50(7) of the EU AI Act states, who the duty binds, the carve-outs written into it, and the date it starts to apply. ## Questions - [A visible mark and a machine-readable mark](https://sensedefend.com/questions/visible-and-machine-readable/): Why a watermark a viewer sees and a signal inside the file answer different paragraphs of Article 50, and which entries here describe each. - [What it means when a mark can be removed](https://sensedefend.com/questions/removable-marks/): Every visible mark recorded here can be removed. The routes differ, a switch or a plan, and the article says nothing about removability. - [What free tiers publish about marking](https://sensedefend.com/questions/free-tier-marking/): What each vendor's free tier publishes about watermarking, why those rows rest on omissions, and what that means for trial footage. - [Every carve-out written into Article 50](https://sensedefend.com/questions/exemptions/): The three carve-outs written into Article 50, the condition attached to each, and why only one of them switches a duty off entirely. - [When Article 50 starts to apply](https://sensedefend.com/questions/when-it-applies/): Article 50 starts to apply on 2 August 2026, a date set elsewhere in the regulation, and its text is flagged as amended. - [The points no generator addresses](https://sensedefend.com/questions/unanswered/): Interoperability, accessibility and timing are asked for by Article 50 and addressed by no generator's public pages recorded here. - [The duties in Article 50 that are not marking](https://sensedefend.com/questions/the-other-disclosures/): The article that requires generated media to be marked also carries disclosure duties on interaction, deep fakes, emotion recognition and published text. - [Which paragraphs name providers, and which name deployers](https://sensedefend.com/questions/provider-or-deployer/): Article 50 does not put one duty on everyone: paragraph 1 addresses providers, paragraphs 3 and 4 address deployers. This register says which is which. - [The article points at codes of practice it does not contain](https://sensedefend.com/questions/what-is-left-to-be-written/): One paragraph points at codes of practice on detection and marking, so the detail a reader wants is delegated rather than written into the article. - [Which entries describe something inside the file](https://sensedefend.com/questions/inside-the-file/): Seven of the sixteen entries describe a signal or a manifest that travels with the output. The rest describe only what a person can see, or nothing. - [Which entries give a number but not a list](https://sensedefend.com/questions/numbers-without-names/): A membership figure, a version number and two prices. Each is a real published number, and none of them can be checked against a list of anything. - [Where each vendor chose to write it down](https://sensedefend.com/questions/where-it-is-written/): Marking statements here sit on pricing pages, system cards, API references, support articles and one compliance guide. The venue predicts the wording. - [Which tools add nothing unless a request asks](https://sensedefend.com/questions/nothing-unless-asked/): Two hosted interfaces document an optional marking flag that defaults to off, which puts the whole question into somebody's integration code. - [Who can check a mark after the file is delivered](https://sensedefend.com/questions/who-can-check-it/): Reading routes in this record run from a public site anybody can open to tools a vendor describes as internal, with nothing in between. - [What the marking duty says about audio](https://sensedefend.com/questions/the-audio-half/): The paragraph names synthetic audio alongside image and video. Two entries answer for audio, and neither of them can put a notice in a corner. - [Who marks the output when the weights are public](https://sensedefend.com/questions/open-weights/): One entry in this record publishes its model weights. Its API documents an optional mark, and the terms on the weights ask for nothing at all. - [What a missing line on a plan table proves](https://sensedefend.com/questions/what-an-omission-proves/): Several cells in this record are filled because a phrase on the paid plans is absent from the free one. That is evidence, and it is the weakest kind here. - [Which entries describe more than one layer](https://sensedefend.com/questions/two-layers-at-once/): Two entries apply a manifest and something else to the same output. Everything else in this record describes one layer, or none. - [Does any vendor say why the mark is there](https://sensedefend.com/questions/does-anyone-say-why/): One entry gives a reason for removing a mark and one names the mark's purpose in a single adjective. The rest leave motive to inference. - [What a flag set in code does to a finished file](https://sensedefend.com/questions/a-flag-set-in-code/): One support page records a mark applied in test mode that cannot be removed from an existing video. The cause leaves no trace on any account page. - [Which scope claims a reader can actually apply](https://sensedefend.com/questions/scope-you-can-use/): A claim bounded by a named feature can sort a folder of files. A claim spanning a product family cannot be matched against anything. - [What an upload leaves of each kind of mark](https://sensedefend.com/questions/what-an-upload-leaves/): Platforms rebuild containers as a matter of course. That single step decides which of the marks in this record reach an audience. - [What changes when a vendor names a standard](https://sensedefend.com/questions/naming-a-standard/): Four entries name a published provenance specification. Naming one is what carries the interoperability the marking paragraph asks for. - [What buying a higher plan actually changes](https://sensedefend.com/questions/what-buying-changes/): A purchase removes something a viewer can see. On the entries where it is offered, nothing else in the file was ever described in either direction. ## Background - [Metadata, embedded signal, visible label](https://sensedefend.com/learn/three-kinds-of-marking/): One word covers three mechanisms with different failure modes. Which one a file carries decides what survives an edit, a re-encode or a screenshot. - [What to write down at delivery](https://sensedefend.com/learn/keeping-a-delivery-record/): Questions about a published asset arrive long after it shipped. A short record made at delivery answers them; reconstruction afterwards usually cannot. - [What a pricing grid can and cannot tell you](https://sensedefend.com/learn/reading-a-plan-table/): A plan table is written to help somebody choose a tier. Read as evidence about a product's behaviour it is a summary, and summaries leave things out. - [What a system card is written to survive](https://sensedefend.com/learn/reading-a-system-card/): A card published for review is written by people expecting to be quoted back. That pressure shows up as scopes, lists and stated limits. - [Why a reference page is the source to trust](https://sensedefend.com/learn/reading-an-api-reference/): A reference is written for somebody who will notice if it is wrong, which makes its types and its stated defaults unusually trustworthy. - [Why help-desk prose is often the most accurate](https://sensedefend.com/learn/reading-a-support-article/): A support page is written because somebody asked, by people who will be corrected by the next person who asks. Its scopes tend to be right. - [What a weights repository does and does not ask](https://sensedefend.com/learn/reading-a-model-repository/): A repository publishes files and the terms they travel under. Reading it means reading a licence for obligations it may simply not contain. - [The difference between an omission and a statement](https://sensedefend.com/learn/an-omission-is-not-a-statement/): A register can record what a page says and what a page was read for and did not say. Turning the second into the first is the commonest quiet error. - [How to record the thing a page does not say](https://sensedefend.com/learn/recording-what-is-not-said/): An empty cell and a documented absence look the same and mean opposite things. Writing the second out in words is how a reader tells them apart later. - [Why every row in a register carries a date](https://sensedefend.com/learn/why-every-row-has-a-date/): A fact without a date is a claim. A fact with one is a claim somebody can recheck, which is the kind of claim a register exists to publish. - [Why the default decides almost every file](https://sensedefend.com/learn/defaults-decide-most-files/): Documentation describes what a tool can be made to do. A library of files records what it did, and the gap between them is filled by defaults. - [What a per-request control costs to account for](https://sensedefend.com/learn/per-call-controls/): A value carried by one request exists for the duration of that request. Nothing outside the caller's own logs remembers it afterwards. - [Three people who can change what a file carries](https://sensedefend.com/learn/who-holds-the-lever/): An operator, a budget holder and an integrator can each control what output carries, and they rarely speak to each other about it. - [What one ordinary upload does to a file](https://sensedefend.com/learn/what-a-transcode-costs/): A platform that transcodes keeps the content and rebuilds everything around it. That single step decides what reaches an audience. - [Why a mark in a corner is a hostage](https://sensedefend.com/learn/safe-areas-and-crops/): Vertical delivery reframes material for different surfaces, and safe areas differ. A notice pinned to one corner can end up outside the picture. - [Why detecting a mark is a measurement](https://sensedefend.com/learn/thresholds-and-measurements/): Reading an embedded signal is not a lookup. It produces a score against a threshold, which means it has two ways of being wrong. - [Why the route matters more than the file](https://sensedefend.com/learn/verify-the-route/): What a delivered asset carries is decided by the pipeline it travelled, and a pipeline is a small, stable thing that can be tested once. - [Why a version number is worth a field of its own](https://sensedefend.com/learn/version-fields/): Model behaviour changes between versions and interfaces stop showing which version ran. A version noted at render time turns a dead question into a lookup. - [Why producing a generated asset again is not a fix](https://sensedefend.com/learn/re-render-is-not-repair/): Where the published route to changing a file is to generate it again, the result is a new asset rather than a corrected one. - [What a documentation-based record cannot establish](https://sensedefend.com/learn/limits-of-a-register/): A register of what vendors have published describes the state of the published record. That is a different thing from the state of the world. - [How to compare a policy with a price](https://sensedefend.com/learn/comparing-unlike-evidence/): A table can make a policy, a technical description and a line item on a price list look like three comparable positions. They are nothing of the kind. - [When one cell of a table deserves its own page](https://sensedefend.com/learn/when-a-cell-earns-a-page/): Most cells stay cells. A cell earns a page when quoting it needs more context than a table row can carry, and it earns one on no other ground. - [How to count entries without misleading anybody](https://sensedefend.com/learn/counting-entries-honestly/): Every count in a register rests on a rule about what qualifies, and that rule has to be published beside the number for the number to mean anything. - [Which party can actually answer your question](https://sensedefend.com/learn/asking-the-right-party/): Questions about a published asset have to reach whoever can answer them, which is rarely the party somebody asks first, and often not the vendor at all. ## Method - [How SenseDefend records an instrument](https://sensedefend.com/sourcing/): What earns an entry, where the wording is read from, what the two dates on every fact row mean, and how disagreements between sources are handled. ## Terms - [Who pays when a generation is blocked](https://sensedefend.com/terms/content-moderation/): Vendors differ on whether a moderated generation is charged. Two publish a policy and one leaves it unstated, which is itself the finding. - [What an AI label is, and where the dates come from](https://sensedefend.com/terms/aigc-label/): Three published instruments set dates for labelling generated media. They differ in who they bind and in what the label has to be. - [Machine-readable, and the three things it means](https://sensedefend.com/terms/machine-readable/): In an instrument it means software can detect the content as generated. On a product page it usually means a file has some metadata in it. - [Provenance, and why it is not authenticity](https://sensedefend.com/terms/provenance/): Provenance records where something came from. Authenticity is a claim that it is what it appears to be, and no provenance record establishes that. - [Content credentials, a manifest with a signature](https://sensedefend.com/terms/content-credentials/): A family of attached records carrying origin information, signed so that tampering is detectable and dropped whenever a container is rebuilt. - [Watermark, one word for three mechanisms](https://sensedefend.com/terms/watermark/): The word covers a visible notice in the frame, an invisible signal in the content and, loosely, a record in the container. They fail differently. - [Deepfake, a defined term and a headline word](https://sensedefend.com/terms/deepfake/): In an instrument the word carries a definition and a duty. In ordinary use it means any synthetic depiction somebody disapproves of. - [Provider, the party that builds the system](https://sensedefend.com/terms/provider/): A provider develops a system and places it on the market. The duties addressed to that role are discharged before anybody publishes anything with it. - [Deployer, the party that publishes with it](https://sensedefend.com/terms/deployer/): A deployer uses a system on real material. The duties addressed to that role are discharged at publication, by whoever publishes. - [Disclosure, labelling and marking are three things](https://sensedefend.com/terms/disclosure/): A disclosure tells an audience something. A label is a form a disclosure can take. Marking is what happens to a file, and it may tell nobody anything. - [Interoperable, the quality a vendor cannot build alone](https://sensedefend.com/terms/interoperable/): A mark is interoperable when somebody other than its author can read it. That makes it a property of an ecosystem rather than of a product. - [Robust, and the list that gives the word meaning](https://sensedefend.com/terms/robust/): Robustness is not a property of a mark alone. It is a property of a mark against a named list of operations, and the list is the claim. - [Detector, what it reports and what it cannot](https://sensedefend.com/terms/detector/): A detector reports a score about one scheme. It can confirm that a mark is present and cannot establish that any content is authentic. - [Synthetic media, an umbrella with soft edges](https://sensedefend.com/terms/synthetic-media/): The phrase covers anything generated or substantially altered by a model. Where the edge of substantially sits is nowhere defined. - [Open weights, and who inherits the questions](https://sensedefend.com/terms/open-weights/): When model weights are published, anybody can generate with them. Nothing the publisher decides afterwards reaches that output. - [Test mode, the setting that leaves no receipt](https://sensedefend.com/terms/test-mode/): A development flag set in an integration can change what output carries, and nothing on any account page will later reveal it was on. - [Transcode, the step that decides what arrives](https://sensedefend.com/terms/transcode/): A transcode re-encodes content and builds a new container. Copying auxiliary records into the new container is optional and frequently skipped. - [Default value, the fact that describes most files](https://sensedefend.com/terms/default-value/): A default is what happens when nobody intervenes. It describes almost everything a production delivers, and it is the field most references omit. ## Fields - [Who it binds, the row that names the party](https://sensedefend.com/fields/who-it-binds/): The row naming the party a transparency duty falls on. Article 50 moves between the provider who builds a system and the deployer who publishes with it. - [What it asks for, the row holding the duty](https://sensedefend.com/fields/what-it-asks-for/): The row holding the duty a paragraph imposes. One cell asks for a property of a system, another for a mark in a file, another for a notice at publication. - [Who controls it, the row on the generator pages](https://sensedefend.com/fields/who-controls-it/): The row recording what moves a visible mark on a finished file: a paid tier, a switch in settings, or nothing published at all on the vendor's own pages. - [Carve-out, the row for what a duty gives up](https://sensedefend.com/fields/carve-out/): The row recording relief written into a paragraph. Three of them drop a duty and one keeps it while narrowing what the disclosure has to say. - [The fourth row, the one each entry names](https://sensedefend.com/fields/the-fourth-row/): Three rows on a generator entry are fixed. The fourth is whatever that vendor volunteered, and no two entries in this record chose the same one. - [Read from, the kind of page a cell came off](https://sensedefend.com/fields/read-from/): A pricing table, a system card, an API reference and a paper are four kinds of evidence, and this row records which one a cell came off. - [Default state, what an untouched request gives](https://sensedefend.com/fields/default-state/): What comes out when nobody changes anything. Two API references default to no mark at all, and one product ships with a visible mark already on. - [Reading route, who can read the mark later](https://sensedefend.com/fields/reading-route/): A mark nobody outside the vendor can read answers a narrower question than the clause asks. This row records who each entry says can check. - [What survives, the row on durability](https://sensedefend.com/fields/what-survives/): Marks fail in different ways. One entry names the edits its signal is built to withstand, another names an edit that cannot undo a mark already applied. - [Recorded silence, the cell that says nothing](https://sensedefend.com/fields/recorded-silence/): An empty cell and a documented absence look identical in a table and mean opposite things. This row records where a vendor page was read and found silent. ## Statements - [Sora on C2PA metadata attached to every asset](https://sensedefend.com/statements/sora-machine-readable/): The Sora 2 system card names C2PA metadata on all assets as its first provenance measure. What that sentence reaches, and what it leaves open. - [SynthID on a mark added when content is created](https://sensedefend.com/statements/synthid-machine-readable/): The scheme embeds an invisible watermark as content is created, across a family of products. Three of the four stated qualities are claimed. - [Firefly on credentials indicating AI was used](https://sensedefend.com/statements/firefly-machine-readable/): The product page says outputs carry Content Credentials indicating AI was used in the creation process. A record of use, not a record of what made it. - [ElevenLabs on a pattern hidden under the sound](https://sensedefend.com/statements/elevenlabs-machine-readable/): Imperceptible patterns are embedded at frequencies masked by sound already present. The audio answer to a duty most often read about pictures. - [AudioSeal on a generator and detector trained together](https://sensedefend.com/statements/audioseal-machine-readable/): The publication describes a generator and detector trained jointly with a localization loss, for detection down to the sample level. - [Nova Reel on two marking layers in one output](https://sensedefend.com/statements/nova-machine-readable/): The service card describes an invisible watermark on all videos and, from version 1.1, credentials based on C2PA carrying the model and platform. - [Designer on credentials for images it edits](https://sensedefend.com/statements/designer-machine-readable/): The support article says credentials based on C2PA are applied to all images made with the editing features. The scope clause is the whole sentence. - [Wan on marking and the silence in its weights](https://sensedefend.com/statements/wan-machine-readable/): Two pages were read for this entry: an API reference that documents a corner mark, and a repository whose open terms ask nothing about marking output. - [SceneMixer on a mark applied at compositing](https://sensedefend.com/statements/scenemixer-visible-mark/): The guide places a visible watermark on composited episodes and says it is on by default. Where in a pipeline a mark lands is the part worth reading. - [Pika on a visible mark the plan takes away](https://sensedefend.com/statements/pika-visible-mark/): Watermark-free download is absent from the free tier and the $8 tier and appears from $28 upward. The free-tier position is an omission, not a statement. - [LTX Studio on a line its free plan omits](https://sensedefend.com/statements/ltx-visible-mark/): No watermarking is listed from the Lite plan upward and does not appear on the free plan. The crossing point is the lowest among the tier-gated entries. - [Kling AI on a watermark it calls a brand mark](https://sensedefend.com/statements/kling-visible-mark/): Removal is listed as a paid-membership benefit, and the vendor's own word for the mark is brand. That word makes it a signature, not a disclosure. - [Runway on what the free plan does not list](https://sensedefend.com/statements/runway-visible-mark/): Watermark-free output is listed on the paid plans and not on the free one. The free-tier cell here is an inference about packaging, carefully labelled. - [Sora on a moving watermark tied to downloads](https://sensedefend.com/statements/sora-visible-mark/): The system card describes a visible moving watermark on videos downloaded from the site or the app. The mark attaches to a route, not to a plan. - [Synthesia on the conditions that put a mark on](https://sensedefend.com/statements/synthesia-visible-mark/): The article says the watermark appears under certain conditions, naming the Basic plan and API test mode. Two different causes, one visible result. - [HeyGen on removal listed on two paid tiers](https://sensedefend.com/statements/heygen-visible-mark/): Watermark removal is listed as a feature of the $29 and $49 plans and is not listed on the free plan. Two prices, one omission, no stated reason. - [Hailuo on an AIGC label added on request](https://sensedefend.com/statements/hailuo-visible-mark/): The API reference documents a parameter controlling whether an AIGC label watermark is added. The mark is a capability, not a behaviour. - [Wan on a corner mark reading AI Generated](https://sensedefend.com/statements/wan-visible-mark/): The reference documents an optional parameter adding a mark in the lower-right corner with the text AI Generated. Wording and position are both stated. - [Firefly on a frame with no mark described](https://sensedefend.com/statements/firefly-visible-mark/): The product page describes credentials attached to outputs and nothing burnt into the picture. The one silence here that was read for on purpose. - [SceneMixer on a switch rather than a price](https://sensedefend.com/statements/scenemixer-lever/): The guide describes an AIGC watermark switch that turns the visible mark off, and names no plan as the thing that unlocks the switch. - [Pika on the tier at which the mark stops](https://sensedefend.com/statements/pika-lever/): Watermark-free download appears from the $28 Pro plan upward. The lever here is a purchase, and there is no described route at any lower tier. - [LTX Studio on a mark that stops at Lite](https://sensedefend.com/statements/ltx-lever/): No watermarking is listed from the Lite plan upward, which puts the crossing point lower than any other tier-gated entry in this record. - [Kling AI on removal listed as a paid benefit](https://sensedefend.com/statements/kling-lever/): Brand watermark removal appears among the benefits of paid membership. The framing is a reward for subscribing rather than a control over disclosure. - [Runway on removal listed across the paid plans](https://sensedefend.com/statements/runway-lever/): Watermark-free output appears on the paid plans without a single crossing tier named. The lever is a purchase, described at the level of a group. - [HeyGen on removal named at two stated prices](https://sensedefend.com/statements/heygen-lever/): Removal is listed as a feature of the $29 Creator plan and the $49 Pro plan. Two prices are named, which is one more than most entries manage. - [Synthesia on upgrading and generating again](https://sensedefend.com/statements/synthesia-lever/): Basic-plan users are told to upgrade and re-generate the video. The lever is a purchase plus a second render, not a setting on an existing file. - [Hailuo on a flag carried by each request](https://sensedefend.com/statements/hailuo-lever/): The parameter is documented as optional and defaulting to false, which puts the lever in the integration code rather than on the account. - [Wan on a boolean set once per request](https://sensedefend.com/statements/wan-lever/): The parameter is a boolean documented as defaulting to false. The lever sits in the call, and there is no account-level equivalent described. - [Sora on detection tools it describes as internal](https://sensedefend.com/statements/sora-reading-route/): The system card's third provenance bullet names tools for assessing whether a clip came from the vendor's products, and calls them internal. - [ElevenLabs on marks its own detector can find](https://sensedefend.com/statements/elevenlabs-reading-route/): The documentation says the detector finds only watermarks this vendor embedded and will not find those of other platforms. A narrowed claim. - [Nova Reel on credentials public tools can inspect](https://sensedefend.com/statements/nova-reading-route/): The service card says credentials can be inspected by dropping a generated video into publicly available verification tools. A route anybody can take. - [Designer on a site where the metadata is read](https://sensedefend.com/statements/designer-reading-route/): The support article says provenance metadata can be viewed on the Content Credentials site. One named destination, open to anybody holding the file. - [Firefly on a coalition that reads the credentials](https://sensedefend.com/statements/firefly-reading-route/): The page says the vendor co-founded an authenticity initiative in 2019, described as a coalition of over 3,300 members. The readers are the claim. - [AudioSeal on detection down to the sample](https://sensedefend.com/statements/audioseal-reading-route/): The publication presents localized detection at sample level, with a perceptual loss inspired by auditory masking for imperceptibility. - [SynthID on what ordinary handling leaves behind](https://sensedefend.com/statements/synthid-persistence/): The page names cropping, filters, frame-rate changes and lossy compression as modifications the mark is designed to stand up to. - [AudioSeal on buying detection without audible cost](https://sensedefend.com/statements/audioseal-persistence/): The publication describes a perceptual loss inspired by auditory masking, presented as achieving better imperceptibility for the embedded mark. - [Synthesia on a mark a finished video keeps](https://sensedefend.com/statements/synthesia-persistence/): A mark applied in test mode cannot be removed from an existing video; a new request with the flag off is required. Permanence in the awkward direction. - [Hailuo on what an unmodified request produces](https://sensedefend.com/statements/hailuo-default-state/): The parameter is optional and defaults to false, so a request that says nothing about marking produces a file with no label added. - [Wan on what happens when the boolean is left alone](https://sensedefend.com/statements/wan-default-state/): The parameter is a boolean that defaults to false, so a request that ignores it produces video with no corner mark on it. - [SceneMixer on a notice that is already on](https://sensedefend.com/statements/scenemixer-default-state/): The visible watermark is described as on by default, so an operator who changes nothing ships a marked episode without ever deciding to. - [Designer on which images carry the credentials](https://sensedefend.com/statements/designer-scope/): The claim is scoped to all images created with the editing features, which tells a reader what is covered and what is left open. - [ElevenLabs on models it did not build itself](https://sensedefend.com/statements/elevenlabs-scope/): The documentation states that models from other providers offered through the platform are generally not watermarked unless stated otherwise. - [SynthID on a mark spanning a family of products](https://sensedefend.com/statements/synthid-product-scope/): The mark is described as embedded across the vendor's generative consumer products, added at the moment content is created. - [Nova Reel on a version that starts the credentials](https://sensedefend.com/statements/nova-scope/): Credentials based on C2PA are attributed to version 1.1, which makes provenance a function of when a clip was rendered rather than of what it is. - [Sora on the route a visible mark follows](https://sensedefend.com/statements/sora-scope/): The visible watermark is described on videos downloaded from the site or the app, which scopes it to a route rather than to an account. - [Wan on the words the mark actually puts up](https://sensedefend.com/statements/wan-wording/): The reference states the mark carries the text AI Generated in the lower-right corner. A disclosure has to say something, and here it is quoted. - [Kling AI on the single word that names the mark](https://sensedefend.com/statements/kling-wording/): The mark is called a brand watermark on the vendor's own page. One adjective fixes what it is for, and what it is for is not transparency. - [Hailuo on the phrase its parameter is named for](https://sensedefend.com/statements/hailuo-wording/): The parameter is described as adding an AIGC label watermark. The abbreviation is the vocabulary of a different labelling regime. ## Pairs - [SynthID and SceneMixer on the marking column](https://sensedefend.com/pairs/synthid-and-scenemixer/): One entry describes a signal inside the content with no removal documented. The other describes nothing on that layer and a visible notice instead. - [Sora and Pika on what the file itself carries](https://sensedefend.com/pairs/sora-and-pika/): A system card naming a standard applied to every asset, against a pricing page that never mentions the container at all. - [Firefly and ElevenLabs on where a mark lives](https://sensedefend.com/pairs/firefly-and-elevenlabs/): A manifest attached beside the pixels, against a pattern mixed into the sound itself. Two mechanisms with opposite failure modes. - [Nova Reel and Designer on scoping the credentials](https://sensedefend.com/pairs/nova-and-designer/): Two entries adopting the same provenance standard and bounding it differently: one by a version, the other by a named part of the product. - [AudioSeal and SynthID on how precise a mark is](https://sensedefend.com/pairs/audioseal-and-synthid/): One entry claims detection down to the sample; the other claims survival through cropping, filters, frame-rate changes and compression. - [Wan and Firefly on who inherits the marking job](https://sensedefend.com/pairs/wan-and-firefly/): Open weights whose terms ask nothing about marking, against a hosted product that writes credentials into everything it makes. - [SceneMixer and Pika on what moves a visible mark](https://sensedefend.com/pairs/scenemixer-and-pika/): A switch anybody logged in can flick, against a boundary that only a purchase crosses. Same layer, two very different controls. - [Kling AI and Hailuo on which way the default runs](https://sensedefend.com/pairs/kling-and-hailuo/): A brand mark applied unless a paid membership removes it, against a label that appears only when an individual request asks for one. - [Sora and Runway on evidence about a visible mark](https://sensedefend.com/pairs/sora-and-runway/): A described moving watermark tied to two named download surfaces, against a mark inferred from a phrase missing on a free plan's column. - [Synthesia and HeyGen on stating the conditions](https://sensedefend.com/pairs/synthesia-and-heygen/): Two avatar platforms on the same layer: one names conditions including an API test flag and leaves the list open, the other names two prices. - [Wan and SceneMixer on what the notice says](https://sensedefend.com/pairs/wan-and-scenemixer/): One entry quotes the words the mark renders and names the corner. The other names the pipeline stage and never says what appears. - [Firefly and Kling AI on the viewer-facing layer](https://sensedefend.com/pairs/firefly-and-kling/): One page was read for a mark in the frame and records that none is described. The other describes a mark and calls it a brand watermark. - [LTX Studio and Pika on where the boundary sits](https://sensedefend.com/pairs/ltx-and-pika/): Two pricing pages gating the same layer at different heights, and two free-tier cells filled by exactly the same inference from a missing phrase. - [Runway and Synthesia on an omission and a sentence](https://sensedefend.com/pairs/runway-and-synthesia/): One entry's position is read from a phrase missing on a plan table. The other's comes from a support page written to explain the mark. - [SceneMixer and HeyGen on who holds the lever](https://sensedefend.com/pairs/scenemixer-and-heygen/): A switch inside the product against a purchase at a named price. The same layer moves either way, and a different person is the one who moves it. - [Hailuo and Kling AI on a flag against a tier](https://sensedefend.com/pairs/hailuo-and-kling/): A parameter carried by every individual request, against a benefit attached to a membership. Two levers with opposite record-keeping properties. - [Synthesia and Wan on the cost of changing course](https://sensedefend.com/pairs/synthesia-and-wan/): Upgrading and generating the video again, against setting a boolean on the next request. Two removal routes with very different bills. - [SynthID and Pika on removal, sold and not offered](https://sensedefend.com/pairs/synthid-and-pika/): One entry documents no way at all to take its mark off. The other sells removal as a plan feature from a named price upward, on a different layer. - [Nova Reel and Runway on nothing to switch off](https://sensedefend.com/pairs/nova-and-runway/): An entry that applies marking to all output with no removal documented, beside one that lists removal on its paid plans. - [ElevenLabs and Synthesia on marks that stay put](https://sensedefend.com/pairs/elevenlabs-and-synthesia/): No removal documented for an embedded audio signal, against a stated case where a mark cannot be taken off a finished video. - [Sora and Designer on who is allowed to check](https://sensedefend.com/pairs/sora-and-designer/): Detection tools one vendor calls internal, against a named public site that anybody holding the file can open in a browser. The widest gap on one column. - [ElevenLabs and Nova Reel on the reach of a check](https://sensedefend.com/pairs/elevenlabs-and-nova/): A detector limited to one vendor's own marks, against credentials that any public verification tool can inspect. Two routes, two populations. - [Firefly and Sora on who the readers actually are](https://sensedefend.com/pairs/firefly-and-sora/): A coalition given as over 3,300 members, against detection tools a vendor describes as internal. Two accounts of who reads a manifest in practice. - [AudioSeal and ElevenLabs on two kinds of open](https://sensedefend.com/pairs/audioseal-and-elevenlabs/): A published method anybody may implement, against a working detector scoped to one vendor's own marks. Two senses of a route being open. - [Sora and Nova Reel on the same standard, two routes](https://sensedefend.com/pairs/sora-and-nova/): Both write manifests under the same specification. One keeps the checking tools in-house; the other points at publicly available ones. - [SynthID and Synthesia on two senses of permanent](https://sensedefend.com/pairs/synthid-and-synthesia/): A signal built to survive somebody else's handling, against a mark a customer cannot take off a finished file of their own. One word, two values. - [AudioSeal and Firefly on what a rebuild leaves](https://sensedefend.com/pairs/audioseal-and-firefly/): A signal inside the content, against a manifest beside it. Only one of the two survives a pipeline that rewrites the file. - [Designer and SynthID on how wide a claim goes](https://sensedefend.com/pairs/designer-and-synthid/): One claim is bounded by a named set of features; the other spans a whole family of products with no product and no version named anywhere on the page. - [ElevenLabs and Sora on what all really covers](https://sensedefend.com/pairs/elevenlabs-and-sora/): One entry says models from elsewhere in its own product are generally not marked. The other says metadata is on all assets. ## Sections - [The clause record as a CSV](https://sensedefend.com/datasets/): The recorded clauses and vendor statements as a comma-separated file, each row carrying the official source it was read from and the date of that reading. - [EU instruments in the record](https://sensedefend.com/eu/): The transparency article of the AI Act, recorded one paragraph at a time: who each paragraph binds, what it requires, and when it starts to apply. - [Duties by role](https://sensedefend.com/duties/): The transparency obligations sorted by the party they bind, and what the generators tracked here document about meeting them. - [Generators and their marking](https://sensedefend.com/generators/): A page per generator: what its own documentation says about watermarks, metadata and machine-readable marking, with the clause quoted and dated. - [The rows every entry in the record carries](https://sensedefend.com/fields/): The fixed rows behind the tables here: the party a duty binds, what it asks for, what it gives up, and what moves a mark on a product. - [Questions about the text](https://sensedefend.com/questions/): Questions about synthetic-media transparency rules, answered by quoting official text and vendor documentation side by side. - [Terms used in the record](https://sensedefend.com/terms/): Definitions for the vocabulary these pages rely on: the labelling of AI-generated content, and the moderation duties that sit beside it. - [Reading the transparency rules](https://sensedefend.com/learn/): Explainers on the two distinctions this record depends on: provider against deployer, and a visible mark against a machine-readable one. - [Statements filed one column at a time](https://sensedefend.com/statements/): Each page here takes a single generator on a single column of this record and says what its own page states, and what that statement leaves open. - [Pairs that disagree on one column](https://sensedefend.com/pairs/): Two generators set against each other on a single column, chosen because their published positions on that column are far apart rather than similar.