From here
Background
Currently some fields are left behind in state masking which is a security vulnerability. We need to make sure that no private information is shared when exporting one's Onyx state through Troubleshoot.
Problem
When users export their Onyx state through the Troubleshoot feature, sensitive personal data remains visible in the exported text files, which creates a security vulnerability that could lead to unauthorized account access.
Solution
Expand the masking rules so that no private information is shared when exporting one’s Onyx state through Troubleshoot.
You can find the list of keys in attached file. This is not sensitive information per se, but its not needed for the purpose of exporting the onyx state so we can mask it
Issue Owner
Current Issue Owner: @dylanexpensifyUpwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021965074993794679004
- Upwork Job ID: 1965074993794679004
- Last Price Increase: 2025-09-08
From here
Background
Currently some fields are left behind in state masking which is a security vulnerability. We need to make sure that no private information is shared when exporting one's Onyx state through Troubleshoot.
Problem
When users export their Onyx state through the Troubleshoot feature, sensitive personal data remains visible in the exported text files, which creates a security vulnerability that could lead to unauthorized account access.
Solution
Expand the masking rules so that no private information is shared when exporting one’s Onyx state through Troubleshoot.
You can find the list of keys in attached file. This is not sensitive information per se, but its not needed for the purpose of exporting the onyx state so we can mask it
Issue Owner
Current Issue Owner: @dylanexpensifyUpwork Automation - Do Not Edit