Create formsFREE

ParrotIt

Your form is locked before it leaves your device.

Only you and your chosen recipient can read your private answers.

What you see

Your answers

Full name

Sarah Jenkins

Date of birth

14/03/1982

Mobile number

07700 900123

Email address

sarah.jenkins@gmail.com

Address

12 Fore Street, Penzance, TR18 2PT

You can read it

What ParrotIt sees

Locked data

Full name

a93f..Lq8

Date of birth

N4p9..zT6

Mobile number

7xK2..Pz1

Email address

Gk7m..Rw9

Address

Q8mL..V3A

ParrotIt cannot read it

ParrotIt cannot read your private answers, so we cannot sell them.

Not government
Not big business
Not hackers
Not even ParrotIt

How it works

1. You fill in your form

2. It is encrypted on your device

3. ParrotIt transfers locked data

4. Your chosen recipient unlocks it

locked on your deviceAI model

Your answers never train AI.

They are locked on your device before they reach ParrotIt, so there is nothing readable to learn from. The AI features in ParrotIt work from the kinds of questions forms ask, never from what you answered.

How ParrotIt uses AI

You see answers. We see locked data.

Private by design. Locked end to end.

You stay in control
Encryption end to end
Zero access to your answers
Built for trust

ParrotIt

Private by design. Locked end to end.

ParrotIt is built so no one — not government, not big business, not hackers, not even us — can read the answers in your forms while they travel through ParrotIt or sit on our servers. Only you and the recipient you choose hold the keys.

We store what we cannot open
Locked end to end
No plaintext at rest
No access to keys
No data selling. Ever.

Architecture overview

Your device

You fill in the form

ParrotIt platform

We store and route locked data

a93f...Lq8N4p9...zT67xK2...Pz1Q8mL...V3A...

Recipient

They decrypt and read it

1. Encrypt on device
Private keys never leave your device.

  • Encrypted in transit with modern TLS
  • Submission payload encrypted with AES-256-GCM
  • Submission key wrapped with RSA-OAEP for recipients

Key principles

Encrypted on the device

Data is encrypted on your device before it leaves. ParrotIt never sees plaintext or private keys.

We store what we cannot open

ParrotIt stores and routes encrypted blobs. We are technically unable to decrypt the contents.

Locked end to end

Only the intended recipient can decrypt the data with their private key. No one else can.

No plaintext at rest

We do not store readable answers. A system breach should not expose submitted form content.

No keys. No access.

ParrotIt does not hold decryption keys. Without keys, we cannot decrypt. Period.

Cryptography details

  • Payload encryption
    AES-256-GCM
  • Key wrapping
    RSA-OAEP (SHA-256)
  • Submission key
    Generated per submission
  • Signatures
    Ed25519
  • Transport security
    Modern TLS
Recipient public key
(Published with the form)
↓
Submission key
(Generated on your device)
↓
Encrypted payload
(Stored by ParrotIt)
↓
Wrapped submission key
a93f...N4p9...7xK2...
  • Encrypted form data only.
  • Metadata required to deliver the form.
  • No encryption keys.
  • No plaintext content.
  • No ability to decrypt.

Threat model

External attackers

Even with system access, submission contents remain encrypted.

✓ Mitigated

Insider threat

Staff can route data but cannot read responder answers.

✓ Mitigated

Government requests

We can only hand over what we hold: locked data and delivery records. Answers stay unreadable. We have no keys.

✓ Contents unreadable

Data brokers

There is nothing readable to sell, profile, or quietly monetise.

✓ Mitigated

AI training

Answers are ciphertext by the time they reach us, so there is no plaintext to train a model on. The AI features in ParrotIt work from field types and labels, never from answers.

✓ Mitigated

A lost Key

Bringing answers back takes the Key’s tag, a tap at one of the sender’s own kiosks, and the PIN if it has one. A lost tag can be replaced, and the old one stops working.

✓ Mitigated

Device compromise

If your device is compromised before encryption, risks still exist.

△ User responsibility

Recipient compromise

If the recipient device is compromised after decryption, ParrotIt cannot control that endpoint.

△ Outside ParrotIt control

Data flow summary

  1. Your data enters a form.
  2. Your device encrypts it locally.
  3. ParrotIt transports and stores the encrypted data.
  4. The recipient decrypts it locally using their key.

Standards we build to

  • Designed to support UK GDPR duties
  • Privacy by design
  • Data minimisation
  • Security controls mapped to ISO/IEC 27001
  • Modern cryptography and TLS

The bottom line

You see answers.
We see locked data.

We cannot sell what we cannot read.|Not a promise. A technical reality.