Though the playground isn't intended for use with sensitive information, we should still avoid including addresses in URLs to avoid any privacy risks.
The recent addition of analytics that are including URLs in the event parameters exacerbates this risk so it should be prioritized.
Here's an example of what's being passed when there are params included in the URL (there is some masking but that is from a third-party UI and doesn't mean they don't have the full address in their system):
At the same time, we want to balance privacy against the developer experience.
@BelfordZ recommends adding a "Copy" button to allow developers to save their input data from the playground in case they need it again later.
Though the playground isn't intended for use with sensitive information, we should still avoid including addresses in URLs to avoid any privacy risks.
The recent addition of analytics that are including URLs in the event parameters exacerbates this risk so it should be prioritized.
Here's an example of what's being passed when there are params included in the URL (there is some masking but that is from a third-party UI and doesn't mean they don't have the full address in their system):
At the same time, we want to balance privacy against the developer experience. @BelfordZ recommends adding a "Copy" button to allow developers to save their input data from the playground in case they need it again later.