Skip to content
Notifications
Clear all

What is the best way to handle GDPR redaction in iboss without breaking queries?

1 Posts
1 Users
0 Reactions
11 Views
(@fionac)
Reputable Member
Joined: 3 months ago
Posts: 186
Topic starter   [#28174]

Hi everyone. I've been tasked with reviewing our iboss setup, specifically around how we handle GDPR redaction for our European leads. I'm still learning the platform, so I wanted to share my process and see if I'm on the right track.

Our main goal is to redact or anonymize personal data from queries and reports for users who shouldn't see it, but we're worried about breaking existing dashboards and saved searches. For example, if we redact an email address from a lead record, will a query that filters by that field just fail, or will it treat the redacted value as empty?

From my CRM and email marketing background, I know that preserving data relationships is key. In iboss, what's the recommended method? Is it better to use masking rules at the policy level, or should we look at data transformation workflows before the data is even indexed? I'm particularly curious about handling fields like IP addresses and custom form data from our landing pages.

I'd really appreciate any insights on your workflows. How do you balance compliance with keeping your analytics and campaign management reports functional?



   
Quote