Is there any possibility to use a finalise or send system event/status for your relevant? This would make the solution more automatic.
@wroos Just brainstorming: You might have some other required question that you could (ab)use for this. As long as it comes late in the form, after personal information is no longer needed, that should be fine.
Also, I’ve been wondering whether the following alternative would work: Instead of setting the relevant column for private fields, set the calculate and trigger columns. This can be used (I think) to transform the data at the moment when the trigger is selected. For example, you could use:
calculate=concat(substr(., 0, 1), '...')to keep the first character of the private value, but strip everything else. Maybe that would be good enough anonymization while still making the form results easier to interpret.calculate=digest(., 'SHA-256')to hash the value.
You could even use something likeif(starts-with(., 'HASH:'), ., concat('HASH:', digest(., 'SHA-256'))). This makes it idempotent, so that the value survives even if the enumerator selects and deselects the trigger field multiple times.
I haven’t tested any of these yet. If someone else does, I’d be happy to hear how it goes.
