Webopsy

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

72www.creem.io
82Privacy
92Security
98Legal
40Accessibility
63Design
What the scores mean
Scanned Nov 22, 2026, 7:12 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 2, 2026, serial WO-2026-0249. View the certificate

Opportunities

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

Elements must meet minimum color contrast ratio thresholds (14 elements)~1 h

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <p class="text-xs font-bold uppercase leading-none tracking-[0.05em] text-muted-foreground opacity-70">Terminal</p>

WCAG wcag2aa, wcag143. Web accessibility is enforced under the ADA (US, thousands of private suits a year), Section 508, the European Accessibility Act, the UK Equality Act, and AODA (Ontario).

How to fix this rule

All touch targets must be 24px large, or leave sufficient space (12 elements)~1 h

Ensure touch targets have sufficient size and space Example: <a class="focus-ring rounded-sm leading-snug underline-offset-4 transition-colors hover:text-foreground hover:underline xl:leading-none xl:whitespace-nowrap" hr

WCAG wcag22aa, wcag258. Web accessibility is enforced under the ADA (US, thousands of private suits a year), Section 508, the European Accessibility Act, the UK Equality Act, and AODA (Ontario).

How to fix this rule

Diagnostics

Worth fixing. Not an emergency.

Privacy policy is missing 3 expected disclosures~45 min

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

CCPA/CPRA §1798.120, §1798.135 · COPPA; GDPR Art. 8 · CCPA §1798.130(a)(5) (annual update); good practice everywhere

Open reference

Privacy Policy: missing sections privacy-policy-addendum.md
<!-- Sections your privacy policy at https://www.creem.io/privacy 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. -->

_Last updated: November 22, 2026_

## Sale of personal information

We do not sell personal information. Advertising cookies from Meta Pixel, Google Ads and X Ads can count as "sharing" under California law; you can decline them in the cookie banner or through the "Do Not Sell or Share My Personal Information" link in the footer.

