Forms are really just people, asking people, for the truth about themselves.

The same questions, over and over

Think of a person, call her anyone. This week she signs up to a new service, registers with a clinic, applies for support, books an appointment. Each one hands her a form. Each form asks the same things: her name, her address, her date of birth, the details she has typed a hundred times before.

Every time, she copies herself out by hand. Every time, the organisation receives slightly messy, slightly different data. And every time, another copy of her personal details settles into another database she'll never see again.

There has never been a place that is simply hers, one that holds who she is and lets her hand it over on her own terms.

So she fills it in once, into a vault that is hers

The first time she uses ParrotIt, she enters her details into a private vault. Her name, her address, her date of birth. Each one a detail she'll never have to type again.

The vault lives on her own device, and it's locked with a key only she holds. Here's the part that matters: the ParrotIt servers never see what's inside it. They only ever hold a scrambled, unreadable version. Even the people who built ParrotIt can't read her data.

Now a form is just a quick yes

Next time an organisation needs her details, she doesn't start from a blank page. The organisation, the one asking, has described what it needs, and ParrotIt has quietly matched those questions to the details already in her vault. "Date of birth", "DOB", "birth date" all mean the same thing, so they all fill from the same place.

She does not retype. She reviews. And crucially, she chooses, field by field, what this particular form is allowed to see. Her vault proposes; she decides. Nothing leaves without her yes.

And there's a record both sides can trust

Once she's submitted, the exchange leaves a trail neither side can quietly rewrite. Two things can happen to a submission, and they're deliberately different:

Every step is signed and stamped with the time it happened, and she can see the whole history of her own submission. The honesty is not a promise. It is built into how the thing works.

Sometimes the help needs more than one organisation

Here's where it becomes properly human. Imagine she's reaching out for support, and the organisation she contacts needs to bring in a partner, a second service that's part of helping her. Today that means telling her story all over again, or an organisation quietly forwarding her details with no record.

ParrotIt makes that sharing declared, consented and visible. Before she submits, she sees exactly which organisations will receive her answers, by name. Nothing is shared after the fact, and there are no surprises. And the two organisations have to have agreed to it openly first, in a handshake either of them can walk back at any time.

That agreement has a direction and this is the one way, two way distinction:

And the people asking are nudged to ask kindly

There is a person on the other side too, whoever built the form. ParrotIt helps them build a form that's light to fill, not a wall of questions. As they add fields, a simple ease score ring moves: higher means lighter. A pale arc shows how much will autofill from people's vaults, the bits nobody has to retype.

Tap the ring and it explains, in plain words, what's making the form heavy and how to lift it, usually "reuse a standard field instead of inventing a new one." It's guidance, never a gate. The result: shorter forms, asked with more care.

Every honest exchange makes the next one easier

None of this is a single clever feature. It's a loop. The more people fill forms this way, the better the system gets at understanding what forms are really asking, without ever seeing what anyone actually answered. Better matching means fewer questions, fewer questions means lighter forms, lighter forms mean more people finish, and more finished forms bring more organisations in.