/* Toggle AI — the legal documents (privacy policy, and whatever follows it).
   Loaded AFTER `landing.css`, which it borrows entirely: the tokens, the logo, the footer, the
   buttons, the focus ring. Nothing here redefines a colour.

   These pages deliberately do NOT carry the `is-scaled` frame. The landing page is a Figma
   artboard scaled whole; a legal document is text, and text wants a measure, not a scale
   factor. Without that class `landing.css` falls through to its `html:not(.is-scaled)` branch —
   the plain readable column — which is exactly the right starting point, so the work here is
   only to give that column a maximum width and a document rhythm. */

.legal-page .container { max-width: 880px; }

/* The landing header's nav and its ghost buttons are hidden by the plain-page branch, so this
   page carries its own two-item header instead of fighting for them back. */
.legal-header {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 24px;
  padding: 20px;
  border-bottom: 1px solid var(--sage-4);
}

.legal { padding: 56px 20px 88px; }

.legal__eyebrow {
  display: block;
  font-weight: 600;
  font-size: 13px;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--brand-10);
}
.legal h1 {
  margin: 12px 0 0;
  font-weight: 600;
  font-size: 38px;
  line-height: 1.18;
  letter-spacing: -0.018em;
}
.legal__dates { margin: 16px 0 0; font-size: 14px; color: var(--sage-11); }

/* The summary box. A privacy policy nobody reads protects nobody, and "transparent" under
   GDPR Art. 12(1) is a plain-language test, not a completeness one — so the short answer is
   given before the long one rather than after it. It is a summary and says so: every claim in
   it is stated again, in full, in the section it belongs to. */
.legal__tldr {
  margin: 32px 0 0;
  padding: 20px 24px;
  border: 1px solid var(--sage-4);
  border-left: 3px solid var(--brand-10);
  border-radius: var(--radius);
  background: var(--sage-2);
}
.legal__tldr p { margin: 0 0 8px; font-weight: 600; }
.legal__tldr ul { margin: 0; padding-left: 20px; }
.legal__tldr li + li { margin-top: 6px; }

.legal h2 {
  margin: 48px 0 0;
  padding-top: 24px;
  border-top: 1px solid var(--sage-4);
  font-weight: 600;
  font-size: 22px;
  line-height: 1.3;
}
.legal h3 {
  margin: 28px 0 0;
  font-weight: 600;
  font-size: 16px;
  line-height: 1.4;
}
.legal p, .legal li { font-size: 15px; line-height: 1.7; }
.legal p { margin: 14px 0 0; }
.legal ul, .legal ol { margin: 14px 0 0; padding-left: 22px; }
.legal li + li { margin-top: 8px; }
.legal a { color: var(--brand-10); text-decoration: underline; text-underline-offset: 2px; }
.legal a:hover { color: var(--brand-10-hover); }
.legal strong { font-weight: 600; }
.legal code {
  padding: 1px 5px;
  border-radius: 4px;
  background: var(--sage-3);
  font-size: 0.92em;
}

/* Two of these tables are the ones a regulator looks for by name — the cookie inventory
   (PIPA §30, "자동 수집 장치의 설치·운영 및 그 거부") and the cross-border transfer notice
   (PIPA §28-8) — so they are tables rather than prose on purpose: each is a fixed list of
   fields, and a paragraph is where one of those fields quietly goes missing. */
.legal__table-wrap { margin: 16px 0 0; overflow-x: auto; }
.legal table {
  width: 100%;
  border-collapse: collapse;
  font-size: 14px;
  line-height: 1.6;
}
.legal th, .legal td {
  padding: 10px 12px;
  border: 1px solid var(--sage-4);
  text-align: left;
  vertical-align: top;
}
.legal th { background: var(--sage-2); font-weight: 600; }
.legal td code { white-space: nowrap; }

.legal__contact {
  margin: 32px 0 0;
  padding: 20px 24px;
  border: 1px solid var(--sage-4);
  border-radius: var(--radius);
  background: var(--sage-2);
}
.legal__contact p { margin: 0; }
.legal__contact p + p { margin-top: 8px; }