Webopsy

This report was prepared for songflip.link. It shows the top findings; the full report includes every issue and its fix.

90songflip.link
94Privacy
98Security
98Legal
90Accessibility
0Design
What the scores mean
Scanned Nov 22, 2026, 11:33 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 9, 2026, serial WO-2026-1368. View the certificate

Opportunities

These are the issues most likely to matter to a regulator, an app store, or an attacker. Fix them first.

Diagnostics

Worth fixing. Not an emergency.

Privacy policy is missing 2 expected disclosures~30 min

Not found in the policy text: states whether data is sold or shared for advertising; addresses children's data. No last-updated date found.

CCPA/CPRA §1798.120, §1798.135 · COPPA; GDPR Art. 8

Open reference

Privacy Policy: missing sections privacy-policy-addendum.md
<!-- Sections your privacy policy at https://songflip.link/privacy-policy.html does not have.
     Paste each under a heading of its own, in the order shown, and update the
     date at the top of the policy. -->

## Sale of personal information

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

## Children

The Service is not directed to children under 13 (or the minimum age in your
country), and we do not knowingly collect their data. If you believe a child has
provided us information, contact us and we will delete it.

---
_Generated from what the scanner observed on songflip.link on November 22, 2026. Confirm each section matches what you actually do; not legal advice._
Add these 2 sections to your existing policy (https://songflip.link/privacy-policy.html), then re-scan; the audit checks for each one by name.
No security.txt for vulnerability reports~5 min

A /.well-known/security.txt file tells researchers how to report a problem before it becomes a breach. Two lines: Contact and Expires.

RFC 9116; expected by many bug-bounty and disclosure norms.

What these findings expose you to

For scale: the privacy items fall under GDPR's top tier (up to 4% of turnover; small-business fines for missing notices and cookie consent have run from the low thousands of euros upward) and, for California users, CalOPPA at up to $2,500 per violation and CCPA at roughly $2,500 to $7,500 per violation once you pass its thresholds; the accessibility violations are the kind that draw private ADA suits, thousands a year, usually settled for $5,000 to $25,000 plus the plaintiff's fees. In practice the first step is almost always a complaint and a notice with a deadline; the cost comes from ignoring it. These are published maximums and reported ranges, not a prediction.

GDPR / UK GDPR, transparency and consent · EU, EEA, UK2 findings

Maximum. Up to €20 million or 4% of worldwide annual turnover, whichever is higher (Art. 83(5)); UK: up to £17.5 million or 4%.

Usually. A complaint to a data-protection authority, then a notice with a deadline to fix. Published fines against small businesses for missing notices and cookie consent have run from the low thousands of euros upward; the largest cookie-consent fines have been in the tens of millions.

Applies: Any site with users in the EU or UK, regardless of where the company is. Enforced by regulators.

CCPA / CPRA (California) · United States, California1 finding

Maximum. About $2,500 per violation and about $7,500 per intentional violation or one involving a minor, inflation-adjusted each year; each affected consumer can count as a violation.

Usually. A notice from the California Privacy Protection Agency or Attorney General; the 30-day cure period was removed in 2023. Enforcement has focused on larger companies, but the thresholds catch many startups once they pass roughly $26 million in revenue or 100,000 consumers.

Applies: Businesses over the CCPA thresholds with California users. Many early-stage sites are below them; the privacy-policy duty under CalOPPA applies to all. Enforced by regulators.

CalOPPA (California Online Privacy Protection Act) · United States, California1 finding

Maximum. Up to $2,500 per violation, enforced through California's unfair-competition law after a 30-day notice.

Usually. A notice to post a compliant policy within 30 days. Applies to any commercial site reaching Californians, with no size threshold.

Applies: Any commercial site or app collecting personal information from California residents. Enforced by regulators.

PIPEDA / Quebec Law 25 · Canada1 finding

Maximum. Quebec Law 25: administrative penalties up to CA$10 million or 2% of worldwide turnover, and penal fines up to CA$25 million or 4%. PIPEDA itself currently relies on findings and court orders.

Usually. A complaint to the Privacy Commissioner or Quebec's CAI, an investigation, and a public finding; Quebec has begun issuing monetary penalties.

Applies: Any organisation collecting personal information from people in Canada; Law 25 for Quebec residents. Enforced by regulators.

ADA Title III and California's Unruh Act (web accessibility) · United States1 finding

Maximum. The ADA carries no fixed fine for private suits, but the defendant typically pays the plaintiff's attorney fees; California's Unruh Act adds statutory damages of $4,000 per violation. DOJ actions can carry civil penalties up to $75,000 for a first violation.

Usually. Thousands of private lawsuits a year, most against small and mid-sized sites, usually settled for roughly $5,000 to $25,000 plus fees. Fixing the automated violations is the cheapest defence.

Applies: Any business website in the US; California residents can sue under Unruh. Enforced by regulators and private plaintiffs.

European Accessibility Act / UK Equality Act / AODA · EU, UK, Ontario1 finding

Maximum. Set by each EU member state since June 2025; AODA penalties up to CA$100,000 per day for corporations; UK Equality Act claims are private.

Usually. Complaints and compliance orders first; fines are reserved for refusal to fix.

Applies: Consumer-facing digital services in the EU; Ontario organisations; UK service providers. Enforced by regulators and private plaintiffs.

AI design tells

127 patterns on this page read as AI-generated: AI color palette, Glowing shadow accents, Icon tile stacked above heading. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of songflip.link with the most AI design tells, with each one labeled
The spot with the most tells: Gradient text, AI color palette. Labels are drawn by the detector on the live page.
AI color palette96×

Purple/violet gradients and cyan-on-dark are the most recognizable tells of AI-generated UIs. Choose a distinctive, intentional palette.

Example: Cyan gradient background

Glowing shadow accents12×

Colored glow shadows — a zero-offset chromatic halo (box- or text-shadow) on any background, or any colored blurred shadow on a dark background — are the default "cool" look of AI-generated UIs. Use neutral elevation shadows and subtle, purposeful lighting instead.

Example: Zero-offset box-shadow glow (#10b981)

Icon tile stacked above heading9×

A small rounded-square icon container above a heading is the universal AI feature-card template — every generator outputs this exact shape. Try a side-by-side icon and heading, or let the icon sit in flow without its own container.

Example: 52x52px icon tile above h3 "0 Clicks & Direct Playback"

Kicker / eyebrow label above heading5×

A tiny tracked uppercase or small-caps label sitting as its own block directly above a heading is banned outright, repeated or not. Generated kickers never earn their place: the heading carries its own weight. Delete the label and let the heading speak; if the words matter, work them into the heading or the body.

Example: kicker "Simple & Automatic" above h2 "Set it once – enjoy music forever"

Gradient text2×

Gradient text is decorative rather than meaningful — a common AI tell, especially on headings and metrics. Use solid colors for text.

Example: background-clip: text + gradient

Hero eyebrow / pill chip1×

A tiny uppercase letter-spaced label sitting immediately above an oversized hero headline — or the same shape rendered as a pill chip — is now the default AI SaaS hero. Drop the eyebrow, integrate the kicker into the headline, or run it as a navigation breadcrumb instead.

Example: eyebrow chip (accent-bold) "Independent & Open Source • Available fo" above h1 "SongFlip: Tap shared music links.Play immediately in YOUR pl"

Decorative radial spotlight glow1×

A soft, low-opacity accent-colored radial gradient fading to transparent, dropped behind a hero or section as a "spotlight." It is a reflex AI decoration — the translucent cousin of the saturated radial halo. Let the surface stand on its own, or light the composition with a deliberate material accent rather than a floating colored haze.

Example: radial-gradient spotlight glow "mockup-ambient-glow" (#10b981 a0.22 → transparent) on 380x480 surface

Hairline border with wide shadow1×

A hairline border paired with a wide, diffuse shadow is a recurring generated-UI signature. Commit to one — a defined edge or a soft elevation — rather than both at once.

Example: 1px border + 60px shadow blur

Layout property animation · quality8×

Animating width, height, padding, or margin causes layout thrash and janky performance. Use transform and opacity instead, or grid-template-rows for height animations.

Example: transition: width

Line length too long · quality7×

Text lines wider than ~80 characters are hard to read. The eye loses its place tracking back to the start of the next line. Add a max-width (65ch to 75ch) to text containers.

Example: ~96 chars/line (aim for <80)

Undersized functional text · quality4×

Interactive and content-bearing UI text (links, buttons, nav items, labels, table cells, meta rows, timecodes) below 11px is a legibility failure, not a style choice. WCAG sets no absolute pixel floor, but functional text under 11px is a defensible quality bar: it fails on high-DPI and small viewports and it degrades tap and read targets. The 11px floor holds even inside a footer; only non-interactive legal smallprint gets the softer 10px floor. Being ON the DESIGN.md size ramp does not exempt a value here: adding 8px to the ramp launders the token but not the legibility problem, and that is exactly the escape hatch this rule closes. Exempts sup/sub, visually-hidden (sr-only) text, and code/terminal contexts. Decorative letterspaced micro-labels are still functional and stay in scope.

Example: 10px functional text "50% OFF" (below 11px floor)

Cramped padding · quality1×

Text is too close to the edge of its container. Two shapes: (1) an element with its own text where the padding is too low for the font size, and (2) a wrapper with text-bearing children and near-zero padding against a visible boundary (border, outline, or non-transparent background) — children land flush against the boundary line. Add at least 8px (ideally 12–16px) of padding inside bordered, outlined, or colored containers.

Example: 3px vertical padding (need ≥4.0px for 12.48px text)

All-caps body text · quality1×

Long passages in uppercase are hard to read. We recognize words by shape (ascenders and descenders), which all-caps removes. Reserve uppercase for short labels and headings.

Example: text-transform: uppercase on 31 chars of body text

Same text repeated inside one container · quality1×

The same literal text rendered three or more times in structurally different spots inside a single card or panel is redundant messaging — usually a status or label wired into every slot of a template. Say it once, in the slot where it matters most.

Example: "PLAY" rendered 6× in distinct spots inside div.share-card-mockup

Full annotated page (149 labels)
Full page of songflip.link with every design tell labeled

This report is complete and free, and true as of the scan time above. The next deploy, a tag added in Tag Manager or a redesigned footer can change it. Watch re-checks songflip.link every day and after every deploy, emails you the moment something regresses, keeps the dated record, and gives you a trust page your customers can check.

Watch songflip.linkTrust page draft

Passed audits

(9)
Privacy policy is present

A privacy policy link or page was found.

No third-party trackers detected

None of the common analytics or marketing pixels were found in the page.

Terms of service are present

A terms page or link was found.

Public contact or business identity present

A contact email, contact page, or mailto link was found.

No secret keys in the page or its scripts

No server-side keys (Stripe secret, OpenAI, Anthropic, AWS, GitHub, Slack, SendGrid, Supabase service_role, private keys) in the page or the 2 script bundles it loads.

4 security headers set

Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options

No mixed content

All referenced resources use HTTPS.

Served over HTTPS

The final URL uses TLS.

27 accessibility rules passed

Rules axe-core tested and found no violations for.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 200 URLs from sitemap.xml.
Third partiesAnalytics: Segment. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 1 violation types, 27 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 149 findings in 12.4 s at 1280px.
Duration14.6 s

Or a free weekly re-scan of songflip.link. An email only when a new issue appears.

Only change alerts, unsubscribe in any email. Privacy.

Share this report.

The link is public and shows the same free view you see here; nothing about the reader is recorded.

Post on XShare on LinkedIn

The certificate.

songflip.link holds Clean Bill of Health WO-2026-1368, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for songflip.link

Put your score on your README.

An embeddable badge that re-checks weekly. Builders use it the way they use a CI badge: proof the boring stuff is handled.

Markdown
[![Webopsy](https://webopsy.tech/badge/songflip.link)](https://webopsy.tech/s/songflip.link)

Webopsy badge for songflip.link