Privacy policy

Who this covers

This policy covers two groups: people who create a Qwenvo account and build forms (account holders), and people who fill in a form built with Qwenvo (respondents). Qwenvo is operated by an independent team; contact details are at the end.

What we store about account holders

Your email address, name and a hashed password, or the identifier your Google or Apple account gives us when you sign in with it. The forms you build, their settings and their version history. Workspace membership, API keys you create, notification preferences and an audit log of changes in the workspace.

For security: the devices you have signed in from (browser, operating system and a shortened IP address), two-step verification secrets if you enable it, and rate-limit counters.

What we store about respondents

The answers submitted through a form, including uploaded files, signatures and, when the form captures them, partial answers typed before leaving. Technical details of the submission: time, a shortened IP address, browser and country, used for spam checks, duplicate prevention and the form's analytics. If the form includes a payment, the card is handled by Stripe; Qwenvo stores only the payment reference and status, never card numbers.

The account holder who built the form decides what it asks and is responsible for telling respondents how they will use the answers. Requests about answers you gave should go to them first; if you cannot reach them, contact us and we will help.

AI processing

Submissions can be read by an AI model to assign a category, priority, sentiment and summary, and to draft a reply, so the account holder can sort their inbox. The text of the submission is sent to the model provider for that purpose only, is not used to train models, and the result is stored with the submission.

Who else sees data

Service providers that run the product for us: the hosting provider for servers and backups, the email provider for notifications and login links, Stripe for payments, and the AI model provider for triage. Each processes data only on our instructions. Integrations you switch on yourself (Google Sheets, Slack, Notion, webhooks, Zapier, Make and others) receive the submissions you route to them under their own terms.

We do not sell personal data and do not show advertising.

Cookies

The app uses a session cookie to keep you signed in and a few preference cookies for the editor. Public forms set a cookie only when the form owner enables duplicate prevention by browser. Form analytics are anonymous and cookie-free.

Retention and deletion

Submissions stay until the account holder deletes them or sets an automatic retention period on the form. Deleting a form moves it to the trash for 30 days, then removes it and its submissions. Deleting your account removes your forms, submissions, files and workspaces; nightly backups are kept for 14 days and then overwritten. Audit log entries are kept for 90 days.

Your rights

You can export your forms and submissions from the app at any time, change your email and password, and delete your account from Settings. If you want a copy of what we hold about you, a correction, or deletion of something you cannot remove yourself, email us and we will answer within 30 days.

Changes and contact

This page is the current policy; the date at the top changes when the text does. Questions go to the support address on the contact page.