
ParrotIt
ParrotIt Responder
This policy covers the responder-facing side of ParrotIt: opening forms, using local saved data, interacting with cards and devices, and submitting information without creating a responder account.
Last updated: 22 October 2026
This page applies to responder use of ParrotIt forms and responder-side device flows. It covers accountless responder access, local saved-data behaviour, form submission flows, and related card or handoff interactions where available.
Saved answers, phone recovery and AI connections are ParrotIt features for people aged 13 or over. Filling in a form is between you and the organisation that published it. If you are under 18, that organisation should have arranged it with a parent or guardian.
You can choose to connect an AI assistant to your saved answers. If you do, every read or save the assistant makes happens on your device, and every read leaves a receipt you can see on the AI activity page. Sensitive answers need your explicit approval before an assistant can read them. If you never connect an assistant, none of this applies.
ParrotIt does not use your answers to train AI, and cannot: they are encrypted before they leave your device, so there is nothing readable for a model to learn from. ParrotIt's own AI features work from the kinds of questions forms ask, never from what you answered, with one exception described below. If you connect an assistant, it reads on your device only, and what it does with what you allow it to read is between you and that assistant.
ParrotIt's home page offers an Ask ParrotIt form, for questions about ParrotIt itself. This is the one exception to the line above, so it is worth being exact about.
The question you type there is sent to our AI provider, OpenAI, so it can be answered. It is sent as you typed it, because a model cannot read encrypted text. ParrotIt does not store that copy of your question, and the answer is not kept. If you give an email address on that form so we can send you ParrotIt updates, the address is not sent to the model.
Your submission of that form is encrypted on your device like any other, so the copy ParrotIt keeps is one we cannot read. The answer is written only from ParrotIt's own published material. It cannot see your saved answers, any submission you have sent, or anything about an organisation that sent you here.
This applies only to that one form. Answers you give on an organisation's form are never sent to a model.
An organisation can share a submission you sent with a partner organisation only through ParrotIt's sharing mechanism, which keeps the content encrypted for the named partner. Every share is recorded in that submission's history, so you can always see who has received it.
If an organisation gives you a ParrotIt Key with a tag, answers you give with it are also locked to that tag. Tapping the Key at that organisation's kiosk, with its PIN if it has one, brings your earlier answers back so you do not have to give them again. The organisation can turn this off for any form. If the tag is lost, the organisation can replace it, and the old tag stops working.
If the Key has been made yours, you can also read the answers given with it.
To reduce repeat questions, ParrotIt keeps aggregate counts of which kinds of fields forms ask for — for example, how often forms ask for a date of birth. These counts never include your answers, and they are not linked to who you are.
A published form can also add anonymous counters when it opens, when a section is reached, when the Save button succeeds, and when the form is submitted. These are stored as daily totals for that form version. They contain no responder, device or session ID, no cookie or fingerprint, no answer, and no field label. They cannot be used to reconstruct one person's journey.
You can request deletion of a submission yourself, from your History: open the submission and choose Request deletion. This removes the encrypted copy from ParrotIt-controlled systems and asks the organisation to delete any copies it holds.
Two things survive a deletion. Our backups keep a copy for up to 14 days before it is gone for good. And if the submission was certified, the certificate keeps a fingerprint of what was sent, so the public proof page can still show that a record existed even though the answers themselves have been removed.
ParrotIt uses a service called Sentry to receive automatic error reports when something in the app crashes or fails. This is the only third-party telemetry on the responder side. Along with the browser check described below, Sentry is one of only two third parties your browser contacts on these pages. No behavioural analytics library, tracking cookies or marketing pixels run here, and the anonymous form-performance counters described above are sent directly to ParrotIt.
What an error report includes: the JavaScript error message and stack trace, the page path without its query string, your browser and operating system version, and your IP address (Sentry uses it to estimate where errors happen and discards it after a short retention window, typically around 90 days).
What it is designed to exclude: cookies (we don't set any on this side), the contents of forms you have filled in, decrypted submissions, authentication tokens, and any responder-level history of pages or form sections you visit.
Why we do it: so that a crash on someone's device tells us enough to fix it, without telling us anything else.
How to opt out: error reports only send when an error actually occurs. If you would prefer to send nothing at all, block sentry.io in your browser or an extension like uBlock Origin — the app will continue to work normally.
To stop scripts from harvesting forms or filing junk submissions, ParrotIt asks Cloudflare's Turnstile service to confirm that a form load or submission is coming from a real browser. It usually runs invisibly and asks you nothing.
What it checks: that the request came from a browser. It does not check who you are, and it is not a proof-of-human check — ParrotIt keeps that separate and optional.
What Cloudflare receives: your IP address (unavoidable, because your browser connects to them directly), your browser and operating system version, and signals from the check itself. Not your answers, which are encrypted before they leave your device, and not the identity of the form or organisation you are answering.
Cookies: as ParrotIt uses it, the check sets no cookie and builds no cross-site profile of you. Cloudflare does not use it to advertise to you. Their terms for the service are in the Cloudflare Turnstile Privacy Policy.
If it fails: you may be asked to update your browser or open the link on another device. It is never a dead end — the organisation that sent you the form can always take your answers another way.
If you submit a form published by a specific organisation, that organisation's form privacy policy also matters. ParrotIt provides the product surface; the organisation may still be the relevant controller or service provider for the form you used.
Return to the main ParrotIt privacy docs page.
How ParrotIt uses one-time SMS codes for phone-based device recovery.
Where to send requests and how to route product versus form-specific questions.
The companies that process data for us, and what each one receives.