Updated 10 November 2026
This page lists information the NEOS client at https://neos.primusneo.com sends or stores. It is operated by Escherbridge, LLC.
Contact Ahmed Zaher at contact@escherbridge.com, (509) 578-4603, 1140 S Colorado Ln, Boise, ID.
This client does not set a retention schedule, and it does not state an age rule.
If you register or sign in with a password, the client sends a username and password to the NEOS API, and a display name when you provide one. A sign-up link can also send an ecosystem id.
If you sign in with a browser key, this browser stores the private key in local storage. The sign-in request sends the public key's DID and a signature of a server challenge. The private key is not part of that request. The client also posts the DID and public key to the workspace DID endpoint.
If an outside sign-in provider is enabled and you choose it, the browser is redirected to that provider. On return the API sets a session cookie. The membership can record which provider was used. This client does not show an email address or photo received from that provider.
The API sets a neos_session cookie. The client stores the communities you select in a neos_selected_ecosystems cookie, and the sidebar stores an open or closed cookie.
Local storage holds the theme, whether the route guide is open, platform-tour progress for the signed-in user id, the browser key material described above, and a push-owner id if you enable browser push.
Session storage holds the in-app page to open after sign-in, and node-admin navigation if you use that screen.
The profile editor can save a display name, username, headline, biography, location, profile image URL, website, LinkedIn URL, GitHub URL, skills, interests, and projects (name, description, URL, role, start, and end).
The member form can save a phone number and a profile image on a membership. The public profile page does not show phone numbers, authentication details, private notes, or raw quiz answers.
The workspace sends the governance and participation records you submit: agreements, proposals, advice, consent positions, test reports, messages, assistant chat, quiz answers with score and time spent when you submit, orientation progress and reflections, shares, needs, solutions, collaborations, conflict and emergency records, exit records, and personal decision notes.
A person who files an exit and is the one leaving can download a JSON file of the portable governance record the exit page describes.
Community search text is sent as a query.
In-app updates do not require an email address or phone number. If you submit an email address or phone number for updates, the client sends that destination and, when you enter it, a verification code. The settings page then shows a masked destination. You can remove that contact.
If you enable browser push, the client registers a push subscription for this browser.
Notification settings can save a time zone, quiet hours, a pause time, and which updates you follow or mute.
The settings page states that email, push, and SMS stay off until delivery setup is complete and you enable them. This page does not turn those providers on.
The public HTML does not load an analytics, advertising, or tag-manager script.
This page does not describe server logs, and it does not state how long any record is kept.