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 first-party lead intake

The Contact page can store a public-safe inquiry in a separately installed, single-tenant LongTermCapabilities lead system only after the visitor checks the storage-consent notice. The stored record includes the fields submitted, the applicable notice version, consent and intake timestamps, pipeline metadata, and keyed hashes of limited request signals used for abuse prevention and security review.

Lead message content is encrypted at rest in the private application. Encryption keys, application configuration, database access, and audit tooling are kept outside the public document root. Access is limited to authenticated administrative users. The default retention period is up to 730 days; eligible records are then cryptographically redacted by destroying the per-lead key unless an owner records another lawful or contractual basis.

A successful website response confirms intake only. It does not accept an engagement, guarantee a response time, create a secure evidence-transfer channel, or prove that 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, application, and email logs

The hosting provider may retain ordinary web-server logs. The private lead application is designed to write security and operational events without message bodies, passwords, database credentials, or encryption keys. The business email provider processes messages the visitor sends. Provider identities, infrastructure topology, backups, and actual provider retention terms are not asserted here because owner 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, and redaction requests

Questions or requests concerning a submitted inquiry may be discussed by phone at 1 (464) 274-1476 or sent to consulting@longtermcapabilities.com. A reference code, when available, helps locate the record. Identity and authority may need to be verified before disclosure, correction, export, or cryptographic redaction.

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.