BiblioViva Documentation
Compliance

Personal data protection

This page covers Regulation (EU) 2016/679 (GDPR) and the Italian Personal Data Protection Code (D.Lgs. 196/2003, a legislative decree), for the processing of the library patrons' data with BiblioViva. It is written for the head teacher, the DSGA and the DPO, and it contains two ready texts to copy: one for the record of processing activities and one for the information notice.

What the rule asks

The school is the controller of the personal data of its students and teachers (GDPR, art. 4 and 24), represented by the head teacher. Running the school library is one of the school's tasks: the legal basis of the processing is the task carried out in the public interest (art. 6, paragraph 1, point e), and not the consent of the families. The rule does not say expressly whether the patron's photo falls within the same task: the school evaluates it with the DPO, and BiblioViva makes it possible not to use photos.

Among other things, the school must:

When an outside company processes data on the school's behalf, it is a processor and the school appoints it with a written act (art. 28).

The Italian data protection authority (Garante per la protezione dei dati personali) has published for schools the guide «La scuola a prova di privacy» («The school, privacy-proof»), which recalls the same principles: only the indispensable data, care with images of minors, no publication of personal data.

The Personal Data Protection Code

In Italy the GDPR applies together with the Personal Data Protection Code (D.Lgs. 196/2003), which D.Lgs. 101/2018 amended to bring it into line with the regulation. Two articles of the Code are useful to the library.

The patrons' photos

A patron's photo is personal data (GDPR, art. 4, point 1). For schools the Garante recommends care with images of minors, as in the guide already cited. The GDPR treats a photograph as biometric data, and therefore as a special category of data (art. 9), only when it is processed by technical means that allow the unique identification of a person (art. 4, point 14, and recital 51); BiblioViva does no face recognition.

Law 633/1941 on copyright (Legge 633/1941) also regulates the right to one's image: the portrait of a person may not be displayed, reproduced or put on the market without their consent (art. 96), except in the cases of art. 97, among them reproduction justified by scientific, educational or cultural purposes. The two rules concern the publication and dissemination of a portrait, which BiblioViva does not do. The rule does not say expressly whether printing the photo on the patron's card falls within the reproduction of art. 96: the school evaluates it with the DPO, together with the legal basis indicated above.

What BiblioViva does

Data kept

A patron's record (a student or a teacher) contains:

There is no date of birth, tax code, home address or phone number. Each loan records the patron, the copy, the dates and, as a snapshot of the day of the loan, the patron type, the class and the school year. A wish may carry the name of whoever expressed it; removing the patron deletes the name and the wish stays.

The patrons' photos and the books' covers can each be switched off on their own; switching them off does not delete the files already saved. The guide Switch off photos or covers describes the procedure. For the photo census, pictures of a whole class can be uploaded: they stay until the classes are upgraded (see "How long").

The staff accounts are personal data of the people who work in the library: user name, display name, password hash, roles and date of the last login. As a rule the accounts are shared, one per role; whoever wants to know who did what creates one account per person (Manage the staff accounts).

BiblioViva has no public catalogue and no accounts for students or families: no library patron ever enters the software.

Patrons' photos

Where they are

The data are on the school's computer where BiblioViva is installed: the database, the photos and the backups are folders of that computer. BiblioViva does not use a cloud service and does not send the patrons' data to the project or to anyone else. The software contains no analytics or usage reporting, and the pages that the browser loads do not call external services: the fonts, the icons and the images are served by the school's computer.

When the school installs BiblioViva by itself, on its own computer, no company processes the data on its behalf, and so there is no processor to appoint under art. 28. An appointment would be needed if the school entrusted the installation and the management of the data to a supplier, or if someone offered BiblioViva as a hosted service on their own computers: in that case whoever hosts it would become a processor.

How long

Who sees them

