Privacy policy fixes #233

Closed
opened 2019-07-22 15:35:44 +00:00 by jankstudio · 19 comments
jankstudio commented 2019-07-22 15:35:44 +00:00 (Migrated from gitlab.com)

We have to save the actual privacy text that the customer / user agreed to.

Confirming with privacy officer if we need to save the text per customer, or just versions of the text and link each customer to the version they agreed to. ---- confirmed, text needs to be saved

  • create PrivacyPolicy entity with id, name, content (text, since this will contain the privacy policy text).
  • link Customer entity to PrivacyPolicy many to one, bidirectional. Customer is owning side.
  • create crud ui forms / table list for PrivacyPolicy under Customer Support menu
  • add existing privacy policies (will get the text) and take note of ids. we should have 3, mobile app, promo, and third party
  • make migration command that links Customer to PrivacyPolicy. priv_promo and priv_third_party are booleans for the promo and third party privacy policies while flag_mobile_app will mean that the customer is a mobile app user and has accepted the terms for mobile app privacy policy
  • make sure all calls affecting flag_mobile_app, priv_third_party, priv_promo will also update the Customer link to PrivacyPolicy accepted by user
We have to save the actual privacy text that the customer / user agreed to. Confirming with privacy officer if we need to save the text per customer, or just versions of the text and link each customer to the version they agreed to. ---- confirmed, text needs to be saved * [x] create PrivacyPolicy entity with id, name, content (text, since this will contain the privacy policy text). * [x] link Customer entity to PrivacyPolicy many to one, bidirectional. Customer is owning side. * [x] create crud ui forms / table list for PrivacyPolicy under Customer Support menu * [ ] add existing privacy policies (will get the text) and take note of ids. we should have 3, mobile app, promo, and third party * [x] make migration command that links Customer to PrivacyPolicy. priv_promo and priv_third_party are booleans for the promo and third party privacy policies while flag_mobile_app will mean that the customer is a mobile app user and has accepted the terms for mobile app privacy policy * [x] make sure all calls affecting flag_mobile_app, priv_third_party, priv_promo will also update the Customer link to PrivacyPolicy accepted by user
korina.cordero commented 2019-07-23 01:37:29 +00:00 (Migrated from gitlab.com)

mentioned in merge request !274

mentioned in merge request !274
korina.cordero commented 2019-07-23 01:37:29 +00:00 (Migrated from gitlab.com)

created merge request !274 to address this issue

created merge request !274 to address this issue
jankstudio commented 2019-07-23 01:46:25 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
korina.cordero commented 2019-07-23 02:23:44 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
korina.cordero commented 2019-07-23 03:40:16 +00:00 (Migrated from gitlab.com)

mentioned in commit 4a13c3e615

mentioned in commit 4a13c3e6155c9537c6f8a46ece48bef63322197a
korina.cordero commented 2019-07-23 03:40:16 +00:00 (Migrated from gitlab.com)

marked the checklist item create PrivacyPolicy entity with id, name, content (text, since this will contain the privacy policy text). as completed

marked the checklist item **create PrivacyPolicy entity with id, name, content (text, since this will contain the privacy policy text).** as completed
korina.cordero commented 2019-07-23 03:40:19 +00:00 (Migrated from gitlab.com)

marked the checklist item link Customer entity to PrivacyPolicy many to one, bidirectional. Customer is owning side. as completed

marked the checklist item **link Customer entity to PrivacyPolicy many to one, bidirectional. Customer is owning side.** as completed
korina.cordero commented 2019-07-23 04:02:18 +00:00 (Migrated from gitlab.com)

mentioned in commit 1535fd9cd9

mentioned in commit 1535fd9cd96d877a4b8bdb770e9ec4bab6edf4c7
korina.cordero commented 2019-07-23 09:57:37 +00:00 (Migrated from gitlab.com)

marked the checklist item create crud ui forms / table list for PrivacyPolicy under Customer Support menu as completed

marked the checklist item **create crud ui forms / table list for PrivacyPolicy under Customer Support menu** as completed
korina.cordero commented 2019-07-23 09:57:37 +00:00 (Migrated from gitlab.com)

mentioned in commit 50a3afb213

mentioned in commit 50a3afb21326034b32fec58d88a159b9bcf3e0ee
korina.cordero commented 2019-07-24 08:46:08 +00:00 (Migrated from gitlab.com)

marked the checklist item make sure all calls affecting flag_mobile_app, priv_third_party, priv_promo will also update the Customer link to PrivacyPolicy accepted by user as completed

marked the checklist item **make sure all calls affecting flag_mobile_app, priv_third_party, priv_promo will also update the Customer link to PrivacyPolicy accepted by user** as completed
korina.cordero commented 2019-07-24 08:46:10 +00:00 (Migrated from gitlab.com)

mentioned in commit b657ae95d5

mentioned in commit b657ae95d511882d1b36fd9c6d37ea905a556992
korina.cordero commented 2019-07-24 12:55:25 +00:00 (Migrated from gitlab.com)

mentioned in commit 830803ac2d

mentioned in commit 830803ac2d5794ef5f096d11b4585ded8cff8f32
korina.cordero commented 2019-07-24 12:55:59 +00:00 (Migrated from gitlab.com)

marked the checklist item make migration command that links Customer to PrivacyPolicy. priv_promo and priv_third_party are booleans for the promo and third party privacy policies while flag_mobile_app will mean that the customer is a mobile app user and has accepted the terms for mobile app privacy policy as completed

marked the checklist item **make migration command that links Customer to PrivacyPolicy. priv_promo and priv_third_party are booleans for the promo and third party privacy policies while flag_mobile_app will mean that the customer is a mobile app user and has accepted the terms for mobile app privacy policy** as completed
korina.cordero commented 2019-07-24 12:57:55 +00:00 (Migrated from gitlab.com)

closed via merge request !274

closed via merge request !274
korina.cordero commented 2019-07-24 12:57:59 +00:00 (Migrated from gitlab.com)

mentioned in commit 498772ea62

mentioned in commit 498772ea629c664bdaaab93e48d98c927e19760a
korina.cordero commented 2019-07-25 00:42:56 +00:00 (Migrated from gitlab.com)

mentioned in commit 06adce710f

mentioned in commit 06adce710f6a2b2017eeb7f620595038772538d2
korina.cordero commented 2019-07-25 00:43:18 +00:00 (Migrated from gitlab.com)

mentioned in merge request !275

mentioned in merge request !275
korina.cordero commented 2019-07-25 00:43:35 +00:00 (Migrated from gitlab.com)

mentioned in commit c8cb0baec0

mentioned in commit c8cb0baec096e859df0ea7a0d09f91d6b338f95f
Sign in to join this conversation.
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: rgutierrez/resq#233
No description provided.