needing an hour or two to compile on bulk for an exotic audio codex I can understand, but taking that long for something as simple as .mp3 or .wav shouldn't take that long, especially if it's possible to compile the recording as it's being made in real time, because of how long it is taking for our recordings to populate raises concerns about security and customer privacy, especially if recording the calls in .wav it would take that long to bulk compile and scan before upload, meaning that our customer data could potentially be stored on a RingCX server somewhere, literally anywhere as far as we know, for expediency, our policy, and potential privacy concerns, we need those times shortened and those recordings directly uploaded to us.
Jeremy
supported this idea
·
needing an hour or two to compile on bulk for an exotic audio codex I can understand, but taking that long for something as simple as .mp3 or .wav shouldn't take that long, especially if it's possible to compile the recording as it's being made in real time, because of how long it is taking for our recordings to populate raises concerns about security and customer privacy, especially if recording the calls in .wav it would take that long to bulk compile and scan before upload, meaning that our customer data could potentially be stored on a RingCX server somewhere, literally anywhere as far as we know, for expediency, our policy, and potential privacy concerns, we need those times shortened and those recordings directly uploaded to us.