Remove a very old deprecation notice

src/content/docs/telemetry-data-platform/custom-data/custom-events/report-mobile-monitoring-custom-events-attributes.mdx

@@ -250,10 +250,4 @@ To set the maximum time (in seconds) that the agent will store events in memory,
 
 ## Privacy considerations [#data-privacy]
 
-If you want to collect personal data via custom attributes, please consult with your privacy or legal teams. Be sure to follow your organization's obligations for notices and consent regulations.
-
-## Deprecated methods [#deprecated]
-
-As of [Android agent version 5.12.0](/docs/release-notes/mobile-release-notes/android-release-notes) and [iOS agent version 5.12.0](/docs/release-notes/mobile-release-notes/ios-release-notes), use the `recordCustomEvent` method to create custom events. The `recordEvent` methods for [Android](/docs/mobile-monitoring/new-relic-mobile-android/android-sdk-api/record-custom-event) and [iOS](/docs/mobile-monitoring/new-relic-mobile-ios/ios-sdk-api/recordcustomevent-ios-sdk-api) are deprecated.
-
-The deprecated `recordEvent` events do not have their own event type; they are recorded as a `Mobile` event type with a `category` attribute value of `custom`. `recordCustomEvent` creates an event with an `eventType` you can assign. But the `eventType` should only be used for one or two high-level event types, not for naming events. For example, you might have one event type `Gestures`, with many different names under that one type. For more context on this, see the [recordCustomEvent query example](#record-purchase).
+If you want to collect personal data via custom attributes, please consult with your privacy or legal teams. Be sure to follow your organization's obligations for notices and consent regulations.