In this piece
Vibe coding legal risks in Austria: what can get you sued?
Your app takes payments and records sessions. Both work in the demo. Yet the payment button may use the wrong wording, or the recorder may start before the visitor consents.
Vibe coding legal risks in Austria depend on what your app does, its users and markets. Austrian and EU requirements reach from consent to consumer withdrawal and security. The six viral US-led claims need qualifications before you apply them to an Austrian launch.
Sources checked: 18 November 2026. This engineering guide proposes acceptance checks; no app was audited for it. Have a qualified adviser confirm your product’s obligations, then use the checks to verify their implementation.
Are vibe-coded apps already breaking six laws?
The six claims mix US federal law, California law and a German judgment. A violation depends on the app’s behaviour and the law’s scope. These sources document exposure and disputes. They do not establish a wave of lawsuits against “vibe coders”.
| Viral claim | What the source supports | What an Austrian founder should take from it |
|---|---|---|
| No age field plus one child under 13 means a COPPA violation and $53,000 per child. | COPPA covers child-directed services and relevant general-audience services with actual knowledge of collecting under-13 personal information. The FTC lists up to $53,088 per violation, not an automatic bill per child. General-audience services have no universal duty to investigate everyone’s age. See the FTC’s COPPA FAQ. | Assess your audience and legal basis. Austria’s specific consent threshold is 14, with conditions explained below. US users can add separate duties. |
| Loading Google Fonts means paying every visitor €100. | A Munich court awarded one claimant €100 on 20 January 2022 in 3 O 17493/20. That is a case-specific German civil award. | Check the actual font requests. The award is not an Austrian fine or a Europe-wide compensation tariff. |
| Session replay without consent automatically costs $5,000 for wiretapping. | California claims depend on the provision, interception facts, parties and consent. Penal Code §637.2 provides the greater of $5,000 or three times actual damages for a qualifying violation. $5,000 is not a universal maximum. | For Austria, start with TKG §165(3) and the GDPR. Inspect whether replay starts before a valid choice. |
| No unsubscribe link or postal address means up to $53,000 per email. | The FTC’s CAN-SPAM guide lists up to $53,088 per violating email. Covered commercial messages need a valid postal address and a clear opt-out method; a working return-email method can qualify, so a hyperlink is not the only option. | Austria generally requires permission before direct-marketing email. An unsubscribe option does not replace that analysis. |
| Renewal terms away from the button make every renewal an unconditional gift. | California requires clear disclosures, affirmative consent and cancellation facilities. Its gift provision is not an automatic refund for every subscription-layout defect. Read the California Attorney General’s renewal guidance and Mayron v. Google on the limits of the claimed refund theory. | Apply Austrian checkout, renewal and withdrawal rules separately. Do not import “unconditional gift” as an Austrian legal conclusion. |
| Skip a $6 DMCA agent and you owe up to $150,000 for whatever users upload. | The $6 designation and three-year renewal concern relevant US safe harbours. The Copyright Office says losing a safe harbour does not automatically establish infringement liability. Up to $150,000 per work concerns qualifying willful infringement under §504(c), not a missed-registration fee. | EU hosting services have their own conditional protections and notice duties. US-facing operations may need an additional US analysis. |
The FTC’s September 2026 notice kept its 2025 civil-penalty levels unchanged during 2026. The quoted amounts are legal exposures, not automatic payouts to users. California session-replay litigation also has unsuccessful claims: the Ninth Circuit affirmed dismissal of the pleaded claim in Thomas v. Papa John’s in June 2025. That unpublished decision is no blanket exemption for replay tools.
Which vibe coding legal risks matter in Austria?
Austrian launch obligations follow the app’s processing and transactions. An internal staff tool raises different questions from a consumer subscription. Document the operator, users, target markets, data recipients and money flows before choosing the requirements.
Under the GDPR, particularly Articles 3–5, 8, 13, 25, 28, 32 and 33, the party deciding the purposes and means of processing is the controller. For your app, identify who makes those decisions. The deployed product must reflect its lawful basis, notices and required safeguards. A vendor processing personal data on your behalf needs the Article 28 arrangement. Establish each vendor’s actual role.
Start with a one-page map: what signup collects, which scripts run, who receives data and when marketing starts. Add the payment, renewal, withdrawal and deletion journeys. Our production-readiness checklist covers the broader engineering review. The sections here add specific Austrian legal triggers.
Does an Austrian signup form need an age field?
Austrian law does not impose a birthday field on every signup. DSG §4(4) sets 14 as the relevant age for a child’s own consent when an information-society service is offered directly to the child and processing relies on consent. Below that threshold, GDPR Article 8 requires parental consent or authorisation and reasonable verification efforts.
Read Austria’s DSG §4(4) together with Article 8. The rule governs the specified consent, not a universal minimum app age or contractual capacity. Check other target countries' thresholds too.
Choose proportionate age assurance for the actual audience and risk. The EDPB’s consent guidance, paragraphs 127–137 explains the conditional scope and proportionate verification. Collecting identity documents from every user creates another data-processing decision.
Proposed check: identify each consent-dependent operation and the approved under-age route. Test that bypassing a browser field cannot bypass the server-side rule. An “18+” sentence in the terms does not establish who the service targets.
Are Google Fonts illegal in Austria?
Remote Google Fonts require a case-specific assessment in Austria. The Munich €100 judgment concerned one website in 2022. Austria’s DSB later investigated Google LLC without establishing unlawful processing in that inquiry, although it found shortcomings in the information provided. Assess your own integration and current data flows.
The DSB’s 2023 report, section 4.2.6(3) records the inquiry’s conclusion on 19 October 2023. It concerns the investigated Google Fonts configuration. The authority distinguishes local font delivery and requires case-specific examination of data flows.
Compensation needs its own analysis. In C-300/21, Österreichische Post, the CJEU required infringement, damage and a causal link. Non-material damage has no minimum seriousness threshold, but infringement alone is insufficient.
Our engineering recommendation: self-host the fonts where practical, then inspect the production network trace. A local font file does not help if an imported stylesheet still requests Google. Check consent tools, embedded maps and widgets for their own external requests too; removing one font request does not complete a privacy review.
Can you use session replay without consent?
Ordinary nonessential session replay that stores or accesses information on a user’s device generally needs prior consent in Austria. The assessment reaches beyond cookies. A replay product’s “cookieless” label or input masking does not by itself make recording necessary or remove the GDPR duties for the personal data it collects.
TKG 2021 §165(3) contains the device-access rule and its narrow exceptions. The DSB’s cookie guidance says behaviour-recording and analysis services are generally not technically necessary. Assess necessary session management and ordinary server logging separately.
Verify the implementation in a fresh browser: load the page without touching the banner, reject optional tracking, navigate, then reload. Confirm that no optional replay requests are sent. Grant consent, withdraw it, and repeat the journey, including client-side route changes. Inspect actual requests and payloads rather than trusting the banner’s state.
Use synthetic passwords, recovery codes and sensitive free text to check masking. Inspect the recording for page text, URLs and DOM content, as well as typed fields. Document the provider’s role, retention and transfer route. The DSB’s EU–US Data Privacy Framework guidance explains the recipient-specific transfer route; it does not authorise the underlying tracking.
Can you send marketing emails after signup?
A signup is not blanket permission to send direct-marketing email in Austria. TKG §174 generally requires prior consent, with a narrow existing-customer exception. An unsubscribe link does not supply missing permission for the first message.
Under TKG §174(3)–(5), the existing-customer exception requires all of these conditions:
- You obtained the contact details in connection with a sale or service to that customer.
- You market your own similar products or services.
- You offered an easy, free objection when collecting the address and in every message.
- The recipient has not already refused, including through the relevant ECG/RTR list.
B2B outreach is not generally exempt. In BVwG W295 2318611-1, 27 July 2026, the court rejected arguments that public business contact details implied consent or that an unsubscribe option replaced it.
Proposed check: create an account without marketing consent and inspect the email platform, CRM and delayed jobs. Confirm that it does not enter promotional automation unless the documented existing-customer exception applies. Then opt out from another test account and verify suppression across queued and future campaigns. Keep service messages and promotional sequences distinguishable, and retain the evidence supporting consent or the exception.
What must an Austrian subscription checkout show?
An Austrian consumer checkout must make the price commitment clear before the customer agrees to pay. Recurring costs, duration, cancellation conditions and any minimum commitment need the applicable disclosures. The final action must unambiguously acknowledge payment.
FAGG §4 covers pre-contract information, including recurring costs and contract duration. FAGG §8 requires the specified core information prominently immediately before the customer’s binding payment action. Its button rule gives “zahlungspflichtig bestellen” as an example, or an equally unambiguous formulation. If §8(2) is not met, the consumer is not bound by that contract or declaration.
Test annual and monthly plans, trial conversion, discounts, tax display and mobile layouts. “Continue” can describe navigation; it does not clearly tell a customer that clicking commits them to paying. Preserve the exact offer and terms version accepted by the customer.
Automatic renewal needs an effective reminder
For a fixed-term consumer contract renewed through silence, KSchG §6(1) Z2 requires a special warning and a reasonable opportunity to respond. Distinguish that renewal from recurring charges under an existing indefinite subscription.
In OGH 4 Ob 196/23m, 23 May 2024, an online dating service’s reminder was inadequate. The long subject hid the renewal warning on some devices, and the email did not clearly state the cancellation deadline; the recipient had to follow a link and log in. The judgment does not identify the software as vibe-coded.
Proposed check: simulate the contract calendar and inspect the actual delivered reminder on mobile. Verify the warning, deadline, cancellation route and delivery evidence, not merely the scheduled job result.
Does your app need Austria’s withdrawal function?
For in-scope consumer distance contracts concluded through an online interface after 30 September 2026, Austria requires an accessible online withdrawal function during the withdrawal period. The operative date is 1 October 2026; older references to a planned June start do not reflect the enacted Austrian rule.
FAGG §13a specifies the function, and §20(5) gives the commencement and contractual transition. The product flow must support:
- A prominent, easily accessible function, continuously available throughout the withdrawal period, labelled “Vertrag widerrufen” or an equivalent clear formulation.
- The consumer’s name, details identifying the contract and the electronic channel chosen for the receipt.
- A clear confirmation action, labelled “Widerruf bestätigen” or equivalent.
- A prompt acknowledgement on a durable medium, containing the declaration and its receipt date and time.
Distinguish statutory withdrawal from ending a subscription at its next renewal date. A generic “cancel plan” action may not handle both events correctly.
The FAGG’s §§11, 16 and 18 govern the general 14-day period, relevant service charges and exceptions. Digital content and ongoing services have different conditions. Starting a SaaS subscription does not automatically remove all withdrawal rights. Have the offering classified, then test the approved flow, deadline handling and receipt.
What must an Austrian app do about user uploads?
An Austrian app storing user content should assess the EU Digital Services Act’s hosting rules. Qualifying hosting providers have conditional liability protection tied to knowledge and prompt action, alongside notice-handling duties.
The DSA’s Articles 6, 8 and 16 distinguish the hosting exemption, the absence of a general monitoring obligation and the electronic notice mechanism. Qualification depends on the service’s actual role. The exemption does not legalise the operator’s own infringement.
Proposed check: report a specific test upload, verify that the notice reaches a named owner and confirm that the relevant item can be disabled. Retain the handling record and the decision.
Separately inventory the app’s dependencies, copied code, fonts, images and other assets, then check their actual licences. Our guide to reviewing a vibe-coded app covers how to scope that broader technical review.
What else does the six-law list miss in Austria?
An Austrian launch also needs an operator-information check. Update obligations and digital accessibility deserve their own scope decisions. Establish the product, customer and business category before making them release requirements.
| Austrian requirement | Scope that matters | Implementation evidence to retain |
|---|---|---|
| Operator information | ECG §5 requires covered providers' identity, geographic address and direct contact details, including email, to be continuously, easily and directly accessible. Other details apply where relevant. | Actual operator details and working legal-information links on mobile, checkout and logged-out pages. A privacy policy does not replace the imprint. |
| Updates and maintenance | VGG §1 defines scope and expressly extends §7 to relevant B2B contracts. VGG §7 concerns updates necessary to maintain conformity, including security. The period depends on the supply model; it is not a universal two-year SaaS rule. | A maintenance owner, vulnerability intake, supported components and a working update path. Retain evidence of updates after launch. |
| Digital accessibility | The BaFG has covered listed services, including consumer ecommerce, since 28 June 2025. Service-providing microenterprises are exempt: fewer than ten employees and annual turnover or annual balance-sheet total no more than €2 million. This is not an exemption for every product business or an obligation covering every app. | A scope decision, then applicable keyboard, assistive-technology, authentication, form-error and payment checks. An automated accessibility score alone does not establish compliance. |
If your product falls within the Cyber Resilience Act, review its separate scope and reporting duties with the CRA reporting playbook.
Which checks should block the launch?
We would block the affected feature when it fails a confirmed legal requirement. These proposed QA checks turn agreed requirements into release evidence; passing them is not a compliance certificate. Use synthetic data in a controlled environment.
| Journey | Proposed acceptance check | Retained evidence |
|---|---|---|
| Signup and minors | The approved audience and parental-consent route are enforced where applicable, including requests that bypass the UI. | Audience decision, lawful-basis map and positive/negative test results. |
| Fonts and replay | Actual requests match the approved data-flow map; optional recording stays off before consent, after rejection and after withdrawal. | Build identifier, synthetic network capture and consent-state results. |
| Marketing | No-consent accounts stay out of promotional journeys unless a documented exception applies; opt-outs reach every sender. | Permission record, suppression result and queued-message checks. |
| Checkout | All plans and locales show the agreed commitment before a clear payment action. | Offer version, desktop/mobile screenshots and test order. |
| Renewal | The actual reminder clearly states the consequence and deadline and reaches the agreed delivery route. | Contract calendar, rendered email and delivery record. |
| Statutory withdrawal | An eligible customer can submit the declaration during the period and promptly receive a durable receipt. | Contract identifier, receipt timestamp and full flow result. |
| User uploads | A usable notice reaches an owner who can act on the identified content. | Test notice, handling record and removal/access result. |
| Operations and access | Applicable update, accessibility and operator-information requirements have an owner and tested implementation. | Maintenance plan, assistive-technology findings and disclosure checks. |
Attach an owner and retest condition to each finding. A change to the email provider, payment flow, analytics configuration or subscription terms can invalidate earlier evidence even when the app’s main screens look unchanged.
Who should check the law and the implementation?
Your legal adviser should confirm applicability and wording; product and engineering should implement the resulting behaviour; QA should verify it against the agreed requirements. Give everyone the same customer journeys, data-flow map and contract variants.
We would review signup, data collection, marketing and payment before exposing those flows to real users, then assign maintenance and repeat relevant checks after material changes. Wavect’s software QA service can help turn the agreed behaviour into tests and reproducible findings. For a scoped review, bring your signup, checkout and cancellation flows, together with the requirements your adviser has confirmed.
If the released app includes AI functionality, classify that system separately. The RTR explanation of the AI-system definition concerns what a system does; using an assistant to write ordinary application code does not by itself settle that classification.
