Last updated 26 August 2026
Privacy notice
Most people who appear in this product never signed up for it. They wrote a recommendation because somebody they worked with asked them to. This page is written for them first.
Who holds your data
PeopleVouch is operated by Fanki Technology, a business registered in Singapore under UEN 53469352X. We decide what is collected and why, which makes us the data controller.
Write to privacy@peoplevouch.com about anything on this page. A person reads that address.
What we collect, and why
We ask for as little as the job needs. There is no field on any form whose only purpose is to learn something about you.
| About whom | What | Why |
|---|---|---|
| The person a page is about | Email address, display name, page address (handle), an optional photo, and the wording and settings they choose for their page. | To sign them in, and to build the page that collects recommendations about them. |
| The person who writes a recommendation | Name, email address, the recommendation itself, an optional job title, an optional description of the working relationship, an optional rating from one to five, and an unchangeable copy of exactly what was submitted. | To publish the recommendation under a name a reader can weigh, to confirm the address belongs to the writer, and to keep the original readable after the subject edits it. |
| A person invited to write one | The email address and name the subject typed, and the message the subject wrote. | To send the invitation and, if it goes unanswered, one reminder three days later. |
| Anybody who uses a public form | The IP address of the connection, kept only as the key of a counter. | To stop one connection flooding a page with submissions or reports. |
| A person who reports a page | The page reported, the reason, what they wrote, and their email address if they gave one. | To act on the report, and to answer them. |
| A paying customer | A Stripe customer reference, a subscription reference, the plan, and the dates it runs between. No card number, and no part of one, ever reaches us. | To know what has been paid for and when service ends. |
What is published, and what is not
A published recommendation shows your name, your words, and the details you chose to add — a job title, how you worked together, a rating. It also shows whether you confirmed your email address, because that is the whole point of the product.
Your email address is never published. It is not on the page, not in the widget that appears on other people’s websites, and not in anything a reader can fetch. The subject of the page can see it in their own inbox, because they need to know who wrote to them.
Nothing is published until the subject approves it, and nothing can be published at all without your consent. That is not a promise about our code alone: the database refuses to put a recommendation on a wall when the consent record is missing.
If the subject edits your words, the original stays available beside the edit. Neither they nor we can remove it, and neither they nor we can add a confirmation mark to a recommendation that never earned one.
Why we are allowed to hold it
| What we do | On what basis | Why that one |
|---|---|---|
| Publishing a recommendation, and the name on it | Consent — GDPR Article 6(1)(a); consent under the PDPA | Given by the tick box on the collection page, and withdrawn at any time from the link in the writer's own email. |
| Running an account, and taking payment for it | Performance of a contract — GDPR Article 6(1)(b) | The account holder asked for the service and agreed to the terms. |
| Confirming an email address, rate limits, the do-not-mail list, and acting on reports | Legitimate interests — GDPR Article 6(1)(f); the legitimate interests exception under the PDPA | Verification is the point of the product. The rest keeps a page from being flooded, keeps mail away from an address that refused it, and lets a person who is not a customer get a page taken down. |
| Keeping records of what was charged | Legal obligation — GDPR Article 6(1)(c) | Accounting and tax records must be kept whatever anybody would prefer. |
Singapore’s Personal Data Protection Act applies to us because we are registered here. The General Data Protection Regulation applies to what we do with the data of people in the European Economic Area and the United Kingdom, because a subject can send an invitation to anybody, anywhere. We do not ask where you are, so we treat both as applying to you.
Who else touches it
These companies process data on our instructions. We do not sell data to anybody, and this list is the whole list.
Google is the only one you can avoid completely. It appears here only if you choose to sign in with Google rather than with an email link, and it learns nothing about you unless you do.
| Who | What they do | What they see |
|---|---|---|
| Supabase | Database, sign-in, and file storage | Everything listed above, held in us-east-1 (Northern Virginia, United States). |
| Resend | Sends the product's email | The recipient address, the subject line and the body of each message, and whether it arrived. |
| Stripe | Takes payment | The paying customer's own billing details, which they give to Stripe directly. We receive a reference, never a card. |
| Vercel | Runs the website, and measures traffic | The requests that build each page, and anonymous page-view counts. See the paragraph on measurement below. |
| An optional way to sign in | Only if you choose it. Google learns that you signed in here, and tells us the email address on the account, your name and your profile picture. Nothing else about you reaches them, and the email link never involves them at all. |
Your data leaves Singapore. The database runs in us-east-1 (Northern Virginia, United States), and the other three companies are based in the United States. Each of them publishes a data processing agreement that includes the European Commission’s standard contractual clauses, and those terms are what the transfer rests on.
We measure traffic with Vercel Analytics. It sets no cookies and does not follow anybody between websites. We tell it two things it must not look at: pages inside a widget on somebody else’s website, which are not ours to measure, and the one-time codes in a confirmation or removal link, which are replaced before the address is ever sent.
How long we keep it
| What | How long |
|---|---|
| A recommendation, and the name and address on it | Until it is deleted. Deletion is immediate and permanent, and the writer can do it themselves. |
| An invitation a subject sent, and the address they sent it to | Kept as their record of who they contacted, and removed on request. Deleting a recommendation does not reach it. |
| The body of an email we sent | Deleted from our records the moment the message is delivered, because it carries a one-time link. |
| An IP address in a rate-limit counter | At most 24 hours. A job deletes it. |
| A one-time link | Seven days. A link that removes a recommendation never expires, because erasure has no deadline. |
| An address that bounced or complained | Kept, so we do not mail it again. It is an address and a reason, nothing else. |
| An abuse report | Kept after it is closed, because a dispute is usually raised after the fact. |
| Billing records | Kept as long as accounting and tax law requires. |
| Counts of what happened (a page was viewed, a recommendation was published) | Kept. They carry no name, address, telephone number, photograph or IP address — a filter removes those before the count is written. |
What you can do about it
If you wrote a recommendation, you do not need an account and you do not need us. Every email we sent you carries a link to your own management page, and that link does not expire.
- Read it. The page shows what you wrote and whether it is published.
- Take it down. It leaves every page and every widget at once, and the subject cannot put it back.
- Delete it. The recommendation goes, and with it your name, the email address on it, the record that you confirmed that address, and the original wording. This cannot be undone.
One thing that does not go, and we would rather say so than let you find out. If the subject invited you by email, the address they typed into that invitation stays in their own records. They had it before you wrote anything, and it is their account of who they contacted rather than part of your recommendation. Ask us at privacy@peoplevouch.com and we will remove that too.
To correct something, write to us. There is no button for this yet: the management page can remove but not edit. Send the correction to privacy@peoplevouch.com from the address you used, and we will make it. We would rather say that plainly than point you at a page that cannot do it.
Use the same address to ask for a copy of what we hold, to ask us to stop using it, or to object to what we are doing with it. If you have lost your link, write from the address you used and we will find the recommendation. We answer within 30 days.
If a page is about you and should not exist — it impersonates you, it says something untrue about you, or it shows something private — you do not need to have written anything. Report the page. We can pause it, suspend it, or take it down, and a person reads every report.
What we never do
- We do not sell personal data, and we do not share it for advertising.
- We do not follow you across other websites, and we set no advertising cookies.
- We do not profile anybody, and no decision about you is made automatically.
- We do not let anybody collect recommendations about a person who has not asked for them. There is no directory here, and no way to rate a stranger.
- We do not read the contents of a widget’s host website.
How it is protected
- Every table in the database refuses access by default, and each account can reach only its own rows. An automated test fails if a table is added without that rule, so it cannot be forgotten quietly.
- The record that says an address was confirmed, and the record that says consent was given, cannot be written by an account holder at all — not through the product, and not around it. The marks you see on a page are copied from those records.
- One-time links are stored as a hash. We cannot read a link back out of the database.
- Payment card details never reach us.
No system is perfect. If a breach puts anybody at real risk, we will tell the people affected and the regulator, as both laws require.
Children
PeopleVouch is for working adults and is not meant for anybody under 16. If you believe a child’s data is here, write to privacy@peoplevouch.com and we will remove it.
Changes, and complaints
When this notice changes in a way that matters, we change the date at the top of the page and tell account holders by email. We do not change what was already agreed for a recommendation that is already published; a new use needs new consent.
Tell us first, at privacy@peoplevouch.com. If we do not put it right, you can complain to the Personal Data Protection Commission in Singapore, or — if you are in the European Economic Area or the United Kingdom — to your own supervisory authority.