Principal-led architecture for critical systems

Privacy

A public site designed to collect less

This notice describes the public site, local search, optional first-party public-safe lead intake, browser-local email fallback, retention boundaries, ordinary hosting logs, and prohibited sensitive information.

Page summaryUse the page to make a named decision
Purpose
Review the public information, boundaries, and next action for this part of the site.
Boundary
Only verified public facts are rendered; unknown and private facts remain omitted.

Public website behavior

  • No configured advertising pixels or external analytics
  • No hosted search service; search runs locally against a public index
  • No third-party lead platform or form processor
  • No public AI chatbot or autonomous tool interface
  • No external font dependency

Optional WordPress-native lead intake

The Contact page can store a public-safe inquiry as a private WordPress lead record only after the visitor checks the storage notice and submits the form. The stored record includes the submitted fields, consent and intake timestamps, source-page and content-cluster context when supplied by a LongTermCapabilities call to action, optional AI architecture and decision categories, and an allowlisted discovery channel when one is present on the submitted form. The plugin does not record ordinary page views, store a full HTTP referrer, or accept file uploads.

Lead records use the existing WordPress database, users, roles, capabilities, nonces, and privacy export and erasure tools. The plugin does not claim application-layer encryption, a universal retention period, or cryptographic redaction. The site owner remains responsible for WordPress, hosting, database, backup, access-control, retention, and deletion configuration.

A successful website response confirms that WordPress accepted the inquiry record. It does not accept an engagement, guarantee a response time, create a secure evidence-transfer channel, or prove that a separate email was delivered.

Browser-local email fallback

The email-draft and copy options validate and format the inquiry in the visitor's browser. The visitor must review and send the message from their own email application. Those fallback actions do not store the inquiry in the lead system unless the visitor separately uses the first-party submit action.

Hosting, WordPress, and email logs

The hosting provider may retain ordinary web-server, firewall, database, backup, and operational logs. WordPress and installed plugins may also record ordinary security or administrative events according to the owner-controlled configuration. The business email provider processes messages a visitor sends. Provider identities, infrastructure topology, backup rotation, and actual provider retention terms are not asserted here because production deployment details have not been verified for public disclosure.

Prohibited sensitive information

Do not submit credentials, tokens, private keys, private source code, customer records, PHI, financial account data, classified material, CUI, export-controlled material, source-selection-sensitive information, privileged legal material, or confidential production architecture through the public form or public email.

Access, correction, export, and erasure requests

Questions or requests concerning a submitted inquiry may be discussed by phone at 1 (464) 274-1476 or sent to consulting@longtermcapabilities.com. WordPress privacy tools can export the stored lead fields and erase designated personal contact fields after identity and authority are verified. Hosting backups and security logs may persist until their configured rotation or deletion period.

Private local search

Find a service, capability, evidence record, resource, or insight

Press / to open search when focus is not in a form field.

Search runs locally against the public site index.