diff --git a/develop-docs/sdk/foundations/transport/rate-limiting.mdx b/develop-docs/sdk/foundations/transport/rate-limiting.mdx
index e529ef2252b89..e1bed19427bee 100644
--- a/develop-docs/sdk/foundations/transport/rate-limiting.mdx
+++ b/develop-docs/sdk/foundations/transport/rate-limiting.mdx
@@ -94,14 +94,20 @@ While these [data categories](https://github.com/getsentry/relay/blob/master/rel
   - `security`: Events with event_type `csp`
   - `attachment`: Attachment bytes stored (unused for rate limiting)
   - `session`: Session update events
-  - `profile`: Profiling events
-  - `profile_chunk`: Continuous Profiling chunks
   - `replay`: Session Replays
   - `feedback`: User Feedbacks
   - `trace_metric`: Metric type events.
   - `trace_metric_byte`: Metric bytes stored.
   - `internal`: a sentry/system internal event[^internal]
 
+  Relay utilizes various data categories for profiles, allowing separate rate limiting for each. SDKs must implement the same logic applied to other data categories and discard the associated profiling data when a rate limit is active:
+
+  - `profile`: Profiling events for backend platforms.
+  - `profile_chunk`: Continuous Profiling chunks for backend platforms.
+  - `profile_chunk_ui`: Continuous Profiling chunks for UI platforms.
+  - `profile_backend`: Transaction profiles for backend platforms.
+  - `profile_ui`: Transaction profiles for UI platforms.
+
 - **Scope**: The unit / model in Sentry that quotas are enforced for.
   - `organization`
   - `project`