Now, data retention, some applications and some companies may not be able to store user’s data, in fact, security might be so important that the information may not be able to still be stored at all.
So by default, Cyclr will retain successful transaction and error transaction information, 31 days should anything comes up, come up, it allows us to debug it, it allows us to take a look through the information there and see where maybe the data is mal formatted or not successfully sent out and we can sort of look at the reasons why that’s happened.
Now, it could be that you don’t want that information stored at all. So if I hit zero, essentially, what that means is that the data will be deleted immediately. So once that transaction is finished, and everything’s moved through Cyclr, regardless of whether it’s successful or arid, that information will be cleared off.
And what that then means is that if it comes to debugging, we won’t be able to see anything, but you can assure your users that that information isn’t being stored anywhere, it’s just sort of being passed through for the sake of the processing. And then it’s deleted and cleared off the systems.
Now it could be you might need to do that for your compliance, you might need to do that, just to reassure your customers. But you do have the choice the option to decide how long data is retained for and what sort of works for you and what works for your company.
A successful transaction is something that goes through without an error. An error transaction, now that could be something as simple as the field doesn’t exist when you’ve made a call, like the response field that you’re making a filter and doesn’t come back, all the information doesn’t get sent out properly because the system either a rejects it or B Cyclr doesn’t build out the object or is unable to go out the opportunity to a lack of information. So that’s the difference between those two sorts of transactions.