-
Notifications
You must be signed in to change notification settings - Fork 1.4k
adding event deletion guidance to docs #21980
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
Hi @hunterbeezley 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local. If you really require a preview url, reach out to one of the writers and they will generate one for you. |
netlify build fork |
✅ Your PR has been mirrored to our repository as PR #21985. |
netlify build fork |
✅ Your updates have been mirrored to our repository in PR #21985. |
|
||
If **sensitive data** (such as **PII**) has been unintentionally sent to New Relic and already stored in **NRDB**, you cannot delete it yourself. | ||
|
||
Once log data is written to the database, it is **not directly manageable or deletable by customers**. If you find that sensitive information has been ingested and stored, please contact [**New Relic Support**](https://docs.newrelic.com/docs/licenses/license-information/general-usage-licenses/global-technical-support-offerings/) for assistance with data removal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to merge both paragraphs into one:
You cannot delete sensitive data, such as Personally Identifiable Information (PII), yourself after it has been stored in NRDB. If you find that sensitive data has been ingested, you must contact New Relic Support for assistance with its removal.
src/content/docs/security/security-privacy/data-privacy/new-relic-personal-data-requests.mdx
Outdated
Show resolved
Hide resolved
|
||
If **sensitive data** (such as **PII**) has been unintentionally sent to New Relic and already stored in **NRDB**, you cannot delete it yourself. | ||
|
||
Once log data is written to the database, it is **not directly manageable or deletable by customers**. If you find that sensitive information has been ingested and stored, please contact [**New Relic Support**](https://docs.newrelic.com/docs/licenses/license-information/general-usage-licenses/global-technical-support-offerings/) for assistance with data removal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same suggestion as above:
You cannot delete sensitive data, such as Personally Identifiable Information (PII), yourself after it has been stored in NRDB. If you find that sensitive data has been ingested, you must contact New Relic Support for assistance with its removal.
netlify build fork |
1 similar comment
netlify build fork |
✅ Your updates have been mirrored to our repository in PR #21985. |
netlify build fork |
I am looking to add to two of our docs, some small guidance to customers on how to request to delete sensitive data already ingested into new relic.
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
links to related docs, screenshots, etc.