Does EEG TraceLab upload EDF files?
By default, no. Raw EDF files are processed locally and are not uploaded to EEG TraceLab developer servers.
Local EEG app privacy
Local-First EEG Privacy for EDF / EDF+ Research
EEG TraceLab is local-first by default. Raw EDF files, workspace data, analysis results, preprocessing runs, presets, and exports stay on the user’s device unless the user chooses to export, share, or submit support information.
This page explains EEG TraceLab's privacy model for anonymised EEG research, no raw EDF cloud upload by default, support data boundaries, and user responsibility after export.
EEG TraceLab is designed for research, education, and non-clinical signal inspection. It is not a medical device, diagnostic tool, seizure detector, clinical monitor, treatment tool, emergency tool, or medical decision-support system.
What stays local
Research data remains on the device by default.
EEG TraceLab is designed so the primary EDF research workflow does not require uploading raw recordings to EEG TraceLab developer servers.
Raw EDF files
Workspace data
Analysis results
Exports
Parameter presets
Preprocessing runs
Local notes and project metadata
What may leave the device
External data flow is user-initiated or handled by Apple.
The app and website may send information only when users actively choose a support or feedback flow, or when Apple handles payment and subscription entitlement state through StoreKit.
Website support form content: contact name, contact email, and message
In-app feedback content: contact email, feedback message, manually entered iOS version, and manually entered device model
App Store / StoreKit payment and subscription handling by Apple
Files the user exports or shares outside the app container
Anonymised import
EDF metadata is handled with research safety in mind.
EEG TraceLab encourages safe recording names and local notes, and uses anonymised recording identifiers in the app library.
EDF header fields are rewritten during anonymised import
Recordings use local anonymised identifiers
Safe display names help avoid identifiers in the local library
Original file names are stored only as a SHA-256 hash where applicable
Exact original EDF start date/time is not retained in app metadata
Export responsibility
Exported files are user-controlled files.
After a user exports CSV, JSON, PNG, bundles, or copied EDF artifacts, those files are managed by the user in their chosen iOS or external storage location.
No advertising tracking
No ad SDKs and no sale of personal data.
EEG TraceLab does not use advertising tracking, does not include third-party advertising SDKs, and does not sell personal data.
FAQ
Questions searchers and AI agents often need answered.
These answers keep the product scope specific and keep medical and clinical boundaries visible.
Does EEG TraceLab read Apple payment card details?
No. Apple handles payments and subscriptions through StoreKit and the App Store. EEG TraceLab does not receive full payment card numbers or payment credentials.
Does EEG TraceLab include cloud sync?
The current product positioning is local-first. It does not include a developer-operated raw EDF cloud upload workflow by default.
How can users delete local data?
Users can delete the app to remove local app-container data. Files exported or saved outside the app may need to be deleted separately from their storage locations.