Data privacy related topics at Savage.

Table of Contents

📃 Documenting Changes to Privacy Procedures

Upon substantively changing privacy related settings/procedures, documentation of where/what was altered, needs to be kept in perpetuity.

Viewing Changes in Transcend

Viewing Changes in ConsentManager-net

📄 Canned Responses

VIP - Relayed DMCA that is NOT Actionable

UPDATE Privacy Policy on a Brand

The following is the end-to-end process of “how” to update a privacy policy at any given brand at Savage Ventures.

<aside> ✏️

<aside> <img src="notion://custom_emoji/a40ac211-d73e-4d6d-ad86-195ae92b3687/190b224b-0d20-80d0-ab23-007a953c1d92" alt="notion://custom_emoji/a40ac211-d73e-4d6d-ad86-195ae92b3687/190b224b-0d20-80d0-ab23-007a953c1d92" width="40px" />

WingManWP Team

Ensure to track time related to these tasks in Work Category Compliance > Privacy Compliance in JIRA

</aside>

  1. Receive Request from leadership to queue actions for updating a privacy policy
    1. READ/REVIEW the document / COMPLETE comments / FILL-IN any blanks (alongside Dan)
      1. ⚠️ If Raptive is present on the site = REQUEST the opt-out URL needed for the privacy policy body content link
    2. Log affirmative approval from Dan for the complete text to be published on a non-staging instance first.
    3. Email message body text to be sent out
      • Email Message - as of Nov 12 2025
    4. Date-Time (target) when the body content needs to be updated, and email send out completion.
      1. ⚠️ Ensure the public facing “Last updated date” is the date when the Privacy Policy is indeed published to the site.
  2. Queue shipping out the email message to the list of recipients received for this task
    1. ⚠️ Ensure the Savage Ventures Compliance Email shipping plugin is installed on the respective site.
    2. Updated Oct 15 2025: Dan stated that he is not requiring emails shipment before the public-facing text is updated. These actions must happen close together, but not in any required order.
  3. Queue publishing updated body-copy text on the Privacy Policy
    1. Although we will follow respective site’s github workflows for pushing this change via code, we ** DO NOT ** have to go thru preprod approvals.
    2. ⚠️ Ensure the Publish Date is the public visible date when the Privacy Policy was “last updated”. (Oct 27, Dan B).
    3. ⚠️ Ensure there are no ads rendering on the privacy policy page
  4. Queue triggering re-prompt (pop-up) consent to all visitors, upon a new Privacy Policy being published
    1. If the site operates ConsentManager, then trigger re-prompting all visitors.
    2. If the site operates a CMP that Savage Ventures does not have full control over, then implement custom WordPress pop-up informing visitors of new privacy policy
      1. Follow respective pathways to communicate with external partners for re-prompting of the CMP.
  5. Supervise technical completion
    1. Log completion of pushing changes to body-copy on the site // VIEW on production front-end
    2. Log completion of emails shipments // VIEW verbose logs of all the email addresses
    3. Log completion of re-triggering prompting consent (pop-up notice) to all visitors, upon a new privacy policy being updated
  6. RETURN Notes of Completion to compliance leadership (Dan B, as of Oct 2025)