Privacy policy
To optimize the visitors experience, I use a web analysis platform called Matomo (formerly Piwik). I have configured it in a way so that no cookies are set and used for that purpose. In the background all data is anonymized and stored on the servers database. It is therefore not using any personal data and the data can therefore absolutely not provide any information about the person behind it.
To grant the functionality of buying licences cookies are being stored. I consider mainly the income choice as person related data. Furthermore the chosen pieces and or services are being stored in the cookies as some kind of "order list". I do not consider these data as person related, since these are just data from this site itself. After accepting the respecting cookie consent you agree that this is ok to you.
For purchases, a form with personal information must be filled. This is securely transmitted to the server, processed there and I receive an email with this data. They do not remain in any database on the server, but only in my mailbox for further processing of the purchase (in accordance with Article 6, paragraph 1, letter b of the GDPR).
Furthermore there is the so called session-id, which is stored as a cookie. It is stored as a legitimate interest based on article 6, number 1, letter f of the GDPR. This cookies is being deleted automatically after ending the browser session.
You also can delete the cookies at every moment after that.
For analysis purpose there are being stored some none personal related event data on the server. These are the following:
-
Session-ID: A random string, which grants the server to understand which visiting session it is about. Since this string is totally random, it is not possible to backtrace the person behind this session. Thus it is non person related data.
-
Timestamp: The date and time of the event as a so called unix-timestamp. Also not person related.
-
Event type: The type of event. For example this can be if you played or downloaded something. Not person related as well.
-
Event page: The page, on which the event was executed. Not person related as well.
-
Piece-ID: The id of the respecting piece, for which the event was caled. Also not person related.
-
Piece title: The title of the respecting piece, for which the event was caled. Not person related at all.
-
Free text: It is possible to enter free text in the search field. It is not necessary to enter personal data, but it is technically possible. If a visitor does so, they consents and agree to this information being stored in the database. Once again: this is merely a technical possibility that is not intended to be used in this way.
But why? Is use the data to see which pieces are being played or even being downloaded the most. This way I can see what kind of music I could produce in the future more to better serve the needs of you! Another reason is to optimize the search engine in the backend. I store this together with the session-id to prevent spamming events.
I would like to point out that data transmission over the Internet (e.g. when communicating by e-mail) can have security gaps. A complete protection of the data against access by third parties is not possible. I also offer mail traffic with PGP encryption!