Earlier quoted context omitted.
I don't have any evidence whatsoever but I speculate that between the options of: 1. collecting data and hiding it during times it was paused 2. checking if data collection is paused during collection time and keeping it/throwing it away Option (2) is the easiest and most foolproof. For (1), all it takes is a single tiny bug in any code that handles your data history and their whole privacy stance is shot.
How can these statemens both be true? "(2) is the easiest and most foolproof" That doesn't seem any easier; as hiding is harder than checking a bit and discarding at collection time. "For (1), all it takes is a single tiny bug in any code that handles your data history and their whole privacy stance is shot." That doesn't sound foolproof at all.
Checking a bit and discarding at collection time is the easiest. You need to ensure data collection is aware of this setting, and anything that manipulates this data doesn't need to care whether or not some data is "hidden" or not.
> That doesn't sound foolproof at all.
Right - If you go the route of collecting all data and hiding it later then all tools that interoperate with customer data need to make sure they don't accidentally expose "paused" data back to the customer.
Given two choices of throwing away data at collection time, or forever in the future trying to hide data from the customer, it seems simpler to throw away data at collection time.