Security issues are effectively addressed using the HTTPS protocol, which protects against network traffic interception. This allows you to confidently transfer brokerage report data and receive a completed tax return, ensuring their security.
If desired, it is possible to delete all user-related data, such as name, surname, and account number, from the broker’s report before sending the file. You can then request a declaration in the name of “John Doe” and add the correct user data on your own device at this stage. This is irrelevant for this service. In fact, from a data security perspective, it is not mandatory. However, if complete anonymity is a top priority, this option is available. To do this, open the broker report file in a simple text editor, such as Notepad, make the necessary changes, and save the file with the CSV extension. Using Excel for this purpose will most likely result in the service being unable to read the file correctly.
The declaration, like the broker’s report, is not stored on the server for security reasons. Instead, a hash code calculated based on the report is stored in the database. This algorithm is irreversible. No part of the original broker report or declaration can be recovered based on the calculated and stored hash key. However, this allows us to verify that the user has already requested the paid report, which eliminates the need to charge for re-generation. The service converts data streams, but does not store them. Since the data from the reports and submitted declarations is not stored on the server, it cannot be accessed, including by the service developers. Therefore, if you have any questions about your report, please send it to the support service email address: support@robotaxmaker.com.