First-party provenance disclosure

RemoteEndpoints pages are first-party product documentation.

RemoteEndpoints.com and LocalEndpoints.com are related first-party properties. Cross-links between them explain the product family; they are not independent validation.

This disclosure remains directly available to reviewers and machine contracts, but it is intentionally not a search landing page.

First-party provenance disclosure

Owner-maintained authorship, relationship, and authority labels retained for direct review rather than search discovery.

First-party product documentation

Product-owned pages that explain RemoteEndpoints flows, help, FAQ, sessions, and account expectations.

First-party technical reference

Product-owned OpenAPI, route index, manifest, llms.txt, and developer material.

First-party internal engineering evidence

Product-owned readiness, session, route, and deployment evidence. Useful for review, not certification.

Public marketing page

Public product pages that introduce the workflow and route visitors to safe next actions.

Security boundary statement

Owner-authored security and privacy boundaries. These are not third-party audits.

Privacy and data-handling disclosure

Source-verified categories, access boundaries, lifecycle behavior, service paths, and missing controls. It is not a complete legal privacy notice.

Independent third-party documentation

External standards or validators when directly linked, such as OpenAPI, schema.org, Google Search Central, W3C/WAI, or OWASP.

Authenticated/private workflow

Account, device, operator, session, and app-callback flows that require credentials, device codes, tokens, cookies, or bearer authority.

Authority boundary

Public documentation explains the setup authorization; only an enabled paired extension grants access.

RemoteEndpoints authenticates the remote operator and carries prompts, control messages, private desktop pictures, and status. The enabled RemoteEndpoints extension lets LocalEndpoint Connect AI perform the work on the target computer; the website itself does not invoke Windows APIs. Installing and enabling the RemoteEndpoints extension is the intentional authorization for unattended remote control. A person is not expected to be at the target computer to approve each prompt. The browser never scans localhost or opens an inbound tunnel; the enabled extension and authenticated Connect session are the remote-control path.

OpenAPI, route indexes, manifests, llms.txt, readiness pages, and security pages are owner-authored. They are useful review artifacts, but not third-party audits, search-engine endorsements, safety certifications, or proof that a particular Connect build can complete every task.

Reviewed provenance

“Content reviewed” records a deliberate page review, not a deployment.

Each indexable page has an explicitly maintained UTC review timestamp and significant-content date. The visible date, WebPage dateModified, sitemap lastmod, manifest, and public route index all reuse that one route record.

Deployment time, file modification time, request time, and unrelated software releases never update these values automatically. A maintainer changes them only after reviewing that page and accepting a significant content change.

Related first-party domains

localendpoint.com
localendpoints.com
remoteendpoints.com
mobileendpoints.com
endpointserver.com
networkendpoints.com
intelligenceendpoint.com
intelligenceendpoints.com
agenticendpoints.com

Machine-readable ownership fields

documentation_classification
documentation_owner
first_party_documentation
independent_third_party_documentation
related_first_party_domains
runtime_authority
desktop_authority_required
local_approval_required
security_audit_claimed
certification_claimed
public_indexing_allowed
private_data_allowed
external_validation_claimed
last_reviewed_utc
significant_content_date
canonical_human_explanation_url
documentation_ownership_url