Skip to content
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

Session Replay (Native iOS and React Native) Granular Privacy Controls #716

Open
dannyrb opened this issue Aug 19, 2024 · 2 comments
Open
Labels
question Further information is requested

Comments

@dannyrb
Copy link

dannyrb commented Aug 19, 2024

Question

Hello, the documentation is very clear about how to set a defaultPrivacyLevel. This is great, but we often want to "mask everything by default", and then opt-in individual fields and sections of the application to be unmasked.

What I don't see is how to accomplish this for Native iOS or React Native in the current documentation. Searching the code base also did not yield any obvious clues. Is this an unimplemented or undocumented feature? Is it worth submitting a feature request for this functionality?

Notably, text extraction does not seem to account for anything other than the SessionReplayViewTreeRecordingContext, which appears to be scoped to the view? Any/all help here would be appreciated.

(We have both Native iOS applications and are enrolled in the private React Native beta)

@dannyrb dannyrb added the question Further information is requested label Aug 19, 2024
@marco-saia-datadog
Copy link
Member

Hi @dannyrb! 👋 Thank you for reaching out! Apologies for the delay.

We are currently working on improving Privacy Controls and your feedback is very valuable.

I would suggest submitting a feature request where you describe the functionality you are looking for. We can then internally discuss the requested features, and keep you posted about the updates on both native and RN SDKs.

Does it sound good to you?

@dannyrb
Copy link
Author

dannyrb commented Aug 26, 2024

👋🏻 @marco-saia-datadog, thanks for the response!

I believe we are working with support and our CSM to submit a formal feature request. Based on your response, it does sound like this is functionality that does not yet exist. Is it also safe to assume that you're not "accepting PRs" to add this functionality?

I will refer our CSM to this GitHub issue as a reference. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants