Legal hub overview
The shared trust centre and reading template entry point for all future legal content.
/legal
Open routeLegal and trust centre
SummitNinety keeps legal content in the main site, in plain view, and in a layout designed for long-form reading. This hub is the shared entry point for organisation-level and product-level trust pages.
Route directory
The hub lists what is live now and which routes are already reserved for the next policy issues. Reserved routes are visible here so the legal IA stays stable as content lands.
The shared trust centre and reading template entry point for all future legal content.
/legal
Open routePublished product-specific privacy policy covering on-device storage, optional iCloud sync, and the no-analytics stance.
/studyflow/privacy
Open routePublished organisation-level website privacy policy covering basic web requests, email enquiries, and the current no-tracking stance.
/privacy
Open routeIncluded as a dedicated section within the website privacy policy while the site runs without analytics or marketing trackers.
/privacy#no-tracking-and-cookies
Open routePublished site terms covering baseline website use, content, links, and practical limitations.
/terms
Open routePublished company identity page covering the operating entity, contact routes, and policy links.
/company
Open routeReading standard
Later policy issues can plug content straight into the same layout. The aim is readable documents with stable anchors, a visible table of contents, and sections that scan well on both phone and desktop.
The shared layout keeps a focused reading column, clear section headings, and a lightweight table of contents. That avoids markdown-dump pages while staying simple enough to maintain in-repo.
The route structure separates organisation-level pages from product-level pages without inventing a CMS. Shared trust pages live under the legal hub, while product-specific policies can live alongside the product they describe.
Future issues only need to supply the long-form copy and route-specific metadata. The layout, anchors, and trust-centre structure are already in place, which keeps later policy delivery focused on content rather than page mechanics.