Privacy Policy

1. Who we are and what this covers

Prson is run by Yumankind OÜ, Sepapaja 6, 15551 Tallinn, Estonia (registry code 16232402). We are the controller of the personal data described here, except where section 6 says we act for a requester or an organisation.

This policy covers everything Prson runs: the marketplace at prson.net (asking businesses for quotes and booking them), the Prson app (wallet: keys, identities, verified documents, proofs, signing PDFs, signing in to websites and their notifications; and work as a human agent), app.prson.net (checking proofs and signed PDFs, and asking for early access), human agents at agents.prson.net (people doing paid tasks for requesters), our API and MCP server (including verification requests organisations send to people), and the emails we send and receive.

Questions, requests about your data, or complaints: [email protected]. We answer within one month. We haven't appointed a data protection officer; privacy@ reaches the people responsible.

2. The short version

• We collect what each service needs to work, nothing for advertising. We don't sell data, and our websites use no advertising, analytics or tracking cookies.
• Businesses you ask for quotes see your request and area, not who you are, until you book.
• When you verify a passport or ID card, we check the chip and keep the result and keyed hashes, not your name, date of birth or document number. Matching your face to the chip photo happens on your phone; we receive the match score and one-way codes (hashes), never the photos.
• When you sign a PDF, your signing certificate shows your name as your document's chip gives it. We don't keep the PDFs you sign for yourself.
• AI helps us read and write requests, find businesses and score voice interviews; a person (the requester) decides whom to hire.
• Our own databases and file storage are in the European Union.

3. Data we collect, by service

Asking for a service (marketplace customers)

• Your name, email address and, if you give it, phone number.
• Your request: what you need, your answers to the form, the address or area (we look up its coordinates), dates, and photos or files you attach.
• Messages with us and, through us, with businesses; quotes; your choice, booking and payment status (card details go to Stripe, never to us); reviews you leave.
• If you sign in: your account, saved addresses and phone, and your list of requests.

You can also ask us on social networks, and we keep what reaches us from there:

• Direct messages to Prson's accounts (Instagram, Facebook and the other networks we're on): your messages, your name, username and account id on that network, and the email address you give us. Our AI assistant answers them (a person can step in); your request is then handled as above, with the confirmation sent by email.
• Comments under our posts that ask for a service: the comment, your name, username and account id. We answer in public only with a short pointer, never with your details, and carry on in a private message.
• Ad lead forms (Facebook and Instagram instant forms): the answers you submit (typically your name, email, phone, city and what you need), the consent text the form showed you, and which campaign, ad set, ad and form it came from. We email you to confirm before any business is asked.

Businesses

• Businesses that sign up: business name, contact details, services, area, plan and its payments.
• Businesses we find to ask for a quote: public business details (name, business email, phone, website, location, Google rating) from web search and maps and from the business's own website, used to send that request. Every such email lets them unsubscribe, and we stop at once.
• Quotes, replies and messages about each request.

Referrals

• Who referred whom (a referral link, kept in your browser for up to 30 days, or an email copying [email protected]), earnings, cashback, withdrawal requests and what we need to pay you and meet tax rules.

The Prson app: wallet and identity

