This report was prepared for whyleft.com. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
No change since the scan on Nov 14, 2026.
Clean bill of health since Oct 16, 2026, serial WO-2026-2123. View the certificate
Opportunities
No critical or high-severity issues. That's the bar most sites miss.
Diagnostics
Worth fixing. Not an emergency.
Privacy policy is missing 6 expected disclosures~2 h
Not found in the policy text: states a legal basis (eea/uk users); mentions international transfers; covers cookies and trackers; addresses children's data; mentions the right to complain to a regulator; carries a last-updated or effective date. No last-updated date found.
GDPR Art. 13(1)(c)-(d) · GDPR Art. 13(1)(f) · ePrivacy Directive; PECR; CCPA (tracking technologies) · COPPA; GDPR Art. 8 · GDPR Art. 13(2)(d) · CCPA §1798.130(a)(5) (annual update); good practice everywhere
<!-- Sections your privacy policy at https://whyleft.com/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_
## Legal bases (EEA/UK users)
Where the GDPR/UK GDPR applies, we rely on: performance of a contract with you
(providing the Service), your consent (marketing email; you may withdraw it at any time), our legitimate interests in
operating and securing the Service, and compliance with legal obligations.
## International transfers
Our hosting provider may store information outside your country. Where information about people in the EEA or UK is transferred outside the EEA or UK, we rely on Standard Contractual Clauses or an adequacy decision.
## Complaints
If you are unhappy with how we handle your information, tell us first at [[email protected]]. You may also lodge a complaint with your data-protection authority (in the UK, the ICO; in the EEA, the supervisory authority of your country).
## Cookies
We use only the cookies needed to run the site. You can block cookies in your browser; the site will still work.
## 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 whyleft.com on November 22, 2026. Confirm each section matches what you actually do; not legal advice._No legal entity name or address~5 min
Sites that take money or serve EU/German users are expected to show who runs them and where. It also unblocks Stripe and app-store reviews.
GDPR Art. 13(1)(a) (controller identity); German TMG §5 Impressum; EU e-Commerce Directive Art. 5; consumer-protection rules in most countries.
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. 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.
AI design tells
19 patterns on this page read as AI-generated: AI color palette, Decorative radial spotlight glow, Hairline border with wide shadow. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

AI color palette7×
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
Decorative radial spotlight glow6×
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 "absolute" (#1d9e75 a0.16 → transparent) on 1311x1450 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 + 64px shadow blur
Glowing shadow accents1×
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 (#1d9e75)
Overused font1×
Inter, Roboto, Fraunces, Geist, Plus Jakarta Sans, and Space Grotesk are used on so many sites they no longer feel distinctive. Each new wave of AI-generated UIs converges on the same handful of faces. Choose a face that gives your interface personality.
Example: Primary font: geist (100% of text)
Em-dash overuse1×
Em-dash saturation in body copy is an AI cadence tell. Advisory only: humans use em-dashes legitimately, so this fires only on saturation — at least 8 em-dashes (— or --) at a density near one per 500 characters of body text — never on a long article that uses a few. Prefer commas, colons, periods, or parentheses.
Example: 11 em-dashes in body text
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(245, 243, 238)
Auto-scrolling marquee1×
Continuously auto-scrolling content demands attention it has not earned and hides half its content at any moment. Reserve motion for content that changes; let readers move at their own pace.
Example: .launch-marquee-track — infinite horizontal loop animation "launch-marquee"
Line length too long · quality12×
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: ~98 chars/line (aim for <80)
Tight line height · quality1×
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.05x (need >=1.3)
Layout property animation · quality1×
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: height
Full annotated page (33 labels)

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 whyleft.com 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 whyleft.comTrust page draftPassed 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 6 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.
No WCAG A/AA violations found (26 rules passed)
axe-core found no violations of the WCAG 2.2 A/AA rules it can test automatically. Automated checks cover roughly a third of WCAG; manual review is still needed for the rest.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
whyleft.com holds Clean Bill of Health WO-2026-2123, last checked November 22, 2026. Open it for the seal and what it verified.
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.
[](https://webopsy.tech/s/whyleft.com)