Skip to content
ProofList

Send professional training certificates in minutes, not evenings.

For independent trainers

Upload your participant list, check one preview, send the batch. Every certificate carries your logo and your name, never ours.

One email when the beta opens. No newsletter, no tracking, no sharing. How we handle your data.

Free during the beta · Participant data stays in the EU · No card

  1. Your listAny CSV. Blanks and typos are flagged first.

  2. One certificate eachThe real PDF, in your brand, checked before anything is sent.

  3. One email eachFrom your name. Replies come to you, not to us.

Eleven designs. Your logo, your colour, your wording.

Every one of these is a fixed layout you fill in, which is why they stay looking professional no matter what you put in them. Pick one, brand it once, and it carries across every course you run.

Classic Formal. Warm off-white stock inside a double gold rule, the name in a Garamond. For accredited and regulated courses.

What ProofList will not do.

Each of these is a decision, and each is part of why the rest works.

Built for the trainer who runs four courses a month, not four hundred.

Pay when you actually train

Buy a pack of credits and use them whenever. They stay valid for two years, and no monthly fee sits waiting for you through a quiet quarter. Subscriptions exist if your volume is steady. They are not the only door in.

Your name on the certificate, not ours

Logo, colours, fonts and sender name from the free tier upward. We never print our brand on a certificate you issue, not on the free tier either. The email that delivers it does carry a credit to us: our logo and a line on the free tier, a plainer one-line mention on paid plans.

Fix a typo without the apology email

Correct one name and reissue in seconds. The old file is voided and the new one goes to that person alone, not to the whole group again.

Expiry dates that bring people back

Certificates carry an expiry date, and participants are reminded before it lapses. A renewal notice doubles as a rebooking prompt.

EU data, plainly

Participant data never leaves the EU.

  • EU hosting

    The app, the database and the certificate files all sit on European infrastructure, in France.

  • EU email delivery

    Certificates reach participants through a European provider, not a US one.

  • Deletion on request

    Find a participant, export what we hold about them, delete it. In from the first day of the beta, not bolted on later.

Subscription, or credits. Your call.

A plan if you issue certificates most months, credits if you run courses in bursts and would rather not pay through a quiet quarter.

Free
€0
20 certificates a month
Plans
From €20 a month
150 certificates a month
Credits
From €20
50 certificates, valid two years

The beta itself is free, within fair use. No card is taken, so nothing can start charging you when it ends. These are the prices we intend to charge at public launch.

Compare plans and credits

Made by a trainer, with the awkward questions answered.

“The certificate problem is not a market I researched. It is an evening I have spent too many times.”

Dimitris Parperis

Trainer for more than fifteen years, across education, healthcare and the corporate world.

ProofList.app is made in Cyprus and operates under EU data protection law.

Will the certificates actually reach people, or land in spam?

This is the failure that makes the whole thing worthless, so it gets treated as the hard problem it is. Certificates go out through a European transactional email provider, not a bulk newsletter tool, with SPF, DKIM and DMARC configured on our sending domain. They are sent from your sender name, and replies go to your address, not ours.

You get a delivery status for every recipient and a resend button for any address that bounced, because no amount of configuration makes deliverability perfect.

Will my CSV work?

If your tool exports a CSV, it works. Eventbrite attendee exports, Zoom or Teams attendance reports, Google Forms responses, or a spreadsheet you keep by hand.

The only columns that must exist are a name and an email address. Everything else is optional. You map your column headings to our fields once, and that mapping is remembered for next time.

Can I put my accreditation number or a course code on it?

Yes. Templates carry placeholders for the participant name, course, date, trainer, hours and expiry date, plus editable text blocks for anything specific to you: a registration number, an accrediting body, a policy reference, CPD hours. What is not in the first release is a free-form drag-and-drop canvas: layouts have fixed zones, which is the reason certificates come out looking professional rather than homemade.

When does the beta actually start?

There is no date, and inventing one would be the easiest way to lose your trust early. The product is being built in the open and the waitlist is in order. You get one email when it is your turn, and nothing before that.

What do my participants actually receive?

An email from your name with their certificate attached as a PDF. One email each, addressed to them, not a group send with everyone’s address visible. If someone loses it, you resend to that person alone from the batch view.

What happens to my participants' personal data?

It stays in the EU. The app, the database and the certificate files are hosted in France, and certificates are delivered through a European provider. It is never sold, shared, or used to market anything to your participants. They never signed up with us and we do not treat them as if they did.

You can find any participant, export everything held about them, and delete them. That is in from the first day of the beta.

Want in on the beta?

We are looking for trainers who issue certificates regularly and are tired of doing it by hand. Beta trainers send real certificates to real participants, free of charge, and decide what gets built next.

No newsletter, no drip campaign. One email when it is your turn.

One email when the beta opens. No newsletter, no tracking, no sharing. How we handle your data.