Data & privacy
Know what happens to the data.
This page describes the current public showcase. It separates what the application does today from the controls still required for a future study workspace.
The showcase today
Synthetic examples. Local drafts.
The current application has no account system, EEG upload, connected analytics integration, or implemented AI analysis. Its demo values are authored examples, not participant recordings.
Demo selections
Session, channel, band, recording view, and report-preview selections are held in page state. The application does not save them to a user account, a database, or browser local storage.
Synthetic measurements
The dashboard generates deterministic waveform previews from bundled example values. The initial page can be rendered on the server; selections update the example in the browser. There is no EEG upload, device connection, analysis-service request, or model call.
Report downloads
Download report creates a plain-text file in the browser from the selected synthetic example. The application does not send the report to a server or email recipient.
Collaboration inquiry
The form holds name, work email, organization, research area, and question in the current page. It validates those fields and creates a local .txt draft. There is no server-side submission, email delivery, or application database persistence.
Your browser and files
Local does not mean every copy disappears.
Clear form resets the inquiry fields and status in the page. It does not delete a file already downloaded, a copy you have shared, or browser-managed information. Downloads can remain on your device, in backups, or in a synced downloads folder.
Your browser may retain autofill entries, browsing history, cached resources, or restored form values according to its settings. The site does not control those copies. Use browser settings and file management to review or remove them.
Keep patient names, medical records, identifiable EEG, and sensitive health information out of this showcase and its inquiry form. A local text draft is not a protected study record.
Normal website traffic
Pages still make web requests.
Your browser requests pages, scripts, styles, fonts, and other site resources. The web server, hosting provider, or network infrastructure may process connection and request information, such as an IP address, requested URL, time, and browser details.
This website is hosted on Cloudflare. The absence of an application analytics integration does not establish an absence of hosting or infrastructure logs. Processing locations and retention depend on the provider and account settings. This site does not promise a specific infrastructure retention period.
This implementation description does not certify a deployment's security, confidentiality, or regulatory compliance. Those depend on the actual service configuration, operations, and applicable study requirements.
Before real study data is used.
The private upload-to-report workspace is planned work. The controls below are requirements to define, implement, and verify. They are not capabilities provided by this public demonstration.
Consent and study governance
Document the approved study purpose, participant information and consent process, investigator responsibilities, and permission to use each data source before collection. Confirm the ethics-review requirements for the proposed study.
Pseudonyms and separate identities
Use coded participant identifiers and keep any identity key separate from recordings. Pseudonymized data still needs access restrictions and a defined purpose.
Roles and private storage
Define study-specific access roles. Validate private storage, encryption in transit and at rest, authorization checks, and a process for granting and revoking access.
Audit logs and review records
Record relevant access, data changes, analysis versions, exports, and reviewer decisions so study activity can be traced.
Retention, deletion, and backups
Set retention periods, deletion procedures, backup schedules, recovery tests, and the handling of retained copies and exports before storing participant data.
Provider and model policies
Review hosting and analysis providers, processing locations, subprocessors, data-sharing terms, and any provider training or retention policy before sending data to a service or model.
Details still to resolve
Research services need named owners and verified settings.
- Confirm the operating organization or data controller, its responsibilities, and a working privacy contact.
- Before adding research services, define their hosting locations, infrastructure logging, retention periods, and provider terms. The current public showcase is hosted on Cloudflare.
- Confirm the inquiry contact and delivery process before enabling a submission service. The current form only downloads a draft.
- Keep real study uploads disabled until the future workspace controls, provider terms, and study governance are reviewed and verified.
There is no finalized privacy contact, research-data retention schedule, or participant consent service published here. This page is an implementation explanation, not a claim of certification or an operational policy for a research service.
Continue exploring
Understand the example before planning a study.
Read the analysis approach or prepare a local collaboration inquiry.