Note on additional charges for deletions

src/privacy/faq.md

@@ -78,3 +78,6 @@ Segment supports the following regulation types:
 - **SUPPRESS_WITH_DELETE**: Suppress new data based on the `userId` and also delete all existing data for that ID from your workspace and our internal archives. While Segment forwards the deletion request to your downstream destinations, Segment cannot guarantee deletion in your third-party tools.
 - **DELETE_INTERNAL**: Deletes user data from within Segment archives only and not from any connected destinations.
 - **DELETE_ONLY**: Deletes user data from Segment and your connected warehouses. Also sends a deletion request to your downstream destinations.
+
+> info "" 
+> Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might lead to additional charges levied by your destination providers.

src/privacy/user-deletion-and-suppression.md

@@ -31,6 +31,9 @@ The following regulation types are available:
  - **SUPPRESS_WITH_DELETE_INTERNAL:** Suppress new data and delete from Segment internals only
  - **DELETE_ONLY:** Delete existing data without suppressing any new data
 
+> info "" 
+> Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might lead to additional charges levied by your destination providers.
+
 ## Suppression Support and the Right to Revoke Consent
 
 `SUPPRESS` regulations add a user to your suppression list by the `userId`. Segment blocks suppressed users across all sources; messages you send to Segment with a suppressed `userId` are blocked at the API. These messages do not appear in the debugger, are not saved in archives and systems, and are not sent to any downstream server-side destinations. However, if you set up a destination in [device-mode](/docs/connections/destinations/#connection-modes), the events are sent directly to destinations as well. In this case, Suppression doesn't suppress the events.