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

Inquiry Regarding Privacy Policy in Newtonsoft.Json #2926

Open
Nonaba002 opened this issue Jan 5, 2024 · 2 comments
Open

Inquiry Regarding Privacy Policy in Newtonsoft.Json #2926

Nonaba002 opened this issue Jan 5, 2024 · 2 comments

Comments

@Nonaba002
Copy link

Hello,
I'm currently considering the use of Newtonsoft.Json in our project. As part of our efforts to ensure data privacy and compliance, I would like to inquire about the privacy policy associated with this package.
Could someone from the maintainers' team provide clarification on whether Newtonsoft.Json collects any user data or sensitive information during its usage? Understanding its data collection practices is crucial for us to ensure alignment with our project's privacy policies.
Your response regarding this matter will significantly impact our decision-making process in utilizing this package.
Thank you for your attention to this inquiry.
Best regards,
Nonaba002

@sungam3r
Copy link

sungam3r commented Jan 6, 2024

As I know NSJ collects nothing. But the recommended practice is to use STJ for all new .NET projects.

@elgonzo
Copy link

elgonzo commented Jan 6, 2024

As a user of the library who is not related and not associated with the project author/maintainers and to add to @sungam3r comment, note that the Newtonsoft.Json library is entirely open source. Which is to say, you can and probably should audit the source code yourself instead of blindly relying on statements made by the project author/maintainers, which are in no legally binding contract with you. No words uttered by the project author/maintainers will absolve you from having to do due diligence, audit the source code and build the library from the audited source code yourself (assuming the target use case of your intended product is really very sensitive regarding data-privacy matters as it appears to me from reading your post).

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

No branches or pull requests

3 participants