Alstre
Try it
12 · Security

Data protection in practice

The system records customer consents together with the date and source, and each record can be given its own data retention date. We explain how this works and how to respond to requests from the people whose data you process — under the GDPR in the EU, or the data protection law of your country.

Who is the data controller

For your customers' data, the controller is you. We are the processor — we act on your instructions, under a data processing agreement.

The practical conclusion is this: you decide what data goes into the system, on what legal basis and how long it stays there. A customer addresses a request for erasure or access to you, and we carry it out on your instructions.

The details of the division of roles are set out in the data processing agreement, and the scope of processing — in the privacy policy.

Which law applies is up to where you operate
If your company is in the EU, your customers' data is covered by the GDPR. Outside the EU, the data protection law of your own country applies. The tools described below — consents with a date and source, retention dates, erasure — work the same either way.

Consents recorded on the customer record

The customer record stores two independent consents, and for each — when it was given and where it came from.

Consent to data processing
The date given and the source. The source may be a paper form, a phone call or the measurement protocol — you enter whatever matches reality.
Marketing consent
Separate from the previous one, because it concerns something else. Ticking it fills in the current date, but only when the field is still empty — a consent from a year ago will not be replaced with today's date during an ordinary edit of the record.
Withdrawal of consent is not recorded with a date
Unticking the marketing consent simply switches it off — the panel does not record the day the customer withdrew it. Since you must be able to demonstrate both the giving and the withdrawal of consent, it is worth noting the moment of withdrawal outside the system or in the customer's notes.
Why a source and not just a checkbox
A “consent: yes” checkbox on its own is not proof. During an inspection or a dispute, what counts is whether you can demonstrate when and in what circumstances the customer gave that consent. That is why the source field is worth filling in specifically, not vaguely.

Retention date

Every customer record has a field with the date until which the data is to be kept. For a new record the system fills in six years, to the end of the calendar year. This is a default, not the rule of your country — set the period your local limitation and tax-record rules require. The value can be changed per record, because different categories of customers have different grounds for retention.

A customer with whom a contract was concluded is tied to the limitation period for claims and to tax obligations. An enquiry that did not end in a sale has no such grounds, and its data should be removed much sooner.

The date itself does not delete anything
The retention field is an organisational marker — it is there so that you know what to review and when. The system does not delete records automatically after this date. The decision to delete is made by the data controller, that is, you.

Deleting a customer record

Deleting a record works as a soft delete: the record is no longer available in the app and is excluded from search, but it stays in the database marked with the deletion date.

There is a reason for this. The customer record is linked to measurements, quotes, contracts and service requests — documents that must match the accounts and that have to be kept regardless of what happens to the record itself. Hard-deleting the row would break those links.

Right to be forgotten
If a customer requests permanent erasure of their data and there is no basis for keeping it, deleting the record in the panel is not enough. Send such a request to rodo@alstre.com — we carry out permanent erasure on the database side, on the instructions of the data controller.

Accountability: who did what

Operations on data go into the event log together with the user, the IP address, the location determined from it, and the time. This is the material that lets you answer the question of who accessed a specific person's data.

The scope and how to view it are described in Audit log. Only administrative roles have access to the log.

Limiting access
The simplest data protection tool is not the log but permissions. A sales adviser who sees only their own customers has no way to download the whole database. The visibility scope is set on the user account — see Roles and permissions.

Providing data to the person it concerns

There is no automatic database export
The system currently has no function to generate a package with a single customer's data, nor to export the whole database to a file. A data access request has to be handled manually: collect the information from the customer record and the linked documents and pass it on to the person concerned.

The customer record shows all linked measurements, quotes, contracts and cases in one place, so collecting this data comes down to reviewing a single view. Documents can be downloaded as PDF.

If you need the complete data as a file — for example when switching systems or for a broader access request — write to biuro@alstre.com. We provide data from the database on the instructions of the data controller.