The Nessa app's Settings › Legal "Terms of Service" row had no Nessa-owned
document to resolve to: it linked another product's terms, and
nessa.freno.me/terms was a 404. Nessa sells an auto-renewing subscription, so
App Review 3.1.2 requires the app to link terms of use as well as a privacy
policy — the row has to land on a real document.
- src/routes/nessa/terms.tsx: the page, in the privacy.tsx house template
(EdgeCacheHeaders, site-aware PageHead, SubdomainHeader, subdomain-relative
internal links). Sections cover acceptance, the service and its limits,
accounts, community content and acceptable use, auto-renewable
subscriptions (payment, renewal, the 24-hour cancel window, managing it in
the App Store, trials, refunds, price changes), the Apple third-party
acknowledgements, IP, disclaimers and liability, termination, changes, and
contact.
- src/lib/sitemap-routes.ts: add /terms to the Nessa set, and update the
count assertion in sitemap-routes.test.ts to match.
Health and safety: Nessa is not a medical device, so section 2(c) says so
explicitly — the previous app-side link pointed at another product's terms,
which said nothing about Nessa's training features.
Deliberately left out, for Mike to decide rather than have me guess:
- No legal entity name and no governing-law clause. No Nessa page states
either today; the privacy policy speaks only as "we".
- No NAV_CONFIG entry, so the nav link-set matrix tests are untouched. The
route serves through the existing catch-all host rewrite in vercel.json;
adding a nav item is a one-line change plus a matrix update if wanted.
The Nessa API (nessaDb.*, nessa.community.*, Clerk auth and the Clerk user
webhook) lives in the Nessa repo's server/ on pan. This copy never served
the app: RemoteAPIClient wraps every input in {"input": …}, which the stock
tRPC adapter here reads as the input itself (queries 404, writes no-op).
Clerk's webhook already targets nessa-api.freno.me.
Drops the routers, nessa-auth, the webhook, NessaConnectionFactory, the
NESSA_* env and the now-unused @clerk/backend and svix. Nessa's marketing,
privacy and deletion pages stay.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refactor the monolithic main-site contact page into a reusable
<ContactForm> component that encapsulates the Turnstile widget, cooldown
timer, email-verification flow, and tRPC submission. The main
/contact route becomes a thin wrapper that supplies the site-specific
disclaimer subline and Life-and-Lineage FAQ accordion (now exported as
<LineageContactQuestions> for reuse).
Add per-subdomain contact routes (gaze, inputhalo, lineage, nessa) that
render the shared component, with site-aware subject prefix, recipient,
heading, and PageHead metadata derived via useSite() from CONTACT_CONTEXT.
Introduce src/lib/contact-config.ts (with tests) centralizing the contact
recipient/sender addresses and subject building. The misc.sendContactRequest
mutation accepts an optional subjectPrefix (defaulting to "freno.me") so
inbound call sites continue emitting byte-identical legacy subjects, while
subdomain submissions route distinct subjects (e.g. "[Gaze] Contact Request")
to the same inbox.
Consolidate privacy policies per-subdomain:
- Migrate Gaze and Life and Lineage privacy policies verbatim from the
legacy /privacy-policy/* routes to their subdomain paths
(gaze.freno.me/privacy, lineage.freno.me/privacy), and replace the old
routes with 308 permanent redirects to preserve SEO equity and stable
link resolution.
- Add net-new privacy policies for the InputHalo and Nessa subdomains.
- Update the contact page link to point at the Lineage subdomain privacy
policy.
Add the Nessa subdomain landing page served at nessa.freno.me/.
- index.tsx: hero, feature highlights, CTA band, and footer themed via
useSite() brandColor and useDarkMode(); deliberately avoids freno.me
web-auth UI (Nessa uses Clerk) and uses a non-fabricated 'Coming soon'
CTA since there's no app-store presence yet.
- meta.ts: deterministic PageHeadProps (title, description, OG) as a pure
module mirroring the page-head-meta testability pattern; feature copy is
derived from real nessaCommunityRouter capabilities (clubs, challenges,
social.feed, events).
- meta.test.ts: resolves metadata over SITE_CONFIG.nessa + pathname '/' to
assert title suffix composition, canonical, OG image fallback, and
description content.
