Common questions
What manufacturers ask.
If your question is not here, put it in the first conversation. We would rather answer it before a technical evaluation than after.
- Do we have to use the DeepMindex dashboard?
- No. The licensed layer is designed to sit behind your own product. Outputs can feed your app, firmware or cloud service; the practitioner and instructor surfaces are separate DeepMindex products.
- Which devices are a fit?
- The starting point is access to usable EEG and PPG signals, with respiration where available. Fit depends on sensor placement, sampling, signal access and the conditions in which the device is worn — not on the form factor alone.
- Can we white-label the outputs?
- Outputs can be presented inside your product experience under the agreed claims schedule. Branding, attribution and any DeepMindex endorsement are set in the licence rather than assumed.
- Are the algorithms clinically validated?
- DeepMindex is not a diagnostic instrument. Validation is assessed per component and per hardware configuration, and the licence states the current evidence and any remaining candidate status. We do not present provisional results as clinical proof.
- What happens to data from our devices?
- Evaluation data is used only for the agreed assessment, under written data-use and consent terms. Production data can remain in your architecture, with processing on-device or in your cloud where the integration allows.
- Can you support a sensor configuration that does not exist yet?
- That is the co-development route. We assess the signal chain first, then scope the engineering and validation work together. Licensing terms are agreed before the programme starts.