/* The un-hydrated SPA shell renders nonsense without JS, so it stays hidden. But hiding it and printing "you need JavaScript" strands the visitor a click away from the thing they came for. Instead the fallback IS a working search: this form is a plain GET to /lite, which server-renders real results with zero client JS. One keystroke sequence, one navigation, real answers — no detour. */ body > div { display: none !important; } /* …except this hide used to apply to /lite itself, so the fallback sent people to a page that showed them the same empty box. The no-JS path was a loop with no exit, and /report — plain HTML on purpose, because someone reporting child sexual abuse material must not be stopped by a failed bundle — never rendered at all. hooks.server.ts marks a route `noscript-ready` when its SSR output stands on its own; (0,1,2) out-specifies the blanket rule above. */ body.noscript-ready > div { display: contents !important; } body.noscript-ready .noscript-fallback { display: none !important; } /* Scroll-reveal starts at opacity 0 and waits for JS to add `.revealed`, which never comes. Un-hiding the shell without this would trade a blank page for an invisible one. */ [data-reveal] { opacity: 1 !important; transform: none !important; transition: none !important; } .noscript-fallback { display: block; max-width: 34rem; margin: 15vh auto 0; padding: 0 1.5rem; font-family: system-ui, sans-serif; line-height: 1.6; color: #e8eaed; } .noscript-fallback h1 { font-size: 2.5rem; margin: 0 0 0.25rem; color: #8fb3d0; } .noscript-fallback p { margin: 0 0 1.5rem; color: #9aa5ad; } .noscript-form { display: flex; gap: 0.5rem; } .noscript-form input { flex: 1; padding: 0.75rem 1rem; font-size: 1rem; color: #e8eaed; background: #22272b; border: 1px solid #39414a; border-radius: 0.5rem; } .noscript-form button { padding: 0.75rem 1.25rem; font-size: 1rem; font-weight: 600; color: #1a1e21; background: #8fb3d0; border: 0; border-radius: 0.5rem; cursor: pointer; } /* Must out-specify `.noscript-fallback p` above (0,1,1) or its `margin: 0 0 1.5rem` silently wins and the note sits flush against the search field. */ .noscript-fallback .noscript-note { margin: 1.5rem 0 0; font-size: 0.875rem; color: #737d85; } .noscript-fallback a { color: #8fb3d0; }

Argand

Search the web without the clutter.

JavaScript is off, so you're getting the text-only view at /lite — it works in Lynx, w3m, ELinks, Tor Browser on Safest, and screen readers. Nothing is missing but the animation.

Back to Argand Ads

Argand Ads

Transparency Report

The whole point of Argand Ads is that there's nothing to hide. Here are the numbers — how many ads ran, how many we turned away and why, and the audit that confirms we track no one. Read the full Ads Policy for the rules behind them.

By the numbers

August 2026

0 Impressions

0 Advertisers

0 Clicks

$0.00 Revenue

Ads we turned away

0 rejected

No ads were rejected this period.

Zero-tracking audit

✓ Verified

Independently confirmed: Argand Ads sets no cookies, builds no profiles, and stores no per-person tracking data. Ads are matched to page context only.

Auditor: Internal Audit
Audit date: November 1, 2024

What we count — and what we never collect

We count, in aggregate

Impressions & clicks (totals — never tied to a person)
Advertisers running, by category
Ads rejected, and the reason for each
Revenue, so you can see how Argand stays free

We never collect

Who you are — no profiles, no dossiers
Cross-site activity or retargeting
Cookies or device fingerprints for ads
Your identity behind any click or impression

Every figure above is anonymous and aggregate. See the Ads Policy for how reviews, refusals, and the zero-tracking audit work.