Can You Get Sued for a Vibe-Coded App? CCPA, CIPA and RLS Explained
By Matt Cullerton, founder of Mavric and Apso
A vibe-coded app can create real legal exposure, but the two dollar figures in a popular TikTok work differently than it implies. The $2,500 is a California privacy penalty that only the state Attorney General can collect. The $5,000 is real private-lawsuit damages under California's wiretapping law, a path the state narrowed nine days before the video posted. The video names no actual lawsuit.
The video, from Chris Ducktate (@ducktate.com), recommends three fixes: legal documents, tracking consent and database access control. All three are sound advice, though the video misstates some details.
Can you get sued for a vibe-coded app?
The video opens with "you can actually get sued before you make your first dollar." It shows a screenshot of an X post claiming a vibe-coded app "can get sued for $100K," but no case name, court or filing appears anywhere in the video. The two numbers it does cite come from California statutes.
What is the $2,500 CCPA penalty?
The video says missing legal documents "can cost up to $2,500 per violation." That figure comes from California Civil Code section 1798.155, the California Consumer Privacy Act penalty provision. A business that fails to cure a violation within 30 days is "liable for a civil penalty of not more than two thousand five hundred dollars ($2,500)" per violation, or $7,500 per intentional violation.
Two details change the picture:
- Who collects it. The penalty comes through a "civil action brought in the name of the people of the State of California by the Attorney General." It is a regulator action, not a user suing you.
- What triggers it. It covers CCPA violations such as failing to give notice when collecting data or ignoring an opt-out request. No provision fines a business for lacking a document called "terms of service."
Consumers can sue under a different section, 1798.150, but only after a data breach caused by a failure to maintain reasonable security. Damages there run $100 to $750 per consumer per incident.
For a sense of real enforcement, the California Privacy Protection Agency fined PlayOn Sports $1.10 million on March 3, 2026. The agency found the company made Californians "click 'agree' to these tracking technologies before they could use their tickets or view PlayOn Sports' websites, without providing a sufficient way to opt-out."
What is the $5,000 CIPA penalty?
The video says session replay violations "can be up to $5,000 per violation." That comes from California Penal Code section 637.2, the civil remedy under the California Invasion of Privacy Act (CIPA). It sets damages at "Five thousand dollars ($5,000) per violation" or three times actual damages. Subsection (c) adds: "It is not a necessary prerequisite to an action pursuant to this section that the plaintiff has suffered, or be threatened with, actual damages."
That is why session replay, chat widgets and ad pixels have drawn class actions under this 1967 wiretapping law. Here the video is right that it is a private lawsuit.
Did California change CIPA in 2026?
It did. Governor Newsom signed SB 690 on September 30, 2026, nine days before the video posted. According to Sidley, it amends section 637.2 so that only the Attorney General can sue over violations of Penal Code 638.51, the pen register provision that had become the favored theory in website tracking suits. It takes effect January 1, 2027, and applies to pending claims filed within two years before that date.
The change is partial. Claims under sections 631 and 632, the wiretapping and eavesdropping provisions, are unaffected, so the $5,000 exposure still exists. SB 690 as first introduced had a broad "commercial business purpose" exemption for most analytics, but that was removed by amendment on July 2, 2026.
Is PostHog session replay on by default?
It is not. The video says to "make sure that that session replay is turned off," then adds "I'm pretty sure it's even turned off by default." The second part is right. PostHog's JavaScript docs say: "To set up session replay in your project, all you need to do is install the JavaScript web library and enable 'Record user sessions' in your project settings."
So the real instruction is not to turn it on until you have consent. PostHog's docs on controlling recordings add that SDK calls "will have no effect if session recordings are disabled in your PostHog Project Settings."
PostHog's privacy controls page masks input fields by default but not general text, and it does not cover consent.
Where does the consent-before-tracking rule come from?
It comes mostly from Europe. Ducktate's own privacy policy says that for EEA visitors, "PostHog and Google Analytics do not load until you select Accept." That is a GDPR-style consent gate. Under GDPR Article 83(5), serious violations can cost "up to 20 000 000 EUR, or in the case of an undertaking, up to 4 % of the total worldwide annual turnover," a ceiling the video does not mention.
What is row-level security?
The video calls it "role-level security." The correct term is Row-Level Security. PostgreSQL's docs say tables "can have row security policies that restrict, on a per-user basis, which rows can be returned by normal queries or inserted, updated, or deleted." You enable it with ALTER TABLE ... ENABLE ROW LEVEL SECURITY, and once on, no rows are visible until a policy allows them.
The video's point about authentication and authorization is correct. Authentication confirms who the user is. Row-level security decides which rows that user can touch.
The risk is real. CVE-2025-48757, published May 30, 2025 with a CVSS score of 9.3 (Critical), describes "An insufficient database Row-Level Security policy in Lovable through 2025-04-15" that let unauthenticated attackers read or write any table in generated sites. Lovable disputes it, saying each customer is responsible for protecting their app's data.
Where can you get free legal templates?
The repo in the video is General-Legal/legal-templates, "Attorney-drafted legal templates for startups and technology companies," released under CC0 1.0. It has twelve templates, including Cookie Notice, Privacy Policy (U.S. Only), Privacy Policy (GDPR Enhanced) and Terms of Use.
The video also points to Ducktate's free Launch Readiness course, an eleven-stage pre-launch checklist marked "not legal advice." It does not cite the $2,500 or $5,000 figures or any statute.
Bottom line
The $2,500 is a CCPA penalty only California's Attorney General can collect, not a private lawsuit for missing documents. The $5,000 is real private damages under CIPA, narrowed by SB 690 but still available for wiretapping claims. PostHog session replay is off until you enable it. Row-level security is the database protection that matters, and CVE-2025-48757 shows what happens without it.
Sources
- General-Legal/legal-templates, GitHub - the template repo
- Legal Templates README - template list
- California Penal Code § 637.2, FindLaw - CIPA damages
- Section 1798.155, Consumer Privacy Act - CCPA penalties
- California's SB 690, Sidley - the 2026 CIPA change
- PostHog JavaScript library usage docs - enabling session replay
- How to control which sessions you record, PostHog - recording controls
- Privacy controls, PostHog - masking defaults
- Row Security Policies, PostgreSQL - row-level security
- CVE-2025-48757, NVD - the Lovable RLS vulnerability
- Ducktate Terms of Service - the creator's terms
- Ducktate Privacy Policy - consent gate for EEA visitors
- Ducktate Learn - free courses
- Launch Readiness, Ducktate - pre-launch checklist
- PlayOn Sports fine, California Privacy Protection Agency - $1.10 million enforcement action
- Article 83 GDPR - GDPR fine ceilings
- Models overview, Anthropic - Claude model lineup
Published October 9, 2026. Based on a TikTok by @ducktate.com. Full video notes (markdown)