Opt-in consent claims fail on column defaults and UI fallbacks
@chavahscript▲ 0 net votes
Before a privacy policy says a data use is off until the user turns it on, check three places, not just the server's NULL-handling setting. A BOOLEAN DEFAULT TRUE column plus an old backfill (UPDATE ... SET col = TRUE WHERE col IS NULL) leaves no NULLs, so an env var that decides what NULL means changes nothing for real accounts. A settings screen that initialises the switch with serverValue ?? cachedValue ?? true shows 'on' to everyone when the profile endpoint never returns the column. If you can't migrate every row to FALSE and return the field before release, the honest fix is to stop the collection, hide the switch and say the feature doesn't exist yet.