/* Shared stylesheet for the static marketing pages served from public/:
   /privacy, /about, /terms. Extracted from privacy.html once there were three
   of them rather than copied a third time — one place to change the design,
   and one place for a mistake to show up.

   Self-hosted like everything else here. These pages load no font, script or
   stylesheet from any other origin, and the CSP in next.config.ts enforces it. */

:root{
  --bg:#0a0c10; --bg-soft:#0e1116; --card:#14171c; --card-elev:#1a1e24;
  --fg:#f3f5f8; --muted:#8e95a1;
  --lime:#c4ff3d; --lime-soft:rgba(196,255,61,.10); --lime-glow:rgba(196,255,61,.3);
  --danger:#ff5468; --warning:#ffb547; --success:#00d97e;
  --border:#22262e; --border-strong:#2c313a;
  --r:18px; --r-sm:12px; --maxw:760px;
  --font:'Geist',system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif;

  --nav-h:70px;
  /* Minimum comfortable tap target. Everything a thumb has to hit clears it. */
  --tap:44px;
}
*{box-sizing:border-box;margin:0;padding:0}
html{scroll-behavior:smooth;-webkit-text-size-adjust:100%}
body{background:var(--bg);color:var(--fg);font-family:var(--font);
  line-height:1.65;letter-spacing:-.011em;-webkit-font-smoothing:antialiased}
a{color:var(--lime);text-decoration:none}
a:hover{text-decoration:underline}
.wrap{max-width:var(--maxw);margin:0 auto;padding:0 22px}

/* The floating pill, identical to the landing page's. Sticky at every width,
   so it stays reachable for the whole of a long article rather than only at
   the top. The outer <nav> is the sticky box and carries the inset; the pill
   itself is .nav-in, which is why the gap above it survives scrolling. */
nav{position:sticky;top:0;z-index:50;padding:12px 14px 0}
.nav-in{display:flex;align-items:center;justify-content:space-between;gap:12px;
  min-height:58px;max-width:var(--maxw);margin:0 auto;padding:7px 7px 7px 16px;
  border-radius:999px;border:1px solid var(--border-strong);
  background:rgba(20,23,28,.88);backdrop-filter:blur(16px) saturate(140%);
  box-shadow:0 10px 30px -18px rgba(0,0,0,.9)}
.brand{display:flex;align-items:center;gap:10px;font-weight:700;font-size:17px;
  letter-spacing:-.02em;color:var(--fg);min-height:var(--tap)}
.brand:hover{text-decoration:none}
.brand .mark{width:30px;height:30px;flex:0 0 auto}
.nav-back{color:#0a0c10;font-size:14px;font-weight:700;
  display:inline-flex;align-items:center;min-height:var(--tap);
  padding:0 18px;border-radius:99px;background:var(--lime);
  box-shadow:0 10px 24px -12px var(--lime-glow)}
.nav-back:hover{text-decoration:none;filter:brightness(1.08)}

/* Header. A soft lime glow behind the title, not a lime ground: a full band
   read as a flat yellow field on a phone, where almost nothing covers it. */
header{position:relative;z-index:0;padding:46px 0 30px}
/* Held inside the content column on purpose. Bleeding it past the edges with
   negative insets put a horizontal scrollbar back on the document, and the only
   way to hide that is an overflow rule on <html> or <body> -- which on iOS
   Safari turns the body into a scroll container and breaks momentum scrolling.
   A glow that lines up with the text reads better anyway. */
header::before{content:"";position:absolute;z-index:-1;pointer-events:none;
  top:calc(-1 * var(--nav-h));bottom:-40px;left:0;right:0;
  background:radial-gradient(76% 62% at 28% 0%,rgba(196,255,61,.14),transparent 74%)}

.eyebrow{color:var(--lime);font-size:12px;font-weight:700;letter-spacing:.12em;
  text-transform:uppercase;margin-bottom:10px}
h1{font-size:clamp(29px,5.4vw,42px);line-height:1.12;letter-spacing:-.03em;font-weight:800;
  color:var(--fg)}
.lede{color:var(--muted);font-size:17px;margin-top:14px}
.updated{color:var(--muted);font-size:13.5px;margin-top:18px;
  padding-top:16px;border-top:1px solid var(--border)}

main{padding-bottom:70px}
h2{font-size:22px;line-height:1.25;letter-spacing:-.02em;font-weight:700;
  margin:44px 0 12px;scroll-margin-top:76px}
