Skip to content
Age verification for websites and platforms

Age verification 2027 data-minimising and audit-proof

An Austrian draft law provides for effective age verification for video platforms with pornographic content from 2027. We implement it in existing and new websites: privacy-friendly, with open standards and without losing guests at the home page.

–days until 31 March 2027Implementation deadline under the Austrian draft

In brief

Under ministerial draft 132/ME, video-sharing platforms aimed at users in Austria are to protect pornographic content by 31 March 2027 with age verification that transmits only the age, keeps platform and verification provider separate and allows no central logging. NOIR DIGITAL builds this check into existing and new websites, provider-neutral and at transparent fixed prices from €690 for the readiness check.

Ministerial draft 132/ME (Ministerialentwurf), consultation closed on 21 September 2026; information as of 16 September 2026. Not legal advice. The draft at the Austrian Parliament (in German)

Platforms with videosDirectly affected

Cam studios, creator and fan platforms, portals with user uploads. For pornographic content the draft requires effective age verification by 31 March 2027.

Services for GermanyAlready mandatory today

In Germany, pornographic content is permitted only in closed user groups. A solution for Austria should cover that at the same time.

Adult shopsAt checkout

For media without a youth rating, shipping needs a reliable age check, ideally right in the order process rather than in front of the whole shop.

Clubs, studios, escortUsually an R18 gateway

Without pornographic content, an age prompt is usually enough. Anyone planning videos, profiles with clips or member areas should prepare now.

What is changing

The timeline to the obligation

The draft amends the Austrian Audiovisual Media Services Act (Audiovisuelle Mediendienste-Gesetz). It applies to video-sharing platforms that address users in Austria, including those based abroad.

  1. 27 July 2026

    Draft sent for consultation

    The government sends the amendment of the Audiovisuelle Mediendienste-Gesetz (AMD-G, Audiovisual Media Services Act) and the KommAustria-Gesetz (KOG, KommAustria Act) out for consultation.

    Source
  2. 21 September 2026

    Consultation ends

    The consultation period has expired. A consultation is usually followed by a government bill and a vote in the Nationalrat (National Council); whether and when the act will be passed was open as of our information (16 September 2026). Details may still change.

    Source
  3. 31 December 2026

    EU proof of age

    The European Commission recommends that member states provide privacy-friendly age verification apps; the European identity wallets follow.

    Source
  4. 1 January 2027

    Planned entry into force

    The new age verification requirements for video-sharing platforms are due to come into force.

    Source
  5. 31 March 2027

    Implementation deadline under the draft

    By then, under the draft, platform providers must use an age verification that meets the new requirements. Fines are provided for infringements after that date.

    Source
  6. 30 June 2028

    Evaluation

    The age verification rules will be reviewed on the basis of a report by the Datenschutzbehörde (Austrian Data Protection Authority).

    Source

Self-check

Does this affect me?

Four questions, a first assessment. It is no substitute for a legal review, but it shows how urgent the topic is for you.

  1. Does your website or app show videos?
  2. Can users, models or creators upload content themselves or create profiles with videos?
  3. Is pornographic content accessible, including as a preview?
  4. Who is the offer aimed at?

Our assessment

Answer the four questions.

Your answers stay in your browser and are only sent once you add the result to an enquiry.

The challenge

What makes implementation difficult

  • The deadline is short

    Between a vote and the deadline of 31 March 2027 provided for in the draft, only a few months remain for choosing a provider, integration, testing and documentation.

  • Hard barriers cost guests

    A check in front of the home page deters visitors and blocks search engines. What matters is where and when the check happens.

  • Guests’ discretion

    Nobody wants to hand over an ID card to visit an adult website. Data on sex life is specially protected under Art. 9 GDPR.

  • A confusing market

    EU app, ID Austria, online identification, bank-based methods, AI estimation: which method meets the requirements, and what does it cost per check?

  • Existing systems

    WordPress, WooCommerce, shop systems or custom portals: the check has to fit in without breaking booking, payment or login.

  • Proof to the authority

    The draft requires that compliance with the requirements is documented. Without documentation, good technology counts for little in proceedings.

