Skip to Content

Data protection GDPR compliance for businesses that want to keep it up to date

We put your company's data protection in order: what data you process, what for, who has access and what you would do in a breach. We leave it as a system that is updated whenever the business changes.

  • GDPR
  • LOPDGDD
  • Record of processing activities
  • Impact assessment
  • Data breaches
The problem

Compliance was done once and the company has changed

In many companies, data protection is a folder of documents from when the regulation first came into force. Since then the software, the suppliers and the way of working have changed, and the record of processing describes a company that no longer exists.

You notice the day you need it: a client asks for the data processing agreement, an employee exercises their rights or a laptop goes missing.

  • A record of processing nobody has touched in years
  • Suppliers with access to data and no data processing agreement
  • Cloud and AI tools brought in without review
  • No procedure for a breach, with 72 hours to report it
What we do

Data protection that is kept up to date

Record of processing

What data you process, for what purpose and on what legal basis, who receives it and how long it is kept. Written from how you work today.

Risks and assessments

A risk analysis of each processing activity and, where the regulation requires it, the impact assessment with its measures.

Processors and suppliers

An inventory of who processes data on your behalf, data processing agreements and a record of sub-processors. Also when you are the processor.

Individuals' rights

A procedure for answering requests for access, rectification, erasure, objection, restriction and portability on time.

Data breaches

What to do when one happens: contain it, assess the risk, decide whether to notify the authority and the people affected, and document it.

Security measures

Access, backups, encryption and data loss prevention. Whatever the analysis calls for is put in place by our cybersecurity team.

How we work

We start from what you already have

Discovery

A free one-hour session. We go over what you have done, what has changed since then and where the risk lies.

Fixed proposal

Scope, timeline and a fixed price, in writing. What is left out of the proposal is written down too.

Inventory

Interviews with each area to find out what data is really processed, in which software and with which suppliers.

Documentation

Record, analysis, agreements, privacy notices and procedures. The technical measures, each with a date and an owner.

Maintenance

An annual review, and another every time a new piece of software, supplier or data processing activity comes in.

Case studies

Compliance that is kept up to date

Read on

Standards that share work with the GDPR

GRC and ESG

ISO 27001

Implementing your information security management system, from the risks through to the certification audit.

GRC and ESG

Responsible AI and the AI Act

An inventory of the AI your company uses, risk classification, rules of use and a management system under ISO 42001.

GRC and ESG

NIS2 and DORA

Find out whether NIS2 or DORA apply to you, what you're missing and how to comply with measures you can demonstrate.

Cybersecurity

The technical measure that keeps data from leaving

Cybersecurity

Data loss prevention

Classifying your information and controlling email, cloud, USB and web uploads, so your data doesn't leave the company.

Frequently asked questions

What people ask us about the GDPR

Does my company need a data protection officer?

Only in the cases the regulation sets out: public bodies, companies whose core activity is regular and systematic monitoring of people on a large scale or large-scale processing of sensitive or criminal data, and the organisations listed in article 34 of the LOPDGDD, Spain's data protection act. We check this in the discovery session.

Can you be our data protection officer?

No. We are the ones who implement and run your systems, and we can't also be the ones who oversee them. If your company needs a DPO, it has to be someone independent of us.

We did our compliance work years ago. Do we have to do it again?

All of it, hardly ever. It needs updating: which processing activities have changed, which suppliers are new and whether the security measures are still the right ones.

What do I do if I suffer a data breach?

Contain it, find out which data is affected and assess the risk to the people concerned. If there is a risk, the GDPR gives you 72 hours to notify the supervisory authority. With the procedure written in advance, you can meet that deadline.

We use AI tools with client data. Is that a problem?

It can be if the tool has no data processing agreement, takes the data out of the European Union without safeguards or uses it to train its models. We review each tool and put in writing what data can be given to it.

How do you apply it yourselves?

SolveIT maintains its record of processing activities, its record of sub-processors and a data processing agreement for the clients whose data we process. We host Odoo and eramba on our own servers in the European Union.

Does your data protection describe the company you are today?

Tell us what you have and what has changed since it was done. In an hour you'll know what needs updating.