Many clients ask me what are our GDPR rules with coreBOS. This question makes me smile and answer with another question: what does your GDPR compliance documentation say that your coreBOS must do? The general idea is that it isn't the software itself that makes your company compliant, it is how you decide to configure that software. With that said, let's see what some of the coreBOS users are doing.
GDPR compliance is all about responsibility, it is called proactive liability. This concept comes to say that you must know what is happening in your company, what can be done and what can't be done and be able to prove that the correct procedures are being applied in each case. In order to accomplish this, you must have a written document that states these procedures and limitations. Once you have that you will be able to adapt your software, be it coreBOS or any other, to the requirements of this compliance document. This document will also guide to other actions that may have nothing to do with software like putting a lock on a cabinet drawer.
The first procedure that most coreBOS users implement is the proof of legal base to work with a client. You must be able to prove at any given moment that you have explicit consent from your clients to have their data and work with them. The easy way to do this in coreBOS is to add a few custom fields on the Documents module to indicate the type of consent and when it was given and then upload the specific contract or file that establishes the relation.
Some of our users prefer to save this relation separately, on another module, so we created a new module called Personal Consent which has a relation field to Accounts and Contacts, the type of relation picklist field, the from and to date of the relationship and then you can add any documents to the record to prove the consent. We even have some clients that create this record directly from their website using the web server API to record the cookies and website information consent.
A few values of types of relationships can be: Contractual, Vital interest, Legal obligation, Public interest, Legal interest on behalf of third party,... but these really depend on your business sector and needs.
The next set of actions to control are the requests to Access/Portability, Rectification, Erasure, and Objection. The general idea here is to create a ticket which records the fact that a client has requested this right and document all the steps taken in the ticket. This serves as a register of what has happened to the client's request and data so we have traceability. It also serves as a support for establishing procedures as we can add workflows to control time spans and/or overdue requests or send emails as actions are taken on the request. As above, you should add some picklist to separate these GDPR requests from other normal tickets and you can also create or add another module only for this type of request.
With that out of the way let's see some of the configurations we can do for each of the requests.
When a client asks to see all the information you have about them, you must, once again go to your GDPR compliance documentation and see exactly what that means. We can do something simple like showing them the relation of fields we have and their value, this can be done exporting the Account/Contact record in CSV so they can achieve the portability and send the information somewhere else, or you can go to the detail view and print the information to a PDF, you could even go to the length of creating a nicely formatted PDF using GenDoc. But, in reality, this is not all the information we have of them, we also have their invoices with the products they bought and how many times, their tickets, maybe we have some high-level sensible fields like sexual preferences or some illness, maybe you have a coreBOS registering loans and payments, or medical interventions, ... the possibilities are endless and exactly what and how you should give them all this information must be defined and then adapt your coreBOS to the requirements of your compliance documentation.
This is easy; create the ticket, indicate the changes to be made and edit the record accordingly. You should have ModTracket active to record the changes. Inform the client.
This one is rather easy also. If your company sells, sorry, I mean shares, information with other companies you must inform your clients and give them the right to establish with whom you can do that. The idea here is to associate some checkbox to each portion of information and mark the checkbox to permit or not sending the information depending on the demands of the client. Then you can create GenDoc outputs and different reports depending on the values of these checkboxes.
This can be easily accomplished using the Archive record pattern. Additionally, you can add some logic to control the actual elimination of the record like adding a date field which automatically gets filled in when the record is assigned to the archive user, then you could create a scheduled workflow to actually eliminate the record when the legal time span has expired or simply create a scheduled report that lists all the records due to be deleted a certain week and have that sent out weekly to the person in charge of this task.
Note that as with all the other options we can adapt coreBOS to your needs (in fact that is what this is all about), for example we have a client that uses the archive pattern and wanted any user in the system to be able to search for accounts by accountname no matter what their personal permission is, so we added a rule to accomplish this particular task for them. You could also use RAC (to some extent) for something like this.
Another requirement of the GDPR is to keep a detailed record of security breaches. I recommend using the projects module for this. As with tickets and documents, add a picklist to categorize the breach project from the others and then use the tasks, milestones, and workflows to take and document all the necessary steps and their result.
We have some clients that use a specific module to record the breach, this module is called Security Breach and serves only to record that the event happened, when and what steps were taken. A very simple version of the information.
Other things you can do
Finally, we have to talk about the customer self-service application. Although not strictly mandatory by the GDPR, as you can imagine from the explanation above it would be really nice if your clients could do some of that work themselves. Obviously depending on how much burden and on the number of requests you get it can be more or less necessary.
The idea is to have a satellite application for customers to manage their data, a place they can do things like:
You can implement any set of those and from there each company can add other services depending on their requirements: invoices, contracts, projects, quotes, ...
Keep in mind that this is actually another application independent of coreBOS that requires it's own support, customizations, and maintenance, like additional hosting and security measures (as it is an open application on the internet)
I hope to have accomplished two things with this article:
1.- transmit the idea that what coreBOS must do to adhere to GDPR lies more in the requirements of your particular GDPR compliance document than in the application 2.- show you some of the possibilities and flexibility of coreBOS to adapt to the needs of your compliance document.
If you need any help adapting your coreBOS to your needs, contact us, we probably have solved the issue before, but even if we haven't we will be able to make coreBOS do what you need.
Photo by Matthew Henry on Unsplash Matthew Henry