• Public keys of your wallet, identities and phone (never the private keys or the recovery phrase).
• Whether your phone is genuine: the device attestation from Apple or Google (the result and certificates, not your files or messages).
• If you choose: a security email, and a backup of your recovery phrase encrypted on your phone with your passkey. We only hold the encrypted form and can't read it. Passkeys: their public keys only.
• Profile photos you add to an identity. They are stored with an unguessable address, and anyone you give that address to (or who receives it from someone you shared it with) can see the photo.
• Identity documents. When you verify a passport or ID card, the app reads its chip and sends us the chip's security file (SOD), data group 1 (the machine-readable zone: name, document number, nationality, date of birth, sex, expiry), the chip's public key (DG14 or DG15, if present) and its answer to our challenge. We use them only to check the document is genuine, unaltered and the real chip, and then discard them. We keep:
  • the document kind and code, issuing country and expiry date, and the names of the certificates that signed it (the document signer and the country's signing authority);
  • the verification level and our signed statement of the result. The statement holds salted one-way codes (digests) of the document's details; the salts stay in your wallet, so we can't read the details back from it;
  • a one-way code (hash) of the chip photo, taken from the security file, so a face match can be tied to this document;
  • two keyed hashes (made with a secret key only we hold): one of the document's country, kind and number, and one of your nationality, date of birth and names (the person key). They let us make sure one document and one person belong to only one wallet at a time, without keeping the details. If a document or person is already in use in another wallet, we record the conflict and ask you to contact support; if you claim a document another wallet holds, we keep the claim and its steps.
  Websites you sign in to with Prson get a different identifier each, derived from the person key, so they can't link you across each other.
• Face matching. To check the document is yours, the app compares a live selfie with the photo on the chip, on your phone, and checks that a live person is in front of the camera (liveness). The selfie, the chip photo and any face measurements stay on your phone. The app sends us, signed by your phone: the match score, the threshold it had to reach, the liveness method and whether it passed, one-way codes (hashes) of the selfie and of the chip photo, and the app version. We keep these as the evidence for your verification level. This is biometric processing: it happens only when you start it, on the basis of your explicit consent (GDPR Art. 9(2)(a)). You can withdraw consent at any time: write to [email protected] and we delete the stored result, or delete all your data in the app's Settings. Withdrawing doesn't affect checks already made.
• Verified details (email address, phone number, postal address, website domain, and details read from a verified document such as your names and date of birth). We use the value to check it (for example to send a code) and don't keep it, except a postal address you verify by letter: we keep your name and the address as printed on the letter, and a one-way code of the letter's code, until you enter the code or for 60 days. We keep, for each detail: a keyed hash made with a secret key only we hold (so we can recognise the same value again and keep one value to one identity), a salted commitment that we sign and you can share (the salt stays in your wallet, so the commitment doesn't reveal the value), when it was verified and when it lapses, and a few minimised facts (an email's domain, a phone's country code, a document's kind, country, expiry and last four characters).
• Proofs and challenges. Photos, videos and answers you capture to prove something, their time and, if asked for, location, and the packages you share by link.
• Pro and credits. Your credit balance, what you spent them on, and your Pro subscription status. App Store and Google Play purchases are handled by Apple and Google; we receive the purchase receipt to confirm them.

Signing PDFs

• To sign PDFs, your wallet gets a signing certificate from Prson. It names you (your given names and surname as your document's chip gives them) and shows your verification level (5 or 6). The certificate stays on your phone, and the key that signs only exists there. Anyone who receives a PDF you signed can see your name in it.
• We keep a record of each certificate without your name: its serial number, fingerprint, the identity and document it was issued for, the level, its validity, and whether it was revoked. We need this to publish revocations.
• When you sign, your phone sends us the PDF so we can prepare it and add a timestamp (RFC 3161, from Prson's own timestamping service). We keep the prepared PDF for 15 minutes at most. We don't keep a PDF you sign for yourself: it goes back to your phone.
• If an organisation asks you to sign a PDF, we keep the PDF it uploaded and the signed copy (see "Verifications for organisations" below).
• If you choose to add where you signed, the town and country go into the PDF.

These are advanced electronic signatures, not qualified ones (eIDAS Regulation). They show who signed and that the PDF hasn't changed since. Only a qualified signature has the same legal effect as a handwritten one everywhere in the EU.

Sign in with Prson and website notifications

• We count sign-ins per website, to apply its free allowance, not per person. We don't keep a list of the websites you sign in to, except the ones you allow to send you notifications.
• If you tick "Let this site send you notifications" when you sign in, we keep, for your wallet, that website's domain, a random code the website uses to reach you (different for each website), and whether you muted it or turned it off.
• Notifications are kept in your wallet's inbox for 30 days. Separately, we record when each one was sent and by which app (not its text), to apply limits.

Verifications for organisations

• An organisation (or an AI agent working for one) can ask people, through our API, to prove things: a fact such as "over 18", a verified detail, a selfie, a photo or video, a document, or a signature on a PDF.
• We keep the request: who asked, what for, its title and notes, the requirements, its price and when it expires (at most 7 days after it is sent). We keep each answer: what you chose to share, the photos or videos you took for it, our check of the answer and, for a signature, the PDF the organisation uploaded and the signed PDF.
• The organisation sees you only by an identifier made for that organisation alone, plus what you choose to share. It can't link you across organisations.

Early access (app.prson.net)

• If you ask for early access: your email address, where you asked from, and when. We use it only to send you an invite.

Human agents (agents.prson.net and the app)

• Your agent profile: display name, headline, languages, skills, licences you declare, the area you work in (stored rounded to about 1 km) and your verification level.
• Task offers, the tasks you take, and your earnings and payouts (paid through Stripe, which verifies payout accounts itself; we keep the account's country and status).
• Proof you take for a task: photos and videos, the time, and your phone's location while capturing (a track signed by your phone; we keep the best position, its accuracy and the distance to the task). The exact task address is shown to you only once you hold the task.
• Video applications: when a task asks for one, the short video you record.
• Voice interviews: when a task asks for one, the app or website speaks the questions (text-to-speech), records your spoken answers, turns them into text and has AI summarise and score them against the requester's questions.
• For tasks with stops (for example visiting businesses): what you report at each stop. Contact details of people you meet are recorded only if they agree, and you confirm their agreement in the app.
• Reports you make about a task.

Requesters (companies and AI agents using the API)

• Account and organisation details, API keys (stored as hashes), connected apps (OAuth), tasks, balances, top-ups, webhooks, and decisions you take on agents' work.

Waiting list and reports

• If you join a waiting list: your email address, which list (customer, business, agent or requester), your language, your country if you give it, and where you signed up. We email you to confirm before you're on the list.
• If you report content: what you report, your reasons and, if you give it, your email.

When you visit our websites

• Technical data needed to run and protect the service: IP address, browser, pages requested and errors, in short-lived logs, used for security and rate limits (we store a hash of the IP address, not the address, where we keep it longer, for example on a report).
• On app.prson.net, if a page fails, your browser sends an error report: the error, the time, your browser's name and version, and the page's address cut to its first part (never the rest of the link, which can hold a share code). It holds no account details.
• What we keep in your browser, and which site loads fonts from Google: see section 9.

4. Why we use it (purposes and legal bases)

• To provide what you asked for (performing our contract with you, GDPR Art. 6(1)(b)): handling your request, asking businesses, quotes, bookings and payments; running the wallet, verifying documents and details, signing certificates and PDFs, proofs, and answering organisations' requests you choose to answer; Pro and credits; offering and paying tasks; the referral programme.
• Legitimate interests (Art. 6(1)(f)): keeping accounts and payments safe (fraud and abuse prevention, rate limits, device attestation, one person one wallet, publishing revoked certificates); fixing errors on our websites; contacting businesses found in public sources about a specific customer request, with an easy opt-out; checking tasks against our content policy; improving the service.
• Consent (Art. 6(1)(a), and Art. 9(2)(a) for face matching): face matching, optional photos and files, contact details recorded at a stop, the security email, notifications from websites you allow, the waiting list and early access (to email you when Prson opens for you). You can withdraw consent at any time.
• Legal obligations (Art. 6(1)(c)): accounting and tax records, handling reports of illegal content, and answering lawful requests from authorities.

5. AI and automated decisions

We use AI to understand requests and messages, write them up for businesses, translate, find businesses that might do the job, check tasks against our content policy, and, in voice interviews, to transcribe answers and summarise and score them.

No decision with legal or similarly significant effects on you is made by automated means alone (GDPR Art. 22). An interview score is advice for the requester, who decides whom to hire; you can ask us for your interview summary and score at [email protected], give your point of view, and contest the decision with us (see the agent terms). Tasks our screening holds are released or taken down by a person.

6. Who sees your data

Businesses: before you book, the businesses we ask see a write-up of your request and your town, without your name or contact details. After you pay the booking fee, the business you chose gets your name, email, phone and address, and you get theirs. If that business cancels, the replacement you book gets them too.

Requesters see, for their own tasks: agents' display names and verification levels (not legal names or documents), proof with its time and location, reports from stops, video applications, and interview recordings, transcripts, summaries and scores. For that content the requester decides why it is collected, so the requester is a controller of it, and we process it for them. Their use is governed by their own privacy notice and our requester terms.

Websites you sign in to with Prson get only what you approve in the app. A website you allow to send you notifications gets a random code for you that works only for that website, never your contact details.

Organisations that ask you to verify something or sign a PDF get only what you choose to share in the app, under an identifier made for that organisation. A PDF you sign for them carries your name in its certificate. For the answers it receives, the organisation decides why it asks and is responsible for its own use of them, under its own privacy notice.

Anyone you give a signed PDF or a proof link to can see what it contains, and can check it with Prson's published certificates and revocation list.

Service providers who process data for us under contract:

Social networks (Meta for Instagram and Facebook, and the others we're on) are where those messages, comments and lead forms happen: they process them under their own privacy policies, and our replies go through them.

We may also disclose data when the law requires it, or to protect the rights and safety of people using Prson.

7. Transfers outside the EU

Some providers above (Google, OpenAI, Stripe, Apple, fal.ai, Zernio, Cloudflare for email and the network edge) may process data in the United States or elsewhere. Where they do, the transfer relies on the EU–US Data Privacy Framework where the provider is certified, or the European Commission's Standard Contractual Clauses, with additional safeguards where needed.

8. How long we keep it

We delete or anonymise data on these schedules automatically (a daily job), or sooner when you delete it or your account.

When you delete your account (on the website in Settings, or in the app), we delete your profile, wallet, identities, documents (with any face-match result), verified details, proofs and shared packages, photos, addresses, push tokens, passkeys, agent profile, screening videos and interviews, and the sign-in account, and we revoke your signing certificates. Your marketplace requests lose your contact details, text, answers, location, messages and files. What we must keep stays without your name: payment and accounting records (7 years), and proof already delivered to a requester (it is their record). You can't delete an account while a task you took is in progress, a booking you paid for is under way, or a referral withdrawal is waiting to be paid.

9. Cookies and browser storage

Our websites only store what they need to work, so they don't ask for consent. There are no advertising, analytics or tracking cookies. On prson.net and agents.prson.net, fonts and icons are served from our own site. app.prson.net loads its fonts from Google Fonts, so your browser contacts Google when you open it (section 6).

10. Your rights

You can ask for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable format. Delete your account in Settings on the website or in the app; for anything else, including a copy of your data, write to [email protected] from the email address on your account. Where we rely on consent, you can withdraw it at any time.

You can also complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or the authority where you live.

11. Security

Data is encrypted in transit and at rest. Wallet keys are made and kept on your phone, in its secure hardware where available. Access to our systems is limited and logged. If a breach puts you at risk, we tell you and the authority as the law requires.

12. Age

Prson is for people aged 18 and over. We don't knowingly collect children's data; if you think we have, write to us and we'll delete it.

13. Changes

We update this page when what we do changes, and tell you in advance by email or in the app when a change matters.

14. Contact

[email protected] · Yumankind OÜ, Sepapaja 6, 15551 Tallinn, Estonia · Registry code 16232402