OpenAI's EU Text Watermarks: What Businesses Need to Know

OpenAI announced on 5 October 2026 that it will introduce invisible text watermarks for eligible ChatGPT and Codex users in the European Union over the coming weeks. OpenAI’s announcement

For businesses, this raises a practical question: how should AI-assisted writing fit into an accountable publishing process? A watermark can provide useful evidence about a text’s origin, but the decision to publish still needs an owner.

What is changing?

The rollout covers eligible EU users across all ChatGPT and Codex plans. It is not a global default at launch. API customers worldwide can opt in for selected models, with watermarking off by default. OpenAI’s rollout details

That distinction matters when reviewing a business workflow. A team using ChatGPT directly and a developer building an application through the API should check the behaviour of their respective products rather than assume the same settings apply.

How an invisible text watermark works

The method, called textGrain, creates a statistical pattern while the model chooses its next words or word pieces. A secret key influences those choices, and a detector with that key can later test the text for the pattern. The technical report describes detection using the text and key, without needing the watermark strength used during generation. textGrain technical report

This works through the wording itself, rather than a visible badge attached to a paragraph. The useful comparison is a recognisable pattern spread across a passage: individual words may look ordinary, while the combination provides evidence a detector can examine.

Detection has important limits

OpenAI’s tests show why caution matters. In an evaluation of 400-token English passages, replacing 10% of words with synonyms reduced detection from roughly 92% to 66%, at a target false positive rate of 1%. Shorter passages and constrained subjects such as mathematics were harder to detect. These are evaluation results, not guaranteed detection rates for business documents. OpenAI’s evaluation

A detected watermark does not identify a user or measure their contribution. A missing signal does not prove human authorship. OpenAI’s explanation of detection limits

Businesses should therefore avoid treating a detector result as a verdict on an employee, supplier or writer. Keep the original brief, sources, revision history and approval record available when a document needs scrutiny. Those records help explain the work that actually happened.

Text verification also has restricted access at launch. OpenAI’s developer documentation says approved organisations, including research and academic institutions, can apply; its publicly documented verification API checks images and audio. An existing media-verification integration should not be assumed to accept text. OpenAI’s Content Provenance documentation

Watermarking and disclosure serve different purposes

The European Commission says Article 50’s transparency obligations apply from 2 August 2026. Its guidance distinguishes providers’ machine-readable marking duties from deployers’ obligations to inform people in specified circumstances. European Commission transparency guidance

For text published to inform the public on matters of public interest, Article 50(4) contains a disclosure requirement. It also includes an exception where the content has undergone human review or editorial control and a person or organisation holds editorial responsibility. The precise use case matters; the article should not be read as requiring a visible AI label on every business email or edited paragraph. Article 50

Our practical reading is that organisations need to assess their publishing responsibilities separately from the presence of a technical watermark. A setting in an AI product cannot make that assessment for them.

Four practical steps for businesses

1. Map where AI is used. Identify drafting, editing, translation, customer communications and development workflows. Record which products or integrations each team uses.
2. Give published work a named reviewer. Check claims against sources, correct errors and approve the final wording. Make editorial responsibility explicit.
3. Set clear disclosure expectations. Decide how staff should describe AI assistance to clients and readers, taking account of the publication’s purpose and applicable requirements.
4. Keep evidence of the process. Retain proportionate records of sources, edits and approvals. Use these to investigate concerns rather than relying solely on detection software.

For developers, add provenance behaviour to the questions asked when selecting or updating an AI integration: is watermarking supported, who controls the setting, and how will the application explain its output to users?

The useful next step is to review one real workflow, such as publishing a customer guide, and assign responsibility at each stage. Businesses that need help connecting their AI tools with their working processes can explore our technology consulting services.

Reporting checked on 6 October 2026. Original news coverage: TechCrunch. Product availability and guidance may change as the rollout progresses.