[Privacy] Three GDPR Article 9 detectors are off by default but labelled as user-disabled #584

New issue

Closed

opened 2026-07-22 16:16:34 +00:00 by brenno · 0 comments

brenno commented

2026-07-22 16:16:34 +00:00

Owner

Found in the pre-publication first-run review, on a clean install.

Reproduce: delete ~/Library/Preferences/com.dewinter.ocideck.plist, start the app, accept, then open Settings → Security without touching anything.

What you see: under the heading "Disabled rules. These are not reported and not redacted. Tap to turn back on." sit three chips: ethnic origin, political opinion, sexual orientation. Nothing was ever switched off — this is the factory state. Meanwhile the quality panel promises to look for "special categories of personal data (GDPR art. 9/10)", and the README lists art. 9 special categories among the things OciWacht detects.

Why this must be fixed before publication: the wording "turn back on" tells the user they disabled these themselves, which is untrue. An outsider comparing this screen against the claim in the consent screen, the quality panel and the README concludes that art. 9 coverage is claimed but not delivered. If the off state is a deliberate choice about false positives — which would be entirely defensible, and consistent with how carefully the rest of the scanner is tuned — then it has to say so.

Proposal: change the heading to state the default and the reason ("Off by default — these rules produce many false reports. Tap to switch on."), and name the exception in the same breath wherever art. 9 coverage is claimed (README feature list, quality panel copy, docs/PRIVACY.md). If the intent was for them to be on, that is a one-line default change plus a look at the false-positive corpus.

Found in the pre-publication first-run review, on a clean install. **Reproduce:** delete `~/Library/Preferences/com.dewinter.ocideck.plist`, start the app, accept, then open Settings → Security without touching anything. **What you see:** under the heading "Disabled rules. These are not reported and not redacted. Tap to turn back on." sit three chips: `ethnic origin`, `political opinion`, `sexual orientation`. Nothing was ever switched off — this is the factory state. Meanwhile the quality panel promises to look for "special categories of personal data (GDPR art. 9/10)", and the README lists art. 9 special categories among the things OciWacht detects. **Why this must be fixed before publication:** the wording "turn back on" tells the user they disabled these themselves, which is untrue. An outsider comparing this screen against the claim in the consent screen, the quality panel and the README concludes that art. 9 coverage is claimed but not delivered. If the off state is a deliberate choice about false positives — which would be entirely defensible, and consistent with how carefully the rest of the scanner is tuned — then it has to say so. **Proposal:** change the heading to state the default and the reason ("Off by default — these rules produce many false reports. Tap to switch on."), and name the exception in the same breath wherever art. 9 coverage is claimed (README feature list, quality panel copy, `docs/PRIVACY.md`). If the intent was for them to be on, that is a one-line default change plus a look at the false-positive corpus.

brenno added the

privacy

bug

labels

2026-07-22 16:16:34 +00:00

brenno referenced this issue from a commit

2026-07-22 18:28:44 +00:00

docs+ui: zeg wat er standaard uit staat, en wat het zegel dekt

brenno referenced this issue from a pull request that will close it,

2026-07-22 18:28:46 +00:00

docs+ui: zeg wat er standaard uit staat, en wat het zegel dekt (#584, #581) #668

brenno closed this issue