Docs, examples, schemas, route indexes, discovery files, and quality gates are safe public artifacts.
Privacy and control
Security
See where LocalEndpoint Connect messages, model replies, and optional plugin data go, including ordinary owner-gated actions and paired unattended RemoteEndpoints authority.
Your local data path
What happens when you send a message
For local chat, the website is not in the loop: the app, model, reply, and local memory remain on your Windows PC.
-
You type in Connect
Your message starts in the Windows app, not on LocalEndpoints.com.
-
Your model answers on this PC
Connect sends it to your selected local model—not a hosted AI provider.
-
The answer comes back to Connect
The reply and local memory stay on this computer.
-
Ordinary protected local requests wait for the owner
In the normal local mode, protected requests pause for the owner's current decision. This public LocalEndpoints site cannot approve or run them; not every action is proven in this build.
Optional connection
Remote and shared-memory features use different authority paths.
View detailed network behavior
RemoteEndpoints stays off until its independent extension is installed, enabled, and paired once; that pairing establishes standing unattended authority with no target-side per-prompt approval. Installed development Connect 0.2.273 implements MemoryEndpoints browser pairing, but its production round trip and public artifact remain unqualified.
Network behavior
When LocalEndpoint Connect uses the network
Local-only chat does not mean the app never uses a network. These are the current, bounded connection paths.
| Activity | Destination | When | What leaves your computer |
|---|---|---|---|
| Visit this website | LocalEndpoints.com | When you open a public page or download | Normal web request data; no app prompts, model responses, local files, or runtime telemetry |
| Release check | LocalEndpoints.com release metadata | When the app launches | A request for public release metadata; no automatic download or install |
| Browse or download a model | Hugging Face Hub | Only when you open the catalog or approve a download | Catalog/download requests; no chat prompt or generated response |
| Run local chat | Your device and local worker | After you choose a local model and approve readiness | No prompt or model response is sent to this website or a hosted model provider |
| Use RemoteEndpoints | RemoteEndpoints.com | Only after separate extension install, authenticated sign-in, local enablement, and one-time pairing | Private authenticated intent, desktop pictures, progress, and results for the unattended workflow. Connect, not the browser, performs Windows work. |
| Use MemoryEndpoints | MemoryEndpoints.com | After one-use browser-PKCE pairing and company/workspace/project approval | Only owner-selected public-safe memory. No real production round trip or public artifact qualification is claimed. |
Privacy and accounts
Local-only use does not need a website account
Account use is optional and separated from local chat. When you choose an account feature, the data path changes visibly.
- Local-only app
- No website account, email address, or password is required after the app and model files are present.
- Website account
- Only the dedicated register and sign-in routes collect an email address and password. The server stores a salted PBKDF2-SHA256 password hash, not the plaintext password.
- Session
- Successful website sign-in sets a Secure, HttpOnly, SameSite=Lax session cookie. Signing out revokes the server session and clears the cookie.
- Email verification
- The account route can send the verification email through Mailgun when configured, so the account email address is shared with that delivery provider.
- LocalEndpoint Connect
- The Windows app opens the website for account authentication and does not collect or store the website password.
- Optional plugins
- RemoteEndpoints needs an authenticated account plus independent install, local enablement, and one-time pairing; pairing is standing authority, so no human at the target approves each prompt. MemoryEndpoints uses one-use browser-PKCE approval and stores only its bound per-agent connector credential in current-user Windows Credential Manager.
Security boundary matrix
What can happen here is smaller than what the product can become.
The public site can explain, publish contracts, validate local files in the browser, and link to evidence. It cannot operate a visitor's machine.
Manifest checks run in the tab and can export redacted receipts without sending payloads to the site.
Future Desktop approval belongs on the user's device, with visible consent and reviewable receipts.
No scan, fetch, socket check, service discovery, or private-network access is performed by the public site.
Product, docs, download, and validation pages request no password, token, private log, or raw endpoint file. Account credentials stay on dedicated account routes.
No browser click on LocalEndpoints.com launches desktop work, runtime execution, installer actions, or autonomous control.