Is Storing (Personal) Data in a Google Spreadsheet GDPR Compliant? #241

Closed
opened 2025-10-14 16:40:24 -06:00 by navan · 0 comments
Owner

Originally created by @nelsonic on 3/29/2018

Google Spreadsheets are a great way of capturing, analysing and sharing data within a team.
Sadly there are several major drawbacks of using GSheets to capture form data:

  • Data is stored by Google on their Servers in the US.
  • People ("users") cannot see the (personal) data that they have submitted
  • People ("users") cannot change or request deletion of their data (i.e. GDPR compliance)
  • GSheets makes it (too) easy to share (large amounts of) data
  • GSheets makes it (too) easy to "Make a Copy" of sheet(s) at which point any "control" of the data is lost.
    None of these points is communicated to end-users when they are filling in an HTML form.

I think we should add a GDPR "disclaimer" at the Top of the tutorial
advising people to read: https://cloud.google.com/security/gdpr
and understand that they are personally responsible for the safekeeping of any personal data
they collect and store.
And that in addition to the data collection form,
they need a mechanism to allow people to contact them
in order to remove their data from their spreadsheet and any other retrieval systems.
The data collection spreadsheet should be treated with the same (if not more)
respect as your own personal/credit card details.
Don't share it with anyone you would not trust with your own credit card.

*Originally created by @nelsonic on 3/29/2018* Google Spreadsheets are a _great_ way of capturing, analysing and sharing data within a team. Sadly there are _several_ major drawbacks of using GSheets to capture form data: + Data is stored by Google on their Servers in the US. + People ("users") cannot _see_ the (personal) data that they have submitted + People ("users") cannot _change_ or request deletion of their data (_i.e. GDPR compliance_) + GSheets makes it (_too_) easy to share (large amounts of) data + GSheets makes it (_too_) easy to "Make a Copy" of sheet(s) at which point any "control" of the data is lost. _None_ of these points is _communicated_ to end-users when they are filling in an HTML form. I think we should add a GDPR "disclaimer" at the _Top_ of the tutorial advising people to read: https://cloud.google.com/security/gdpr and _understand_ that they are _personally_ responsible for the safekeeping of any personal data they collect and store. And that in _addition_ to the data _collection_ form, they need a mechanism to allow people to contact them in order to _remove_ their data from their spreadsheet and any _other_ retrieval systems. The data collection spreadsheet should be treated with the same (_if not more_) respect as your _own_ personal/credit card details. Don't share it with anyone you would not trust with your own credit card.
Sign in to join this conversation.
No labels
Priority-1
Priority-1
Priority-1
Priority-1
Priority-1
Priority-1
Priority-1
Priority-1
awaiting-review
awaiting-review
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
bug
chore
chore
discuss
discuss
discuss
duplicate
duplicate
duplicate
duplicate
duplicate
duplicate
duplicate
duplicate
duplicate
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
enhancement
epic
epic
external-dependency
external-dependency
external-dependency
hacktoberfest-accepted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
help wanted
in-progress
in-progress
in-progress
in-review
invalid
invalid
invalid
invalid
invalid
invalid
invalid
invalid
invalid
merge-conflicts
merge-conflicts
please-test
please-test
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
question
spam
spam
starter
starter
starter
starter
starter
starter
starter
starter
starter
technical
technical
technical
technical
technical
user-feedback
user-feedback
user-feedback
user-feedback
user-feedback
user-feedback
wontfix
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github/learn-to-send-email-via-google-script-html-no-server#241
No description provided.