Privacy policy
What personal data Certific handles, why, for how long, and what you can do about it.
In short
- Schools use Certific to issue diplomas. Students' data belongs to the school that issued the diploma: the school decides, and Certific handles the data on its behalf.
- Anyone with a diploma's link or QR code can see the holder's name, the course, the school, the dates and whether it is valid. That is what makes it verifiable.
- On this site, nothing optional is stored in your browser until you allow it, and ad personalisation stays off.
- Certific does not sell personal data. It runs on a server in Finland.
- Questions and requests go to privacy@certific.io. You can also complain to the Spanish data protection authority.
1Who is responsible
- Provider
- Jorge Sánchez
- Legal notice
- Tax ID, address and contact details
- Privacy requests
- privacy@certific.io
Certific is the name under which Jorge Sánchez, a sole trader established in Spain, provides this service. "Certific", "we" and "us" refer to that person. The tax ID and the address are in the legal notice.
Certific is the controller, the one who decides why and how data is used, for the data of visitors to this site, of people who book a demo and of the staff accounts that schools open. For students' data in diplomas, the school that issues them is the controller and Certific is its processor: Certific handles that data only on the school's instructions, under the data processing agreement every school accepts.
2Students and people who verify a diploma
When a school issues a diploma with Certific, or imports its students to issue one later, Certific stores on the school's behalf: the student's name; their email address and the school's own reference for them, if the school adds them; the course, the edition and the completion date; the diploma as a PDF and an image; the credential's ID, its status and the history of every correction; and the emails sent with the diploma, with whether each one was sent, delivered or bounced.
Each diploma has its own public page, the address in its QR code. Anyone with the link or the QR code sees the holder's name, the course, the school, the dates, the status, the ID and the diploma itself. That is the point of the service: anyone can check that a diploma is real. If the school revokes a diploma, its page says so and no longer shows the holder's name or the dates.
The school decides what goes on its diplomas and answers requests about them, so to see, correct or delete your data, write to the school that issued your diploma. Its page names the school and, if the school gave one, its contact address. A school can correct or revoke a diploma at once. A school cannot yet delete a diploma itself: when it asks, Certific deletes the diploma, its files and the student's details within 10 working days. If you write to Certific instead, we pass your request to the school and help it answer.
If you choose Add to LinkedIn profile or Share on LinkedIn on a diploma's page, your browser opens LinkedIn with the diploma's details filled in. Certific sends nothing to LinkedIn itself; LinkedIn can read the public page to build its preview, like anyone with the link. Diploma pages never load Google's tags and never ask about cookies.
For the school, Certific counts what happens to each diploma on its page: that the page was opened, and whether the visit came from LinkedIn, the diploma's email, its QR code or elsewhere; that the PDF was downloaded; that Add to LinkedIn profile or Share on LinkedIn was pressed; and that its details were copied, each with the time. It counts per diploma, not per person: no IP address, no browser details, no visitor number and no cookie are kept, and visits from the school's own staff are left out. The school sees these counts with the diploma, and they are deleted with it.
3Schools and their staff
When someone opens an account for a school, we keep their name, their email address and their password, stored only as a hash that cannot be turned back into the password, and records of their sign-ins (time, IP address and browser). For the school we keep its name, website, description, logo, support email, LinkedIn page ID, diploma language, courses and designs, and the legal details it gives for the agreement: its legal name, tax ID and country, and the name and role of the person who accepted it.
When a school asks for the Verified issuer badge, it sends us one document that shows who it is, such as its registration or an invoice in its name; we keep the document, our decision, who took it, when, and the reason when we decline. When a school signs up with a name or website that looks like a well-known university, public body or brand, we keep a note of why and look at it; nothing is blocked. If we suspend a school, we keep the decision, who took it and why. Every change a school makes to a diploma is recorded with who made it and when.
We use this data to provide the service under the terms of service. Where the account holder is the school itself, such as a freelance trainer, the legal basis is the contract (GDPR, article 6.1.b). For the staff of a school that is an organisation, it is our legitimate interest in dealing with the people who act for a school (article 6.1.f, and article 19 of the Spanish data protection act, LOPDGDD). We also use the data to prevent false diplomas and keep the service secure, which is our legitimate interest (article 6.1.f). Account emails, such as the address confirmation and the password reset, serve the same purposes. We keep this data while the account exists. When it is closed, we keep it blocked, out of use, for as long as claims can be brought or the law requires (LOPDGDD, article 32), and then delete it.
4Demo requests
When you book a demo, we keep your name, email address and school, roughly how many diplomas it issues a year, your note if you write one, your time zone and language, the time you chose and where you came from (section 5).
We use it to confirm, move or cancel the demo, to hold the call and to follow up. The legal basis is your request, which comes before a possible contract (article 6.1.b), and our legitimate interest in answering a school's enquiry (article 6.1.f). The call takes place on Google Meet, so Google handles what you share when you join it. The invitation is sent by email and added to our Google calendar.
We keep a demo request for 12 months after our last contact with you, and delete it sooner if you ask.
5Where visitors came from
If you allow Measurement in the cookie settings, a cookie of our own, certific-src, keeps for 90 days the first campaign or website that brought you here: the campaign parameters in the address (utm_source, utm_campaign and the like), a Google Ads click ID or the other site's name, with the page you arrived on and the day. No visitor ID and no IP address.
That cookie is sent to no one. It is stored only if you book a demo or open an account, together with that request or account, so we can tell which campaigns bring schools. The legal basis is your consent (article 6.1.a), which you can withdraw at any time.
One exception: if the address of the demo page itself carries campaign parameters, the booking keeps them even without the cookie, because they arrive with your request. The legal basis is our legitimate interest in knowing which campaigns bring demo requests (article 6.1.f).
6Every visit
Our server records each request it receives, with the IP address and the browser, to keep the service secure and to fix faults. That is our legitimate interest (article 6.1.f). These records are deleted within 14 days.
8Who else handles data
Certific does not sell personal data or share it for advertising, except the conversion signals in section 7, and only if you allow them. These companies handle data for us, each under a contract that binds it to data protection law:
| Company | What for | Where |
|---|---|---|
| Hetzner Online GmbH | Provides the server Certific runs on. | Company in Germany. Server: Finland. |
| Scaleway S.A.S. | Stores Certific's encrypted backups. | Company in France. Backups: France. |
| Resend, Inc. | Sends diploma emails, account emails and demo confirmations. | Company in the United States. Sends from its EU region, in Ireland, and may also process data in the United States. |
| Hostinger International Ltd. | Hosts the mailbox where mail sent to Certific's addresses arrives. | Company in Cyprus. |
| Google Ireland Limited | Google Meet and Google Calendar for demo calls. Google Analytics and Google Ads, only if you allow them. | Company in Ireland. May process data in the United States. |
| Anthropic Ireland, Limited | Answers a school's request to change one of its diploma designs, when the school asks. It receives the design, the school's name and colours and what the school typed, never a student's data. | Company in Ireland. May process data in the United States. |
When a school pays for a plan, it pays Paddle (Paddle.com Market Limited, or Paddle.com Inc. for buyers in the United States and Paddle.com (Canada) Ltd for buyers in Canada), which sells Certific's paid plans: Paddle collects the payment and billing details at checkout, charges the taxes and issues the invoice, as a controller in its own right under its privacy policy. Certific receives from Paddle only what it needs to give the school its plan: the plan, the amounts and dates of each payment, whether it went through, and the buyer's email address and country. Certific never receives card details. The legal basis is the contract with the school (article 6.1.b), and Certific keeps these records like the school's other details (section 3).
We also give data to public authorities when the law obliges us to.
9Data outside the European Union
Certific's server is in Finland and its backups are in France. Resend, Inc., which sends our emails, is a company in the United States: the emails leave from its European region in Ireland, but Resend may also handle them in the United States. That transfer is covered by the standard contractual clauses approved by the European Commission, included in Resend's data processing agreement, and by Resend's certification under the EU-U.S. Data Privacy Framework.
Google may handle data in the United States. Google LLC is certified under the EU-U.S. Data Privacy Framework, and Google's terms include the standard contractual clauses.
When a school asks Certific to change one of its diploma designs, Anthropic answers the request and may process it in the United States, under the standard contractual clauses in Anthropic's data processing addendum. It receives the design, the school's name and colours, the names of the school's own fields and what the school typed; never a student's name, email or diploma.
Paddle, which takes the payment when a school buys a plan, is Paddle.com Market Limited, in the United Kingdom, which the European Commission recognises as protecting personal data adequately; for schools in the United States or Canada it is Paddle's company in that country.
Schools established outside the European Economic Area receive their students' data in their own country, under the standard contractual clauses that the data processing agreement includes.
10How long we keep data
- Students' data: as long as the school keeps the diploma in Certific, including after the school stops paying, so the diploma stays verifiable, and at most until Certific stops offering the service, as the terms of service set out.
- Staff accounts and school details: while the account exists, then blocked for as long as claims can be brought or the law requires.
- Demo requests: 12 months after our last contact, or until you ask us to delete them.
- Where you came from: 90 days in your browser, and once stored with a demo request or an account, as long as that is kept.
- Server records with IP addresses: at most 14 days.
- Backups: made every night and kept for at most 90 days, so data deleted from Certific leaves the backups within that time.
- Google Analytics data: 14 months.
11How we protect it
The site is served over HTTPS only. Each school's data is kept apart from every other school's by rules in the database itself, and those rules are tested. Nightly backups are encrypted before they leave the server, and the server can only be reached with an SSH key. The full list of measures is in the annex to the data processing agreement.
12Your rights
You can ask to see your data (access), correct it (rectification), delete it (erasure), limit how it is used (restriction), object to its use (objection) and receive it in a format you can take elsewhere (portability). Where we rely on your consent, you can withdraw it at any time; that does not affect what was done before.
Write to privacy@certific.io. We answer within one month, as the law requires. For data in a diploma, write to the school that issued it (section 2).
If you think we have not handled your data properly, you can complain to the Spanish data protection authority, the Agencia Española de Protección de Datos, at aepd.es.
13Changes to this policy
When this policy changes, we change the date at the top of the page. If a change affects schools, we tell their account owners by email before it takes effect.