neuron-technologies/neuron-web
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

[P0] Terms §5 overclaims: "cannot read network traffic" is false for first-party inference #156

New Issue
Open
opened 2026-06-14 14:50:31 +00:00 by tim.lingo · 0 comments
tim.lingo commented 2026-06-14 14:50:31 +00:00
Member
Copy Link
Copy Source

PRE-LAUNCH. §5 'The Network Layer' says Neuron LLC 'cannot read, inspect, retain, or produce the contents of network traffic as an architectural constraint.' That is FALSE for the first-party Neuron Inference path: you cannot run inference on ciphertext — the server terminates TLS and the model reads the plaintext prompt. It holds only for pass-through/relay to third-party providers. Internal contradiction: §4 correctly uses POLICY language ('will not store/train/share') while §5 uses CAPABILITY language. FIX: narrow §5 to 'encrypted in transit; for relayed third-party traffic we do not retain/inspect; for Neuron inference the request is processed in memory and never stored/logged/trained-on/shared.' Restore 'cannot' only when confidential-compute/TEE inference ships. ALSO add a feedback/telemetry clause (none today): response thumbs stored locally and never transmitted; the feedback door sends only typed text, user-initiated. Spec: docs repo (PR #1).

PRE-LAUNCH. §5 'The Network Layer' says Neuron LLC 'cannot read, inspect, retain, or produce the contents of network traffic as an architectural constraint.' That is FALSE for the first-party Neuron Inference path: you cannot run inference on ciphertext — the server terminates TLS and the model reads the plaintext prompt. It holds only for pass-through/relay to third-party providers. Internal contradiction: §4 correctly uses POLICY language ('will not store/train/share') while §5 uses CAPABILITY language. FIX: narrow §5 to 'encrypted in transit; for relayed third-party traffic we do not retain/inspect; for Neuron inference the request is processed in memory and never stored/logged/trained-on/shared.' Restore 'cannot' only when confidential-compute/TEE inference ships. ALSO add a feedback/telemetry clause (none today): response thumbs stored locally and never transmitted; the feedback door sends only typed text, user-initiated. Spec: docs repo (PR #1).
will.anderson was assigned by tim.lingo 2026-06-14 14:50:32 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees will.anderson
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/neuron-web#156
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?