h3{font-size:16.5px;font-weight:650;margin:26px 0 8px}
p{margin:12px 0;color:#dfe3e9}
ul{margin:12px 0 12px 20px}
li{margin:7px 0;color:#dfe3e9}
strong{color:var(--fg);font-weight:650}

.callout{background:var(--card);border:1px solid var(--border-strong);
  border-radius:var(--r);padding:18px 20px;margin:22px 0}
.callout p:first-child{margin-top:0}
.callout p:last-child{margin-bottom:0}
.callout.warn{border-color:rgba(255,181,71,.35);background:rgba(255,181,71,.06)}
.callout.good{border-color:rgba(196,255,61,.28);background:var(--lime-soft)}
.tag{display:inline-block;font-size:12px;font-weight:700;letter-spacing:.04em;
  text-transform:uppercase;padding:3px 9px;border-radius:99px;margin-bottom:10px}
.tag.warn{background:rgba(255,181,71,.16);color:var(--warning)}
.tag.good{background:rgba(196,255,61,.16);color:var(--lime)}

table{width:100%;border-collapse:collapse;margin:18px 0;font-size:14.5px;display:block;overflow-x:auto}
th,td{text-align:left;padding:11px 12px;border-bottom:1px solid var(--border);vertical-align:top}
th{color:var(--muted);font-weight:600;font-size:12.5px;text-transform:uppercase;letter-spacing:.03em;white-space:nowrap}
td:first-child{color:var(--fg);font-weight:550;white-space:nowrap}
/* A cell whose entire content is a link ("Never", "Fully") was tappable only
   across its text, 16px tall, inside a cell that looked like the target. The
   link takes over the cell's padding, so the whole cell is the link and at
   least a tap target tall. Links inside a sentence ("Speak or type") are not
   tagged and stay inline. */
td.cl{padding:0}
td.cl>a{display:block;min-height:var(--tap);padding:11px 12px}

footer{border-top:1px solid var(--border);padding:20px 0 46px;color:var(--muted);font-size:14px}
/* Footer links were 23px tall, which is a comfortable click with a mouse and a
   miss with a thumb. The row gap shrinks to compensate for the taller targets. */
.foot-links{display:flex;gap:4px 18px;flex-wrap:wrap;margin-bottom:6px}
.foot-links a{display:inline-flex;align-items:center;min-height:var(--tap)}

@media (max-width:560px){
  header{padding:36px 0 26px}
  h2{margin-top:36px}
  .wrap,.nav-in{padding-left:18px;padding-right:18px}
  .lede{font-size:16px}
  .answer{padding:18px 18px}
  .answer p{font-size:16px}
  /* Full-width so the thumb cannot miss it, and so it reads as the one action
     on the screen rather than a link that happens to be a pill. */
  .cta{display:flex;width:100%}
  .cta-band{padding:22px 18px}
  table{font-size:13.5px}
  th,td{padding:10px}
  td.cl>a{padding:10px}
  /* th and td:first-child do not wrap, which suits a desktop. On a phone it
     pushed 8 of the 17 tables wider than the screen, by 5 to 110px, so the
     last column, usually Finly's, sat behind a sideways scroll. Letting them
     wrap here fits every table at 375; the scroll stays as a safety net for
     anything genuinely unbreakable. */
  th,td:first-child{white-space:normal}
}

/* ─────────────────────────────────────────────────────────────────────────
   SEO landing pages (/khata-app, /expense-tracker-without-bank-login, etc.)

   These share the legal pages' shell — nav, wrap, headings, callouts, table,
   footer — and add only what a landing page needs that a policy page does not:
   an answer block, a CTA, and an FAQ.

   The answer block is not decoration. Each page opens by answering its query
   in one paragraph before it sells anything, because that paragraph is what a
   featured snippet and an AI assistant lift. Burying the answer under a pitch
   is how a page ranks for nothing.
   ───────────────────────────────────────────────────────────────────────── */

/* The answer block: raised, with a lime hairline so the one passage a search
   engine is most likely to lift is also the one the eye lands on first. */
.answer{position:relative;background:var(--bg-soft);
  border:1px solid rgba(196,255,61,.2);border-radius:var(--r);
  padding:22px 24px;margin:26px 0;
  box-shadow:0 18px 40px -18px rgba(0,0,0,.85)}
.answer p{margin:0;font-size:17px;color:var(--fg);line-height:1.6}
.answer p + p{margin-top:12px}

.cta{display:inline-flex;align-items:center;justify-content:center;gap:8px;
  background:var(--lime);color:#0a0c10;font-weight:700;font-size:15.5px;
  letter-spacing:-.01em;padding:0 24px;min-height:50px;border-radius:99px;margin-top:16px}
.cta:hover{text-decoration:none;filter:brightness(1.08)}
.cta-note{color:var(--muted);font-size:13.5px;margin-top:11px}

.cta-band{background:var(--card);border:1px solid var(--border-strong);
  border-radius:var(--r);padding:26px 24px;margin:44px 0 8px;text-align:center}
.cta-band h2{margin:0 0 8px;font-size:20px}
.cta-band p{margin:0 0 16px;color:var(--muted)}

.faq h3{margin:24px 0 6px;font-size:16.5px;color:var(--fg)}
.faq h3:first-of-type{margin-top:12px}
.faq p{margin:6px 0 0}

/* Related pages. Internal links between these six are half the reason they
   work: each one is a different query for the same product, and a crawler that
   finds one should find the rest without going back to the sitemap. */
/* minmax(220px,1fr) collapses to one column on its own below 462px, so this
   needs no breakpoint of its own. */
.related{display:grid;grid-template-columns:repeat(auto-fit,minmax(220px,1fr));
  gap:10px;margin:16px 0 0}
.related a{display:block;background:var(--card);border:1px solid var(--border);
  border-radius:var(--r-sm);padding:14px 16px;color:var(--fg);font-weight:550;font-size:14.5px}
.related a:hover{text-decoration:none;border-color:var(--border-strong);background:var(--card-elev)}
.related span{display:block;color:var(--muted);font-weight:400;font-size:13px;margin-top:3px}

.checks{list-style:none;margin-left:0}
.checks li{padding-left:26px;position:relative}
.checks li::before{content:"";position:absolute;left:4px;top:9px;width:9px;height:9px;
  border-radius:99px;background:var(--lime)}