## 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 creem.io on November 22, 2026. Confirm each section matches what you actually do; not legal advice._
Add these 3 sections to your existing policy (https://www.creem.io/privacy), then re-scan; the audit checks for each one by name.
Missing 1 security header~15 min

Not set: X-Content-Type-Options. These defend against clickjacking, MIME sniffing, and protocol downgrade.

Security Headers next.config.js
// next.config.js — Missing on your site: X-Content-Type-Options. The Content-Security-Policy below already allows Google Analytics, Meta Pixel, Google Ads, X Ads; add the domain of anything else you load to script-src or connect-src, then re-scan.
/** @type {import('next').NextConfig} */
const securityHeaders = [
  { key: 'Strict-Transport-Security', value: "max-age=63072000; includeSubDomains; preload" },
  { key: 'X-Content-Type-Options', value: "nosniff" },
  { key: 'X-Frame-Options', value: "SAMEORIGIN" },
  { key: 'Referrer-Policy', value: "strict-origin-when-cross-origin" },
  { key: 'Permissions-Policy', value: "camera=(), microphone=(), geolocation=()" },
  { key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' https://www.googletagmanager.com https://www.google-analytics.com https://connect.facebook.net https://googleads.g.doubleclick.net https://static.ads-twitter.com 'unsafe-inline'; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://www.googletagmanager.com https://www.facebook.com https://www.google.com https://googleads.g.doubleclick.net https://analytics.twitter.com; img-src 'self' data: https: https://www.google-analytics.com https://www.facebook.com https://www.google.com https://googleads.g.doubleclick.net https://t.co https://analytics.twitter.com; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src https://td.doubleclick.net; frame-ancestors 'self'; base-uri 'self'; form-action 'self'" },
];

module.exports = {
  async headers() {
    return [{ source: '/:path*', headers: securityHeaders }];
  },
};
Next.js config (works on Vercel, Netlify, or a Node server). Then re-scan. The Content-Security-Policy is written for what the scan saw (Google Analytics, Meta Pixel, Google Ads, X Ads); if a script or request is blocked after deploy, the browser console names the origin to add.
No "Do Not Sell or Share My Personal Information" link~15 min

Advertising or analytics trackers (Google Tag Manager, Google Ads, Meta Pixel, X Pixel) can count as "sharing" under California law. Businesses over the CCPA thresholds must offer an opt-out link on the homepage. Also expected under several other US state laws.

CCPA/CPRA §1798.120 and §1798.135; Colorado, Connecticut, Virginia, Texas, Oregon privacy acts (opt-out of targeted advertising).

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 security items sit under GDPR Art. 32 (up to 2% of turnover) and the FTC's security enforcement, where the real cost arrives with a breach and its mandatory notifications; 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, UK3 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.

GDPR / UK GDPR, security of processing · EU, EEA, UK1 finding

Maximum. Up to €10 million or 2% of worldwide annual turnover (Art. 83(4)); UK: up to £8.7 million or 2%.

Usually. Fines follow a breach, not a scan. If exposed data reaches users, breach notification to the regulator within 72 hours is mandatory and the fine considers whether the weakness was known.

Applies: Any site processing personal data of people in the EU or UK. Enforced by regulators.

ePrivacy Directive (EU) / PECR (UK), cookies and marketing · EU, UK1 finding

Maximum. Set nationally in the EU; the UK ICO can fine up to £500,000 under PECR.

Usually. Regulators run periodic sweeps of cookie banners; a warning letter is the common first step, with fines reserved for repeat or large-scale cases.

Applies: Sites setting non-essential cookies or sending marketing email to people in the EU or UK. Enforced by regulators.

CCPA / CPRA (California) · United States, California2 findings

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 States2 findings

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, Ontario2 findings

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.

FTC Act §5 (unfair or deceptive practices) and state breach laws · United States1 finding

Maximum. No fixed fine for a first violation; the FTC obtains consent orders with 20-year audit obligations, and violating an order costs over $53,000 per day. State breach-notification laws add per-resident notification costs and, in some states, per-record penalties.

Usually. Enforcement follows an incident. An exposed live key or open database is the incident waiting to happen; the practical cost is fraud on the account plus mandatory notification.

Applies: Any US company holding consumer data. Enforced by regulators.

AI design tells

15 patterns on this page read as AI-generated: Nested cards, Cream / beige palette. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of www.creem.io with the most AI design tells, with each one labeled
The spot with the most tells: Nested cards. Labels are drawn by the detector on the live page.
Nested cards14×

Cards inside cards create visual noise and excessive depth. Flatten the hierarchy — use spacing, typography, and dividers instead of nesting containers.

Example: Card inside card

Cream / beige palette1×

A warm cream or beige page background has become the default "tasteful" AI surface, reached for by reflex. Choose a background that comes from a deliberate palette, not the safe warm off-white.

Example: cream/beige page background rgb(248, 244, 241)

Cramped padding · quality9×

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: <div> "group/card": children flush against border+bg on top (no inset)

Tight line height · quality2×

Line height below 1.3x the font size makes multi-line text hard to read. Use 1.5 to 1.7 for body text so lines have room to breathe.

Example: line-height 1.21x (need >=1.3)

Low contrast text · quality2×

Text does not meet WCAG AA contrast requirements (4.5:1 for body, 3:1 for large text). Increase the contrast between text and background.

Example: browser contrast 1.1:1 median 1.1:1 (need 3:1) via canvas-background-image+alpha "Creem is the money platform for the AI era."

Content overflowing its container · quality1×

Content renders wider than its container, spilling out or forcing a horizontal scrollbar. Let text wrap, constrain widths, or give the region a deliberate scroll affordance.

Example: span.relative.inline-block overflows its box by 24px

Skipped heading level · quality1×

Heading levels should not skip (e.g. h1 then h3 with no h2). Screen readers use heading hierarchy for navigation. Skipping levels breaks the document outline.

Example: <h1> "Build with AISell withCreem" followed by <h3> "Get paid globally" (missing h2)

Full annotated page (30 labels)
Full page of www.creem.io 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 creem.io 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 creem.ioTrust page draft

Passed audits

(9)
Privacy policy is present

A privacy policy link or page was found.

Google Consent Mode defaults to denied

Trackers detected (Google Tag Manager, Google Ads, Meta Pixel, X Pixel) and consent is handled by Google Consent Mode with storage denied until the visitor agrees. Confirm non-Google trackers also wait for consent.

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 6 script bundles it loads.

3 security headers set

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

No mixed content

All referenced resources use HTTPS.

Served over HTTPS

The final URL uses TLS.

30 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.
Also read/pricing /sign-in /contact, for the third-party services on them.
StackNext.js on Vercel, from response headers and the page. The header fix is written for it.
Third partiesAnalytics: Google Analytics. Advertising: Meta Pixel, Google Ads, X Ads. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 2 violation types, 30 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 30 findings in 9.6 s at 1280px.
Duration10.4 s

Or a free weekly re-scan of www.creem.io. 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.

creem.io holds Clean Bill of Health WO-2026-0249, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for creem.io

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/creem.io)](https://webopsy.tech/s/creem.io)

Webopsy badge for creem.io