diff --git a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
index 5d92e22eb4557f..03e52381f54372 100644
--- a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
+++ b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
@@ -20,15 +20,13 @@ With it enabled, Sentry will scrub the following:
   - passwd
   - api_key
   - apikey
-  - access_token
   - auth
   - credentials
   - mysql_pwd
-  - stripetoken
-  - card[number]
-  - github_token
   - privatekey
   - private_key
+  - token
+  - bearer
 - Values that contain strings in, or whose keynames are listed in, [Project] > Settings > Security & Privacy in "Additional Sensitive Fields".
   - An entry in "Additional Sensitive Fields" such as `mysekret`, for example, will cause the removal of any field named `mysekret`, but also removes any field _value_ that contains `mysekret`. Sentry does this to protect against sensitive data leaking as part of structured data that has been sent as a single string to Sentry (such as a JSON object that is stringified and embedded as JSON string in another JSON structure).
   - As an extreme example where this behavior can become surprising, the string `"Unexpected error"` will be removed from events if the entry `exp` is in "Additional Sensitive Fields".