From 376dcaa3c90ac941423770d7adb7d4468ac26b89 Mon Sep 17 00:00:00 2001 From: Alex Schofield Date: Sun, 2 Mar 2025 23:41:56 +0000 Subject: clarify how obfuscated data is returned in README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 16c5f94..c3f14a6 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ The MVP covers: 1. Reading a JSON string containing the S3 location of the CSV file and the names of the fields that are required to be obfuscated 2. Ingesting the CSV file containing data records (with a primary key) from an AWS S3 bucket 3. Obfuscating chosen PII fields (e.g. `name`, `email_address`) by replacing their values with an obfuscated string (`***`) -4. Producing an output CSV file (or a byte-stream) that maintains the original structure but with sensitive fields changed +4. Returning the obfuscated data as a byte-stream that maintains the original structure but with sensitive fields changed This meets the requirements under the General Data Protection Regulation [(GDPR)](https://ico.org.uk/media/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr-1-1.pdf) to ensure that all data containing information that can be used to identify an individual should be anonymised. -- cgit v1.2.3