An account of the staff is needed to enter. Each account has one or more roles, and each role is a set of permissions (loans, patrons, catalogue, reports, imports, anonymization, administration): an account does only what its permissions allow. Photos and covers open only with an account. Removing a patron requires the anonymization permission; exporting a person's data, downloading the backups and managing the accounts are for the administrator. Whoever lends the books sees the name and the class of whoever takes them, because the loan needs it.

Passwords are kept as hashes and not in clear, and failed login attempts are limited. The security measures are described in the page Security.

What leaves the school

Logs

BiblioViva writes its technical logs to the standard output, with no log files of its own, and no names, photos or card numbers appear in them. The Audit log lists who did what: it contains the account name, the type of operation, what was touched and its internal number; the fields that carry names, emails, notes, photos or card numbers are discarded before the row is written. The rows can be consulted from Audit log.

What the school does

Text for the record of processing activities

The following text is copied into the school's record of processing activities and completed. It follows the fields of art. 30, paragraph 1, of the GDPR. The parts in square brackets are to be filled in or chosen.

Processing: management of the school library (patron records, catalogue, loans and returns), with the BiblioViva software.

  • Controller: [name of the school], represented by the head teacher [name]; contact: [mail or PEC address]. Data protection officer: [name and contact].
  • Purposes: management of the loan of books and of the other materials of the school library; printing of cards and overdue reminders; statistics on the use of the library. Legal basis: task carried out in the public interest by the school (art. 6, paragraph 1, point e, GDPR). [Legal basis chosen for the patron's photo, or: photos are not used.]
  • Categories of data subjects: students; teachers; staff who use the library with an account of their own.
  • Categories of data: first name and last name, patron type, class and year, card number, registration number, email address assigned by the school, photo [if switched on], internal notes; loan history with the class of the day of the loan. For the staff: user name, display name, roles, date of the last login, audit log. No special categories of data and no data relating to criminal convictions are processed.
  • Recipients: the authorized school staff, with accounts that limit access to the data necessary for their role. No external recipient. [Any suppliers who manage the computer or the backups, to be appointed processors under art. 28.]
  • Transfers to third countries: no patron data is transferred. [If the school uses Tailscale: the connection between the devices goes through a private network provided by Tailscale Inc.; the traffic is encrypted end to end and the provider processes the data of the school's account and of the connected devices; basis for the transfer: [to be checked with the DPO]. If the school uses the local network: no external service takes part in the connection.] [If the external copy is on: destination, operator and location.] The search for the books' data and covers sends to external services only the ISBN, the title or the author of the book.
  • Storage periods: the patron's data and loans stay for as long as the patron is at the school. At removal (also with the end-of-year class upgrade) first name, last name, email, registration number, notes, card number and photo are deleted at once; what stays, without identifying data, is the patron type, the class and the loans for the statistics. Backups are kept for [30] days. The audit log is kept for [24] months.
  • Security measures: access reserved to staff with personal or per-role accounts, protected by a password kept as a hash; separate permissions for loans, patrons, catalogue, reports and administration; data kept on the school's computer [located in: place]; nightly backup [kept in: place and custody arrangements]; audit log; software updates [at the interval: ...]. The backups are not encrypted by the software: [measure adopted by the school].

Text for the information notice

The following paragraph is added to the information notice that the school gives to families and staff (art. 13 GDPR), and completed.

School library. To allow the loan of the books and of the other materials of the school library, the school records in a library management software the first name and last name, the class and the card number of students and teachers[, the email address assigned by the school][, the registration number][, the photo for the card] and the loan history. The processing falls within the school's task carried out in the public interest (art. 6, paragraph 1, point e, GDPR). The data are accessible only to authorized staff, stay on the school's computer and are not communicated to other parties[, except: ...]. When the student or the teacher leaves the school, first name, last name and the other identifying data are deleted; what stays, without identifying data, is the class and the loans for the statistics. Backups are kept for [30] days. To exercise the rights provided by articles 15 to 22 of the GDPR (access, rectification, erasure and others), contact [school contact] or the data protection officer, [name and contact].

References

A–Z index