Webopsy

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

90reopenly.com
94Privacy
98Security
98Legal
100Accessibility
49Design
What the scores mean
Scanned Nov 22, 2026, 9:46 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 23, 2026, serial WO-2026-2774. View the certificate

Opportunities

No critical or high-severity issues. That's the bar most sites miss.

Nothing here.

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; mentions the right to complain to a regulator. Last updated 7 November 2026.

CCPA/CPRA §1798.120, §1798.135 · COPPA; GDPR Art. 8 · GDPR Art. 13(2)(d)

Open reference

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

## Sale of personal information

We do not sell personal information. Advertising cookies from Google 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.

## 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).

## 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 reopenly.com on November 22, 2026. Confirm each section matches what you actually do; not legal advice._
Add these 3 sections to your existing policy (https://reopenly.com/privacy/), 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. 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

6 patterns on this page read as AI-generated: Decorative radial spotlight glow, Gradient text, Hero eyebrow / pill chip. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of reopenly.com with the most AI design tells, with each one labeled
The spot with the most tells: Gradient text. Labels are drawn by the detector on the live page.
Decorative radial spotlight glow2×

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 "v2-glow" (#22c55e a0.14 → transparent) on 480x480 surface

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 (tracked-caps) "Low-code fine-tuning for LLMs" above h1 "Small models, frontier results."

Kicker / eyebrow label above heading1×

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 "// small beats big" above h2 "A small model tuned to your task beats a giant generalist"

Undersized functional text · quality11×

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 "Faster responses" (below 11px floor)

Tiny body text · quality8×

Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.

Example: 11px body text

Line length too long · quality3×

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: ~86 chars/line (aim for <80)

All-caps body text · quality2×

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 37 chars of body text

Full annotated page (30 labels)
Full page of reopenly.com 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 reopenly.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 reopenly.comTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Cookie language present alongside trackers

Trackers detected (PostHog) and the page mentions cookies. Confirm the banner actually blocks scripts until 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 4 script bundles it loads.

4 security headers set

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

Cookie policy or settings are linked

A cookie policy, notice, or preferences link was found.

No mixed content

All referenced resources use HTTPS.

Email signup shows consent or privacy language

2 email fields with consent or privacy wording on the page.

Served over HTTPS

The final URL uses TLS.

No WCAG A/AA violations found (30 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.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 14 URLs from sitemap.xml.
Also read/pricing /signin, for the third-party services on them.
StackAstro, from response headers and the page. The header fix is written for it.
Third partiesAnalytics: Google Analytics, PostHog. Advertising: Google Ads. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 30 rules passed, 2 need manual review.
Design auditImpeccable browser detector. 30 findings in 6.4 s at 1280px.
Duration7.8 s

Or a free weekly re-scan of reopenly.com. 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.

reopenly.com holds Clean Bill of Health WO-2026-2774, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for reopenly.com

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

Webopsy badge for reopenly.com