Skip to content
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

Jump to bottom

data security concerning PII #71

Open
emilyliquin opened this issue Mar 22, 2023 · 2 comments
Open

data security concerning PII #71

emilyliquin opened this issue Mar 22, 2023 · 2 comments
Assignees
@guydav @emilyliquin
Labels
enhancement New feature or request important Important issue to address
Milestone
first version (v0...

Comments

@emilyliquin
Copy link
Contributor

  • add private subcollection for identifying info
  • add authentication with Guy's set-up
@emilyliquin emilyliquin added enhancement New feature or request important Important issue to address labels Mar 22, 2023
@gureckis
Copy link
Member

just FYI this might be related to/solve issue #7

@gureckis gureckis changed the title data security data security concerning PPI Mar 24, 2023
@gureckis gureckis changed the title data security concerning PPI data security concerning PII Mar 14, 2024
gureckis added a commit that referenced this issue Apr 26, 2024
@gureckis
moving recruitment info to a private part of smilestore (issue #71)
74eba93
@gureckis
Copy link
Member

gureckis commented Apr 26, 2024 •
edited

  • save the private data in a different document
  • update the data browser so you can see inside the private data
  • update download datafiles stuff to include authentication
  • what happens when you reconnect to Firestone in this case? we were assuming that the private data is read only so if a subject reloads some of that info might not come back. a problem?

gureckis added a commit that referenced this issue Apr 26, 2024
@gureckis
private document support (issue #71)
19325fa 
- moves PII type data to a new private subcollection
- field moved are recruitment_info (e.g., workerid/prolificids), withdraw_data (info about why a person withdrew), and the browser_fingerprint (info about browser and ip address)
- these fields are separate and easier to keep away from downstream analysis
- needs to be blocked with firebase fules (issue #24)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guydav guydav

@emilyliquin emilyliquin

Labels
enhancement New feature or request important Important issue to address
Projects
None yet
Milestone
first version (v0.1.0) 🌱
Development

No branches or pull requests
3 participants
@gureckis @guydav @emilyliquin