{"_id":"5b0431512577f600032f98c2","project":"54aa7f773b56130b0056c86e","version":{"_id":"576a656c6f15260e001f8938","__v":3,"project":"54aa7f773b56130b0056c86e","createdAt":"2016-06-22T10:16:12.661Z","releaseDate":"2016-06-22T10:16:12.661Z","categories":["576a656c6f15260e001f8939","576a656c6f15260e001f893a","576a656c6f15260e001f893b","576a656c6f15260e001f893c","576a656c6f15260e001f893d","576a656c6f15260e001f893e","576a656c6f15260e001f893f","5797787ce2d8f40e0052b4a6","5b041bc0769904000374c645"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"For Marketers","version_clean":"4.0.0","version":"4.0"},"category":{"_id":"5b041bc0769904000374c645","project":"54aa7f773b56130b0056c86e","version":"576a656c6f15260e001f8938","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2018-05-22T13:31:44.791Z","from_sync":false,"order":1,"slug":"gdpr-data-protection","title":"GDPR/ Data Protection"},"user":"577cf7765fd4de0e00cc3d50","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-05-22T15:03:45.964Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"[block:api-header]\n{\n  \"title\": \"Introduction\"\n}\n[/block]\nArticles 16 and 17 of the GDPR outline the right to erasure, also known as the right to be forgotten. All users have the right to be erased if any of the following criteria apply: \n\n1. Where your personal data is no longer necessary in relation to the purpose for which it was collected or processed;\n2. Where you withdraw your consent to the processing and there is no other lawful basis for processing the data;\n3. Where you object to the processing and there is no overriding legitimate grounds for continuing the processing (See point 6 below).\n4. Where you object to the processing and your personal data is being processed for direct marketing purposes (See point 6 below);\n5. Where your personal data has been unlawfully processed;\n6. Where your personal data have to be erased in order to comply with a legal obligation;\n7. Where your personal data has been collected in relation to the offer of information society\nservices to a child.\n\nIt is the right of the data controller to erase user data for any user based on a request that meets any of the above criteria. Pulsate has a number of tools to enable this, however, it remains the obligation of the data controller to ensure that user data is erased and to determine whether any of the above criteria has been met. \n\n\n[block:api-header]\n{\n  \"title\": \"Erase a Pulsate User and their Data\"\n}\n[/block]\nThere are a number of methods that can be utilised in Pulsate erase a user and all of their data:\n\n- Delete a user and their data in the Pulsate CMS\n- Send an API call to Pulsate to delete a user and their data via the Pulsate Delete User endpoint\n\n\n[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"Deleted Users\",\n  \"body\": \"Please note that when a user is deleted in Pulsate, all historic data for that user will be deleted including campaign data, segment data, user messages and geofence and beacon data as well as all events and custom attributes for that user. This may result in some campaign or segment statistics being altered as the previous user data for a deleted individual will be erased.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Delete a User and their Data in the Pulsate CMS\"\n}\n[/block]\nTo manually delete a user using the Pulsate CMS, go to that user's profile page and click the settings cog and press Delete. \n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/50de9c1-Screenshot_2018-05-23_09.07.21.png\",\n        \"Screenshot 2018-05-23 09.07.21.png\",\n        1420,\n        678,\n        \"#e7eaea\"\n      ],\n      \"caption\": \"Delete User\"\n    }\n  ]\n}\n[/block]\nWhen you press Delete, you will be asked to confirm this action before it is completed. \n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/a6c4811-Screenshot_2018-05-23_09.08.24.png\",\n        \"Screenshot 2018-05-23 09.08.24.png\",\n        1400,\n        580,\n        \"#e6e8e8\"\n      ],\n      \"caption\": \"Confirm Deletion\"\n    }\n  ]\n}\n[/block]\nTo confirm that you wish the user to be Deleted, click Delete User.\n[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"Deleted Users\",\n  \"body\": \"When a user is deleted from Pulsate, that user will be blocked form all future Pulsate sessions and all future inbox requests for that user will also be blocked. If we have been sent an alias for a user, we will block start session and get inbox requests for that user on all current and future devices that use that alias. If no alias is present, the user will be blocked based on their device GUID. \\n\\nIf a user is deleted by mistake or a user changes their mind about wanting to be deleted, please contact Pulsate directly to request that the start session and get in box block is removed for a user. No historic data for that user will be recoverable but they will be able to use Pulsate again.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Delete a User and their Data via API call\"\n}\n[/block]\nTo delete a user and their data using the Pulsate API, please see our documentation [here](https://pulsate.readme.io/docs/users-delete-one).\n\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Deletion Timeframe\",\n  \"body\": \"When a user and their data is deleted it may take Pulsate some time to delete all of the user data for an individual and, depending on how many concurrent delete requests are underway, the user deletion may be placed in a queue to ensure that our system is not placed under unnecessary strain. \\n\\nWhen a delete action is completed, Pulsate will automatically send an email to the admin that instituted the delete action confirming that all user data for that individual has been deleted. That email will act as a confirmation that the delete action has been successfully completed.\"\n}\n[/block]","excerpt":"","slug":"deleting-user-data-in-pulsate","type":"basic","title":"Deleting User Data in Pulsate"}

Deleting User Data in Pulsate


[block:api-header] { "title": "Introduction" } [/block] Articles 16 and 17 of the GDPR outline the right to erasure, also known as the right to be forgotten. All users have the right to be erased if any of the following criteria apply: 1. Where your personal data is no longer necessary in relation to the purpose for which it was collected or processed; 2. Where you withdraw your consent to the processing and there is no other lawful basis for processing the data; 3. Where you object to the processing and there is no overriding legitimate grounds for continuing the processing (See point 6 below). 4. Where you object to the processing and your personal data is being processed for direct marketing purposes (See point 6 below); 5. Where your personal data has been unlawfully processed; 6. Where your personal data have to be erased in order to comply with a legal obligation; 7. Where your personal data has been collected in relation to the offer of information society services to a child. It is the right of the data controller to erase user data for any user based on a request that meets any of the above criteria. Pulsate has a number of tools to enable this, however, it remains the obligation of the data controller to ensure that user data is erased and to determine whether any of the above criteria has been met. [block:api-header] { "title": "Erase a Pulsate User and their Data" } [/block] There are a number of methods that can be utilised in Pulsate erase a user and all of their data: - Delete a user and their data in the Pulsate CMS - Send an API call to Pulsate to delete a user and their data via the Pulsate Delete User endpoint [block:callout] { "type": "danger", "title": "Deleted Users", "body": "Please note that when a user is deleted in Pulsate, all historic data for that user will be deleted including campaign data, segment data, user messages and geofence and beacon data as well as all events and custom attributes for that user. This may result in some campaign or segment statistics being altered as the previous user data for a deleted individual will be erased." } [/block] [block:api-header] { "title": "Delete a User and their Data in the Pulsate CMS" } [/block] To manually delete a user using the Pulsate CMS, go to that user's profile page and click the settings cog and press Delete. [block:image] { "images": [ { "image": [ "https://files.readme.io/50de9c1-Screenshot_2018-05-23_09.07.21.png", "Screenshot 2018-05-23 09.07.21.png", 1420, 678, "#e7eaea" ], "caption": "Delete User" } ] } [/block] When you press Delete, you will be asked to confirm this action before it is completed. [block:image] { "images": [ { "image": [ "https://files.readme.io/a6c4811-Screenshot_2018-05-23_09.08.24.png", "Screenshot 2018-05-23 09.08.24.png", 1400, 580, "#e6e8e8" ], "caption": "Confirm Deletion" } ] } [/block] To confirm that you wish the user to be Deleted, click Delete User. [block:callout] { "type": "danger", "title": "Deleted Users", "body": "When a user is deleted from Pulsate, that user will be blocked form all future Pulsate sessions and all future inbox requests for that user will also be blocked. If we have been sent an alias for a user, we will block start session and get inbox requests for that user on all current and future devices that use that alias. If no alias is present, the user will be blocked based on their device GUID. \n\nIf a user is deleted by mistake or a user changes their mind about wanting to be deleted, please contact Pulsate directly to request that the start session and get in box block is removed for a user. No historic data for that user will be recoverable but they will be able to use Pulsate again." } [/block] [block:api-header] { "title": "Delete a User and their Data via API call" } [/block] To delete a user and their data using the Pulsate API, please see our documentation [here](https://pulsate.readme.io/docs/users-delete-one). [block:callout] { "type": "info", "title": "Deletion Timeframe", "body": "When a user and their data is deleted it may take Pulsate some time to delete all of the user data for an individual and, depending on how many concurrent delete requests are underway, the user deletion may be placed in a queue to ensure that our system is not placed under unnecessary strain. \n\nWhen a delete action is completed, Pulsate will automatically send an email to the admin that instituted the delete action confirming that all user data for that individual has been deleted. That email will act as a confirmation that the delete action has been successfully completed." } [/block]