FAQs - Security

What steps has OSF taken to comply with GDPR?

OSF has taken several steps to comply with GDPR, including revising our Terms of Use and Privacy Policy, ensuring GDPR compliance of third-party vendors and executing Data Processing Addendums with each, and reviewing policies and procedures for deleting user data. Read our blog post for more detail.

What types of data does OSF collect?

OSF may collect various data that you share upon registering and in using OSF and its suite of products. Please see section 7 of our Privacy Policy for this information.

Can I have my data deleted?

You’re always welcome to deactivate or delete your account. If you’d like to delete your account and personal data, please email support@osf.io.

Can I opt out of having my data collected?

You’re always welcome to deactivate or delete your account. You should be aware that information that you've shared with others or that others have copied may also remain visible after you have closed your account or deleted the information from your own profile. In addition, you may not be able to access, correct, or eliminate any information about you that other users have copied or exported out of the Websites, because this information may not be in our organization's control. Your public profile may be displayed in search engine results.

How can I export my data?

In your account settings, click the Export Account button and our support team will be in touch shortly.

What if I cannot consent to the updated terms and privacy policy?

If you cannot consent to the updated terms and privacy policy, you may export your data and close your account at any time.

What if I don't want to make anything available publicly in the OSF?

The OSF is designed to support both private and public workflows. You can keep projects, or individual components of projects, private so that only your project collaborators have access to them.

How secure is my information?

Security is extremely important for the OSF. When you sign up and create a password, your password is not recorded. Instead, we store a bcrypt hash of your password. This is a computation on your password that cannot be reversed, but is the same every time it is computed from your password. This provides extra security. No one but you can know your password. When you click "Forgot your password," the OSF sends you a new random password because it neither stores nor has the ability to compute your password.

How does the OSF store and backup files that I upload to the site?

For OSF Storage, files are stored in multiple locations and on multiple media types on Google Cloud. We keep three types of hashes (MD5, SHA-1, SHA-256) for files. We keep parity archive files to recover from up to 5% bit error. 

The OSF database is backed up via streaming replication 24 hours a day, and incremental restore points are made twice daily. Further, the OSF database is maintained in encrypted snapshots for an additional 60 days. Database backups are verified monthly.

Operational data (e.g., config files) for other OSF services are backed up in primary cloud file storage for 60 days.

Logs are primarily stored in Google Cloud cold storage indefinitely. In certain cases a third party aggregation service is used for up to 90 days.

Is data stored on OSF Storage encrypted? What are my options?

Transfer of data to OSF storage is encrypted with TLS and is encrypted at rest with Google-managed Encryption Keys(https://cloud.google.com/storage/docs/encryption/default-keys). If you would like your data to be encrypted at rest with your own self generated key, you can encrypt it before uploading to OSF Storage.

Is the OSF HIPAA compliant?

You should refer to your institutional policies regarding specific security requirements for your research.    This article is licensed under CC0 for maximum reuse. 
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us