tree: 7f9b7609de7c0697faec450b627c0102c45c4604 [path history] [tgz]
  1. BUILD.gn
  2. DEPS
  3. OWNERS
  4. README.md
  5. consent_auditor.h
  6. consent_auditor_impl.cc
  7. consent_auditor_impl.h
  8. consent_auditor_impl_unittest.cc
  9. consent_sync_bridge.h
  10. consent_sync_bridge_impl.cc
  11. consent_sync_bridge_impl.h
  12. consent_sync_bridge_impl_unittest.cc
  13. fake_consent_auditor.cc
  14. fake_consent_auditor.h
  15. pref_names.cc
  16. pref_names.h
components/consent_auditor/README.md

Consent Auditor

The consent auditor component is a service containing methods used for recording and retrieving the records of the exact language the user consented to when enabling a feature.

These methods should be called from any UI which enables a feature based on the user's consent, and record the consent language that the user has seen. If we later find out there was a mistranslation, need to expand the scope of a setting etc., we will know which users are affected.

TO EMPHASIZE, these methods should ALWAYS be called from the corresponding UI, not from the backend code or pref change observers. The latter could cause the consent to be wrongfully recorded if feature was enabled through other means (through extensions, a new UI surface added, or even a bug).

Consents related to local features will be stored in a local preference.

Consents related to features for signed-in users will be stored in the user's Google account.