3 ms·
hey @yaseer, Really cool idea, thanks for sharing! RPA is a great, underserved niche for the SMBs. I've read through your privacy policy but i'd like some m
by wheelerwj 6y ago
hey @yaseer, Really cool idea, thanks for sharing! RPA is a great, underserved niche for the SMBs.
I've read through your privacy policy but i'd like some more clarification.
specifically, can you talk about exactly what data is sent to your servers? For example, if i use Axiom to login to a vendor site, those log on credentials should be stored only locally correct? Does your team have the ability to access any of the data that would be retrieved from the vendor application? I have a few really solid use cases but I need to cover the data privacy concerns first.
- yaseer 6y agoYep, of course. That's right; Right now, we don't store credentials. The cookie from your local machine when logged in is passed to axiom locally, and never sent to us. We store the code for your script on our servers. This is necessary to update scripts for future versions of axiom. We do not store the data this code processes. We do have a cloud version upcoming that will process data on our servers, but this will be optional, and not enforced.
- wheelerwj 6y agoThanks, for example, you would be able to see the steps of the automation, and the site (full URL) where the automation is targeted, the name of the fields being captured during scraping, and you might receive some data about the success of the step/process. But you do not receive any feedback about whats gathered or returned to the desktop. Cloud version could be cool for some people but i think it might kill any shot at the industry I serve.
- yaseer 6y agoYes, that's exactly right - we would see the URLs, the names of fields (from the DOM), and success states. Just not the data itself. It's basically what would be stored in a web-scraping or automated testing script.