Privacy Policy

This policy is in effect, and is under legal review

Everything described below is what we do today — it applies now. The wording is still with counsel and may be tightened before general availability, but the practices it describes will not change without this page changing first.

Who this policy is from

Last updated 15 October 2026. The organization responsible for the data described here — the data controller — is:

• —NeuroNexus Technologies, Inc.
• —640 Avis Drive, Suite 200, Ann Arbor, MI 48108, United States
• —Privacy contact: [email protected]

Desktop apps — what we collect every time

Allego and Videre send a small amount of information each time you run them, whether or not you allow detailed analytics. We need it to know which versions are still in the field and need supporting, and whether the software is being used at all. A user who declines analytics would otherwise be completely invisible to us.

• App launch — one event per start, carrying the app name and version string (for example: 4.2.1 (electron: 39.0.0) (node: 22.12.0))
• App usage — how many seconds the app was open and focused
• Your account identifier — the Cognito user ID that signs you in. Not your email, name, or organization. It is not anonymous: it is an identifier we can trace back to your account, which is why the rest of this policy applies to it
• Standard event metadata — timestamp, operating system and platform, an identifier for the app window, and the session and device identifiers our analytics tool generates

Update checks go to GitHub

Separately from analytics, both apps check GitHub for a newer release when they start, and download updates from there. GitHub receives your IP address as part of that request, the same way it would if you visited a GitHub page in your browser. We send GitHub nothing about you or your work.

Why we may do that without asking

We rely on legitimate interest — our interest in supporting and maintaining the software for licensed users. This is not consent, and we will not call it consent: you are not asked, and there is no toggle that turns it off. What you do have is the right to object. Write to us and we will stop processing your data on this basis.

Desktop apps — what we collect only if you allow it

The first time you launch Allego or Videre, the app asks whether you want to share detailed usage. You can change your answer at any time in the app’s Settings tab. If you allow it, we also collect:

• Which features you open, and how long you spend in each
• How long data acquisition runs
• Your name, email address, and organization, from your Radiens license record
• The version of each app on your profile

Declining also keeps analytics off your disk

This is a real difference, not a formality. If you allow detailed usage, the app stores analytics state on your machine so we can recognize you across sessions. If you decline, that state stays in memory only and is cleared when the app closes — nothing personal is written to your disk.

What we never collect

None of the following ever leaves your machine through the Radiens apps:

• —Neural recording data
• —File contents of any kind
• —Patient or subject information
• —Screen recordings or session replay — disabled at the analytics SDK level
• —Automatic click or keystroke capture — disabled. Every event we send is one we wrote by hand

The website and Radiens Web

radiens.ai works differently from the desktop apps: no analytics or advertising cookies are set until you accept them. Until then, and if you decline, we still count your visit, but without cookies and without storing any identifier in your browser — PostHog counts it on its servers with a hash that changes every day. If you accept, PostHog sets a cookie so we can recognize you across visits, and links your activity to your Radiens account when you are signed in. Some functional data is kept in your browser either way — a cache of page content, your interface preferences, and the record of your cookie choice itself — but it stays in your browser and is not sent to us. You can change that choice at any time from Cookie settings in the footer. When you hold a Radiens account we also hold the account and session information needed to run it — but never your raw recordings, which stay on your instrument or in your own institutional storage.

• Account metadata — name, email, organization, tier, and the Cognito identifier that authenticates your sessions
• Session metadata — recording duration, channel counts, RIGOR quality scores, sync timestamps
• Usage analytics — page views, feature interactions, error reports. Counted for every visitor without cookies; linked across visits, and to your account, only after you accept
• Cookies — your authenticated session, plus the record of the cookie choice itself. No third-party advertising trackers

How we use it

We use account metadata to authenticate you, to gate tier-licensed features, and to contact you about service-affecting issues. We use session metadata to render your dashboards and KPI views. We use analytics to decide which versions to support, to improve the product, and to triage support requests. We do not sell your data and we do not share it with advertisers.

Who processes it, and where it goes

Our analytics processor is PostHog, hosted in the United States. That applies to both the desktop apps and this website, so if you are outside the US, this data leaves your jurisdiction. Where that transfer involves personal data protected by European, UK or Swiss law, our agreement with PostHog incorporates the European Commission’s Standard Contractual Clauses, in their EU, UK and Swiss forms. PostHog additionally self-certifies under the EU–US Data Privacy Framework and its UK and Swiss counterparts. We instruct PostHog to discard IP addresses rather than store them or derive your location from them. For a visit counted without cookies, PostHog first combines the IP address and browser details with a random value that changes daily, and is deleted once that day’s events are processed, to compute the hash it counts by; the address is then removed. Account and session data are stored in AWS, in the US-East and US-West regions; Cognito user pools live in AWS US-East. Institutions with data-residency requirements should contact us about an institutional agreement.

How long we keep it

We keep analytics events for 12 months, after which they are deleted. That is long enough to see a full release cycle — which versions are still running a year after we ship them — and no longer. Account and session metadata are kept for as long as you hold a Radiens account, and deleted when you ask us to close it.

Your rights, and how to object

Write to [email protected] and a person will answer. You can ask us to:

• Object to the always-on desktop telemetry described above, which we collect under legitimate interest
• Access the personal data we hold about you, or have it corrected
• Delete your personal data
• Export your account-tied session metadata in NWB or JSON
• Complain to a data protection supervisory authority. In the EU or EEA that is the authority in the country where you live or work; in the UK it is the Information Commissioner’s Office. We would rather you came to us first, but you do not have to