Add-ons/Reviewers/Guide/Review Decision: Difference between revisions

Jump to navigation Jump to search
→‎Monetization: Add special case for missing user control mechanism involving personal data
(→‎Content Policy: Add clarification on how to reject internal/private use add-ons)
(→‎Monetization: Add special case for missing user control mechanism involving personal data)
Line 217: Line 217:
|-
|-
| The add-on has a monetization feature but does not present a user control mechanism at startup. || Delayed Reject
| The add-on has a monetization feature but does not present a user control mechanism at startup. || Delayed Reject
|-
| The add-on has a monetization feature without a user control mechanism, which involves transmitting personal data. || Reject Immediately
|-
|-
| The monetization feature sends personal data, but the user control mechanism at startup is not an opt-in (e.g. default choice is to accept). || Reject Immediately
| The monetization feature sends personal data, but the user control mechanism at startup is not an opt-in (e.g. default choice is to accept). || Reject Immediately
251

edits

Navigation menu