Architecture

Double-blind: your site learns only “18+”

The Austrian draft requires a method made up of a registration component and a presentation component with seven properties. This is what the flow looks like and how we implement each requirement.

  1. 1. Once: establish the age

    The guest proves their age to a verification body, for example with ID Austria or online identification. After that the wallet holds only the attribute “at least 18”.

  2. 2. On your site: show only “18+”

    Before protected content the guest releases this proof. Your website checks the signature but learns neither name nor date of birth.

  3. 3. Access granted

    The site sets a short-lived session token. The verification body does not learn that your site asked.

Diagram following § 54e(3a) AMD-G (Austrian Audiovisual Media Services Act) in the draft: verification body and website stay separate, only the age attribute is transmitted.
  • Separation of roles

    Separation between the platform provider and the provider of the age verification method

    Your website talks only to the presentation component. Who originally established the age stays invisible to your site.

  • Not observable

    Non-observability and non-traceability of the presentation of proofs of age

    The verification provider does not learn that your site made a request. Proofs carry no reusable identifier.

  • Collusion-resistant

    Resistance to collusion with the video-sharing platform

    Even if the website and the verification provider pooled their data, no visit could be linked to a person.

  • Control with the guest

    User transparency and user-controlled release

    The guest sees what is transmitted and releases the proof actively. No silent reading in the background.

  • Only “over 18”

    Data minimisation and selective disclosure

    What is transmitted is an age predicate, that is the statement “at least 18”. No name, no date of birth, no copy of an ID.

  • No central log

    Exclusion of central usage logging

    Your servers store only a short-lived, signed session token. There is no list of who was checked when.

  • Open standards

    Interoperability through open standards and standardised age predicates

    We rely on OpenID for Verifiable Presentations and the formats of the EU identity wallets, so that changing provider does not mean a rebuild.

Methods

Which methods come into question

Our assessment based on the state of the draft. Which method suits your offer is defined in the concept, provider-neutral and with reasons.

Age verification methods compared, our assessment
MethodData minimisationFriction for guestsLevel under the draftAvailability
EU age verification app and EUDI walletZero-knowledge proof of “over 18” following the EU blueprint.highmediumdesigned for double-blind operation and data minimisationPilot countries in 2026, wallets from the end of 2026; Austria open
ID Austria (eAusweise)Transmits neither a date of birth nor a name.highmediumgovernment-issued identificationProof of age exists, online connection for websites still to be clarified
Online identification (ID card and selfie or video)Double-blind only with a reusable proof instead of a direct connection.mediummediumstandard of the Online-IDV (Online-Identifikationsverordnung) attainableAvailable today
Bank-based verificationUses an identification the bank has already carried out.mediumlowequivalent depending on the methodDepends on provider and country
AI age estimationUseful as a pre-filter or for areas without pornographic content.mediumlowon its own probably not sufficientAvailable today

Technology

How we build the check in

The check sits where it is needed and nowhere else. Public pages stay fast, free and visible on Google.

  • Two-stage model

    Home page, directions, prices and teasers stay open and indexable, protected by an R18 notice. The hard check appears only in front of content that requires it.

  • Signed session

    After the check we set a short-lived, signed session token with no personal reference. For user accounts, a single check is enough according to the draft.

  • Several routes

    Wallet, ID Austria or online identification: guests choose the route that suits them. If one provider fails, the next takes over.

  • SEO without cloaking

    Search engines see the same public pages as guests. Structured data only for the public part, SafeSearch labelling for the rest.

  • Measurable drop-offs

    How many guests start the check, how many complete it? We measure without cookies and optimise the point where guests drop out.

  • Documentation

    Architecture, provider evidence, data protection impact assessment and test records as a package for your legal adviser and for any inspection.

middleware.ts
// middleware.ts, simplified example of a presentation component
import { NextResponse, type NextRequest } from 'next/server'
import { verifyAgePredicate, presentationRequest } from '@/lib/age'

