Privacy Policy
This policy covers the ParrotIt Setter product: authenticated setter access, organisation setup, form creation, submission management, and related operational data.
Last updated: 6 September 2026
What this policy covers
This page applies to people and organisations using ParrotIt as setters. That includes account sign-in, organisation privacy defaults, form creation, the setter Ledger, and compliance tooling. It does not replace the privacy policy shown on a specific published form, which may describe how a particular organisation handles responder data for that form.
Data handled in setter flows
- Account and authentication data used to sign setters in and keep access secure.
- Organisation profile and privacy-default data used to generate form-specific privacy policies.
- Form schemas, field structures, publishing metadata, and share identifiers.
- Form drafting briefs — the plain-English descriptions setters write when generating a form with AI.
- A summary of your organisation's earlier forms — the questions you usually add and the AI suggestions you usually delete — used to shape new drafts.
- Submission management, audit, review, export, and administrative activity connected to a setter workspace.
- Technical and security logs needed to maintain the service and investigate misuse.
- Browser-verification signals from the automated-traffic check described below.
Why this data is processed
- To provide authenticated access to the setter workspace and protect organisation data.
- To let setters create, publish, review, and manage forms and submissions.
- To generate or manage privacy-policy material and compliance support inside the setter product.
- To improve how ParrotIt drafts forms, including training future form-building models.
- To support reliability, fraud prevention, troubleshooting, and legal obligations.
Analytics cookies
We use Google Analytics to understand which pages help organisations set up forms — things like which parts of the builder get abandoned. It sets cookies in your browser and is provided by Google, who process that data on our behalf.
It is off until you agree. We ask once, on these organisation pages, and nothing is measured unless you choose “Allow”. Declining costs you no functionality, and you can change your mind at any time, here or under Privacy in the menu once you're signed in. Saying no stops the measuring straight away and removes the analytics cookies. Your answer is kept in this browser, so another browser or device asks again.
Analytics never runs on responder surfaces. People filling in your forms are not measured, are never asked to accept cookies, and their pages set no cookies at all.
Automated-traffic checks
To keep scripts off published forms, ParrotIt asks Cloudflare's Turnstile service to confirm that a request is coming from a real browser. It runs invisibly on both setter and responder pages and normally asks nobody anything.
Cloudflare receives the IP address, browser and operating system version of the device making the request, plus signals from the check itself. It does not receive form content or submission data. As ParrotIt uses it, the check sets no cookie and is not used for advertising. Cloudflare's terms for the service are in the Cloudflare Turnstile Privacy Policy.
This is a security control, not measurement, so it runs whether or not you allowed analytics cookies, and there is no per-form switch — a gate an organisation can leave off protects nobody.
Form drafting and product improvement
When you describe a form in your own words and let ParrotIt draft it, we keep that description alongside the structure of the form you went on to publish. Both are things you wrote as a setter: titles, section wording, questions, and the rules that decide what gets asked. We use them to make form drafting better, including training future form-building models.
The drafting model also sees a short summary of your organisation's earlier published forms: the questions you usually add yourself and the suggestions you usually delete, with how often. That is how a new draft follows the way you work. The summary carries the wording of those questions and nothing else — never an answer, an answer option, or a value you set on a field. We keep it with the draft, together with which of the model's suggestions you kept or deleted, for the same purpose.
Responder answers are never part of this. They are encrypted on the responder's device before they reach us, we cannot read them, and they are never used for training. If you turn off “share with AI” on a value list, the entries in that list are left out too.
This material is kept even if your organisation later closes its account, and identifying details are stripped from it before it is used.
What deletion removes
When a submission reaches the end of its retention rule, or a responder asks for it to be deleted, ParrotIt removes the encrypted answers. The submission's audit trail, and the fingerprint a certified record carries, stay so the history remains verifiable. Backups keep a copy of deleted data for up to 14 days before it is gone for good.
Important boundary
Setter privacy is not the same thing as responder privacy. Setters have accounts, workspaces, organisation configuration, and operational controls. Responders do not. The two are kept in separate policies so each stays clear about what actually happens.