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.
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.
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.
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.
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.
Providing data to the person it concerns
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.
