<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>webform replacement on asdfasdfasdfasdfddd</title><link>https://academy.test.quriobot.com/tags/webform-replacement/</link><description>Recent content in webform replacement on asdfasdfasdfasdfddd</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://academy.test.quriobot.com/tags/webform-replacement/index.xml" rel="self" type="application/rss+xml"/><item><title>How to replace my existing webform with a shiny Quriobot?</title><link>https://academy.test.quriobot.com/advanced-options-api-js-response-data-etc/how-to-replace-my-existing-webform-with-a-shiny-quriobot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://academy.test.quriobot.com/advanced-options-api-js-response-data-etc/how-to-replace-my-existing-webform-with-a-shiny-quriobot/</guid><description>Quriobot allows a way of integration that makes it totally transparent: it&amp;rsquo;s your user&amp;rsquo;s (personal) data and your storage or endpoint which will receive the data.
Privacy: No data will be stored on the Quriobot side in this case, as the data might be sensitive, for example, contain passwords.
Quriobot will be executed in the context of your webpage so it can also be placed in the auth-protected pages and call endpoints that are not public.</description></item></channel></rss>