Description

Hi! I'm a maintainer on an addon that's listed on AMO, and we (semi) recently were asked to update our privacy policy. I would like to be able to push updates to our privacy policy using our release workflow, rather than having to ping the person who's AMO account actually hosts the addon every time there's a change to our privacy policy.

So basically, I would like if there was a Privacy Policy (and probably EULA) key to the following external API endpoints:

• PATCH /api/v5/addons/addon/(int:id|string:slug|string:guid)/
• PUT /api/v5/addons/addon/(string:guid)/
• POST /api/v5/addons/addon/(int:addon_id|string:addon_slug|string:addon_guid)/versions/ (if it would make sense to add it there?)

Another possible solution is to add push/patch/put methods to the /api/v5/addons/addon/(int:id|string:slug|string:guid)/eula_policy/ endpoint.

Acceptance Criteria

### Milestones/checkpoints
- [x] Add a way to update privacy policies and/or EULAs to the external API.

Checks

• If the issue is ready to work on, I have removed the "needs:info" label.
• If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task