Skip to content

Update privacy.md #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 6, 2024
Merged

Update privacy.md #137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/privacy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ brainlife.io allows administrators to access uploaded and generated data-objects

The archive data is currently stored on [OSiRIS](https://www.osris.org/), the NSF founded distributed storage infrastructure. We are also exploring the use of [OSN](https://www.openstoragenetwork.org) in the coming months. Only the brainlife administrator is authorized to access these storage systems, however, administrators of these storage systems may have access to the data.

brainlife.io provides their users several *shared* computing resources including brainlife.io's own slurm clusters running on Jetstream, and various other XSEDE resources. These shared resources are enabled to all users by default, and when you submit jobs on brainlife, the data must be transferred to these remote computing resources. The data transfer between resources is encrypted by ssh/sha2 protocol with ssh keys encrypted by PBKDF2/sha512 algorithm.
brainlife.io provides their users several *shared* computing resources including brainlife.io's own slurm clusters running on Jetstream, and various other [ACCESS](https://access-ci.org/) resources. These shared resources are enabled to all users by default, and when you submit jobs on brainlife, the data must be transferred to these remote computing resources. The data transfer between resources is encrypted by ssh/sha2 protocol with ssh keys encrypted by PBKDF2/sha512 algorithm.

The staged data and any data derivatives generated by Apps may be persisted up to 30 days (or shorter) on remote resources during which the administrators of those resources may have access to the data. All shared resources uses a single login account ("brlife") and only the brainlife service (amaretti) and the platform administrators have access to this account. brainlife platform then allows authorized users access to the data that belongs to the projects.

Expand Down
Loading