const PROTECTED = ['/videos', '/members']

export async function middleware(req: NextRequest) {
  // Teasers, prices and directions stay open and indexable.
  if (!PROTECTED.some((p) => req.nextUrl.pathname.startsWith(p))) return NextResponse.next()

  // Only a signed attribute "at least 18": no name, no date of birth.
  const proof = req.cookies.get('av')?.value
  if (proof && (await verifyAgePredicate(proof, { over: 18 }))) return NextResponse.next()

  // Request under OpenID for Verifiable Presentations to the guest's wallet.
  return NextResponse.redirect(await presentationRequest({ claim: 'age_over_18', returnTo: req.nextUrl.pathname }))
}

We integrate into any system that accepts requests:

  • WordPress
  • WooCommerce
  • Next.js
  • PHP and Laravel
  • Shopify
  • custom portals
  • member areas
  • apps via API

Process

Five steps to the finished check

  1. AV readiness check

    Which content, which target countries, which systems? You receive a written assessment with the action needed, questions for your legal adviser and a fixed price for the implementation.

  2. Concept and provider selection

    Define the protected areas, choose methods and providers by data protection, cost per check and availability, and plan fallback routes.

  3. Integration and testing

    Building it into your website or portal, tests on real devices, measuring drop-offs, checking indexing.

  4. Documentation

    Evidence that the requirements are met, a data protection impact assessment as a template, and adjusting the privacy policy together with your legal adviser.

  5. Operation and monitoring

    Updates, provider changes, adaptation to the final version of the law and to the EU wallets, monthly report.

Prices

Transparent fixed prices

All prices net, plus VAT. We pass on the verification costs of the chosen provider without a mark-up; they are stated in the concept before the start.

AV readiness check

€690

fixed price, 5 working days

credited against the project if you commission us

New build with age verification

from €9,900

one-off, 8–14 weeks

Website or portal including the verification flow

Operation and monitoring

from €290

monthly, ongoing

Updates, change of provider, evidence, drop-off rate

Planning a complete website or ongoing support as well? The cost calculator shows the total.

Frequently asked questions

The questions operators are asking us most often right now.

Background in the guide Age verification in Austria from 2027.

What operators are asking now

Does the new obligation also apply to my club or escort website?

The draft is aimed at video-sharing platforms. A classic website without pornographic content and without user videos generally does not fall under it according to the draft; an age prompt remains usual there. What matters is your content and functions. Have your case reviewed legally.

Is an “I am 18” button enough?

Not for video-sharing platforms with pornographic content under the draft. It requires effective control by way of age verification whose reliability matches, or is equivalent to, the standard of the Finanzmarkt-Geldwäschegesetz (Financial Markets Anti-Money Laundering Act) and the Online-Identifikationsverordnung (Online Identification Ordinance).

Do I have to store my guests’ ID data?

No, and you should not. The draft requires data minimisation. Your website receives only the statement “at least 18” and stores a short-lived session token with no personal reference.

What does a single check cost?

That depends on the method, the provider and the volume. In the concept we obtain quotes and pass the verification costs on without a mark-up. Our own services are listed as fixed prices on this page.

Will I lose search engine traffic?

Not if public pages stay open. We check only in front of the content that requires it, and we show search engines the same public pages as guests.

What happens if the draft still changes?

We build on open standards and interchangeable providers. In the support package we adapt the implementation to the version that is passed and to the EU wallets.

Do you work with particular providers?

We work provider-neutrally and choose according to your requirements. Which providers come into question is set out in the concept, with reasons.

Is this legal advice?

No. We implement the technical requirements and supply the documents your legal adviser needs. The legal classification of your offer belongs with a lawyer.

Enquiry

Request an AV readiness check

Describe your offer and your systems. You will receive a reply and a date for the check within one working day.

On request we sign a non-disclosure agreement beforehand.

Topic

What is it about, and what should the website or support achieve for you?

We use your details solely to answer your enquiry. Details in the privacy policy.

Sources

Confidential enquiryCall