This report was prepared for cognitum.one. 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 Sep 28, 2026, serial WO-2026-0014. View the certificate
Opportunities
No critical or high-severity issues. That's the bar most sites miss.
Diagnostics
Worth fixing. Not an emergency.
Google API key in the page: verify it is restricted~45 min
A Google API key (AIzaSyD…weyM) is in /assets/index-CvT3N3zy.js. Browser keys for Maps or Firebase belong there, but only when restricted to your domains; unrestricted, anyone can spend your quota.
No "Do Not Sell or Share My Personal Information" link~15 min
Advertising or analytics trackers (Google Tag Manager) 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 postal address for the business~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; 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. 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, UK1 finding
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.
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.
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.
PCI DSS (card networks, via your processor) · Global1 finding
Maximum. Contractual, not statutory: card brands can assess $5,000 to $100,000 per month for non-compliance, passed through by the acquirer or processor.
Usually. Stripe and similar processors handle most of PCI for you, but a page that takes card details over plain HTTP or ships a live secret key breaks the assumptions they rely on.
Applies: Any site that takes card payments. Enforced by private parties.
AI design tells
176 patterns on this page read as AI-generated: AI color palette, Glowing shadow accents, Nested cards. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

AI color palette120×
Purple/violet gradients and cyan-on-dark are the most recognizable tells of AI-generated UIs. Choose a distinctive, intentional palette.
Example: Cyan neon text on dark background
Glowing shadow accents20×
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: Colored box-shadow glow (#1ad5e6) on dark background
Nested cards9×
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
Decorative radial spotlight glow8×
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 "systems-section" (#1ad5e6 a0.06 → transparent) on 1280x1124 surface
Gradient text6×
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
Hairline border with wide shadow5×
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 + 50px shadow blur
Pulsing status dot4×
Small pulsing status dots simulate liveness decoratively. Reserve pulse animation for indicators tied to genuinely live, changing data; a static indicator with clear labeling is honest and calmer.
Example: .dashboard-packet — 5x5px dot with infinite "dashboard-packet" animation
Kicker / eyebrow label above heading2×
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 "The Cognitum dashboard" above h2 "One place to put AI to work."
Oversized hero headline1×
A full-sentence headline set at display size ends up dominating the viewport, leaving no room for anything else above the fold. A punchy one- or two-word headline at that size is fine — the problem is a long headline blown up too large. Set long headlines smaller, or tighten the copy.
Example: 78px h1, 136 chars, 29vh "Ambient IntelligenceAmbient Intelligence· : + · : · + : ·™th"
Image hover transform1×
Scaling or rotating an image on hover is a recurring generated-UI signature. Let imagery sit still, or use a subtler, purposeful interaction.
Example: Tailwind hover transform on <img>
Undersized functional text · quality7×
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 "Cognitum One Intelligence, everywhere" (below 11px floor)
Raster buried under a wash or opacity · quality4×
A background image under a near-opaque gradient wash, or a raster on an element at near-zero opacity, never reaches the screen: the page shows the wash, and the produced texture or photo ships as a compliance token. Let the material show (a tint under 0.9 alpha, a blend mode, an opacity you can see) or remove the file.
Example: <img> at opacity 0 "VS Code for the Web running inside the ruOS desktop"
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 39 chars of body text
Cramped padding · quality2×
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: 0px vertical padding (need ≥4.8px for 16px text)
Line length too long · quality2×
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: ~85 chars/line (aim for <80)
Tiny body text · quality1×
Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.
Example: 11.52px body text
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: <h2> "Ready to exploreproportional intelligence?" followed by <h4> "Platform" (missing h3)
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 (196 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 cognitum.one 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 cognitum.oneTrust page draftPassed audits
(12)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy covers the expected disclosures
1382 words; 14 disclosure checks passed; last updated August 25, 2026.
A consent manager is installed alongside the trackers
Trackers detected (Google Tag Manager) and consent is handled by a consent-management platform. 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 2 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
1 email field with consent or privacy wording on the page.
Served over HTTPS
The final URL uses TLS.
No WCAG A/AA violations found (28 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.
cognitum.one holds Clean Bill of Health WO-2026-0014, 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/cognitum.one)