We should also update our privacy review template to follow the new SPUR process along with other updates we are making to our auto-generated privacy bugs. Here's my proposed change:


" "
This template is used for one-off request for Chrome Privacy input.

<bold>If you already have a launch entry on crbug or Ariane, please don't create a review bug using this template.</bold> For crbug, simply change your Launch-Privacy- status to "ReviewRequested" and wait for your automated review bug. For Ariane, a review bug will find you or you can email chrome-privacy-core@.


1. If this  privacy review is associated to a feature tracking bug, what's the bug number?
Issue <insert issue number here>

2. In a few sentences, tell us about the proposed change, or existing issue you want our input or decision for?

3. Review go/cr-privacyreview-checklist. Answer any questions that are relevant to your change / issue.

4. Do you already have a PDD, or a server PDD for the server your client feature will call?

5. Do you have a detailed design doc?

6. Make sure you put all relevant folks in the Cc: field.


=====

More information about privacy reviews: http://go/chrome-privacy-reviews

Label description:
-N/A: the respective document does not need to be updated
-No: the respective document needs to be updated
-Yes: the respective document has been updated

This bug is used for documenting privacy reviews and for tracking necessary
changes to related documents.
Please try not to make legally-sensitive remarks.

" "

Labels:

Remove "Dev-PrivacyPolicyUpdated-" and "Restrict-View-ChromePrivacy"




* * * * * * * * * * * * * * * * * * * *
*           CURRENT LABELS            *
* * * * * * * * * * * * * * * * * * * *
Dev-PrivacyDesignDocUpdated-No
Dev-PrivacyPolicyUpdated-No
Dev-PrivacyWhitepaperUpdated-No
M-?
Restrict-View-ChromePrivacy
Review-Privacy




* * * * * * * * * * * * * * * * * * * *
*         CURRENT TEMPLATE            *
* * * * * * * * * * * * * * * * * * * *

Hello,

Please begin a privacy review for launch bug:
Issue <insert issue number here>

Feature owners, please follow the instructions and answer the questions at
goto.google.com/chrome-privacy-questions

(Additionally, if you already have a server side PDD, update the PDD and
add comments to the sections that changed from the previous version, and
include the link here. Then you can skip these questions.)

=====

More information about privacy reviews: http://go/chrome-privacy-reviews

Label description:
-N/A: the respective document does not need to be updated
-No: the respective document needs to be updated
-Yes: the respective document has been updated

This bug is used for documenting privacy reviews and for tracking necessary
changes to related documents.
Please try not to make legally-sensitive remarks.


* * * * * * * * * * * * * * * * * * * *
*           CURRENT LABELS            *
* * * * * * * * * * * * * * * * * * * *
Dev-PrivacyDesignDocUpdated-
Dev-PrivacyPolicyUpdated-
Dev-PrivacyWhitepaperUpdated-
M-?
Restrict-View-ChromePrivacy
Review-Privacy