Data processing agreement
How Certific handles students' data on behalf of each school, as article 28 of the GDPR requires.
1Parties and acceptance
The controller: the school, training provider or other organisation that creates its school in Certific (the school). Before it can issue diplomas, the school gives its legal name, tax ID and country, and the name and role of the person who accepts this agreement on its behalf; Certific records them with the acceptance.
The processor: Jorge Sánchez, a sole trader established in Spain who provides the service under the name Certific (Certific), reachable at privacy@certific.io. The tax ID and the address are in the legal notice.
The school accepts this agreement when it creates its school in Certific, and again when the agreement changes. Certific records each acceptance with its date and the version accepted, which is the date at the top of this page. The agreement forms part of the terms of service; where the two differ on personal data, this agreement prevails, except for the limits of liability in the terms, which also apply to it.
2Subject matter and duration
Certific processes personal data for the school to provide the service described in the terms of service: issuing, publishing, emailing, correcting and revoking the school's diplomas.
The agreement lasts as long as Certific holds personal data for the school. That includes the time after the school stops paying, while its issued diplomas stay verifiable, and ends at the latest when Certific stops offering the service under the terms of service.
3Nature and purpose
Certific stores the data the school enters or imports, turns it into diplomas (a PDF and an image) with a QR code and a permanent ID, publishes each issued diploma on a public page, emails it when the school asks, keeps the history of corrections, records whether each email was delivered and counts what happens on each diploma's page (opened, downloaded, added to or shared on LinkedIn, details copied), per diploma and never per person, so the school can see whether its diplomas reach students. The purpose is to let the school issue diplomas that anyone can verify.
On the public page of an issued diploma, anyone with its link or QR code can see the holder's name, the course, the school, the dates, the status, the ID and the diploma. By issuing a diploma, the school instructs Certific to publish it. When the school revokes a diploma, its page stops showing the holder's name and the dates.
4Personal data and data subjects
- Data subjects
- The people the school imports into Certific or issues a diploma to.
- Personal data
- Name; email address and the school's own reference, if the school adds them; course, edition and completion date; the diploma as a PDF and an image; the credential's ID, its status and history of corrections; email delivery events (sent, delivered, bounced); counts of what happened on the diploma's page (opened and from where, downloaded, LinkedIn buttons pressed, details copied) with their times, without anything about the visitor.
- Special categories
- None. The school must not put health or other special category data in a diploma.
5Certific's obligations
- Process the data only on the school's documented instructions: this agreement, the terms of service and what the school does in Certific. If the law requires Certific to process it otherwise, Certific tells the school first, unless the law forbids that. If Certific believes an instruction breaks data protection law, it tells the school immediately.
- Make sure everyone at Certific who can reach the data has committed to confidentiality.
- Take the security measures article 32 of the GDPR requires, listed in the annex (section 13).
- Help the school, as far as it can, to answer data subjects' requests (section 9), to keep the data secure, and with data protection impact assessments and prior consultations with the authority.
- Tell the school about any personal data breach without undue delay and within 48 hours at the latest (section 10).
- Delete or return the data when the service ends (section 11).
- Make available the information needed to show that it meets these obligations, and allow audits (section 12).
6The school's obligations
- Have a lawful basis for giving Certific its students' data, for publishing their diplomas and for emailing them.
- Tell its students how their data is used, including that each issued diploma has a public page.
- Give Certific only the data the service needs, and no health or other special category data.
- Give its instructions through Certific or in writing, and keep its students' data accurate, correcting or revoking a diploma as soon as it learns that it is wrong.
The terms of service (section 4) list the rest of what the school is responsible for.
7Sub-processors
The school authorises Certific to use the sub-processors below. Certific binds each of them by contract to the same data protection obligations as this agreement, and remains fully liable to the school for them.
| 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. |
Certific tells the school by email at least 14 days before adding or replacing a sub-processor. Within that time the school can object on reasonable data protection grounds. If the objection cannot be resolved, the school may close its account before the change takes effect.
When the school asks Certific to change one of its diploma designs, Certific sends Anthropic Ireland, Limited the design, the school's name and colours, the names of the school's own fields and what the school typed, to answer the request. No student's data is sent, so Anthropic is not a sub-processor of the school's data. The privacy policy says where Anthropic may process the request.
8Transfers outside the European Union
The data is stored on a server in Finland, and its backups are kept in France. Resend, Inc. sends the diploma emails from its European region in Ireland, but it is a company in the United States and may also process them there. 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.
When a school established outside the European Economic Area accesses or receives its students' data, that is a transfer to the school's country. Where that country has no adequacy decision, the standard contractual clauses of Decision (EU) 2021/914, module four (processor to controller), apply between Certific and the school and form part of this agreement.
Certific makes no other transfer of the school's data outside the European Economic Area apart from those described above.
9Requests from data subjects
The school answers its students' requests. In Certific it can see and correct a student's data and revoke a diploma at once; a revoked diploma's page no longer shows the holder's name or the dates.
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 of the request. If a student writes to Certific, Certific passes the request to the school without undue delay and does not answer it itself unless the school asks it to.
10Personal data breaches
If Certific becomes aware of a breach affecting the school's data, it tells the school without undue delay, and in any case within 48 hours of becoming aware of it, by email to the account owner, with what it knows: what happened, the kinds of data and roughly how many people are affected, the likely consequences and the measures taken or proposed. It adds what it learns later, and helps the school notify the authority and the people affected where that is needed.
11When the service ends
When the school closes its account, it chooses what happens to its students' data: either Certific keeps the issued diplomas verifiable, under this agreement, or Certific returns the data to the school and then deletes it. What remains in the backups disappears within 90 days, as they expire. If a backup is restored, Certific deletes again what had been deleted.
A school that keeps its diplomas verifiable after closing its account remains the controller and keeps a working contact address with Certific. If it no longer exists, or does not answer two messages sent 30 days apart, Certific may stop publishing its diplomas and delete the data 90 days later.
If Certific stops offering the service, it gives the school the notice set out in the terms of service; until then the school can download its data, and afterwards Certific deletes it.
Certific keeps only what the law requires it to keep, and only for as long as it requires.
12Information and audits
Certific gives the school the information needed to show that it meets this agreement. It allows audits, including inspections, by the school or by an auditor bound to confidentiality whom the school appoints, with reasonable notice, at the school's cost and no more than once a year, unless a breach or a data protection authority makes another one necessary. An audit is done first through documents and written answers, then remotely if those are not enough, and never gives access to other schools' data.
13Annex: security measures
- All traffic to and from Certific is encrypted with HTTPS.
- Each school's data is kept apart from every other school's by row-level security in the database, checked by automated tests.
- Every school account is opened from a confirmed email address, and a school on the free plan sends a limited number of diploma emails a day.
- Every correction to a diploma is recorded with who made it and when, and earlier versions are kept.
- Staff passwords are stored only as hashes.
- Backups are made every night, encrypted before they leave the server and kept outside it, in France, for at most 90 days.
- The server can only be reached with an SSH key, never with a password.
- Server logs that include IP addresses are deleted within 14 days.