Token exposed on client side

[vaishak10]

Description

While the task runs or when you navigate across different routes, came across a client side token call which gives a jwt token in response.
I am confused as to why such sensitive data is exposed and what is this used for. The least thing that can be done is masking the token value for client side.
Also is this a token already available to the user and get's expired once the task is created or any navigation is made back to the task to get the previous results?

Steps to reproduce

1. Create a Task.
2. Create a Prospect
3. Enter the necessary details
4. Run the task (While the task runs open your network tab and check for the token client side request)

Acknowledgements

• My issue title is concise, descriptive.
• I have searched the existing issues to make sure this bug has not been reported yet.
• I am using the latest version of superagent.
• I have provided enough information for the maintainers to reproduce and diagnose the issue.