Legal
Privacy policy
Controller and contact
KIM Systems GmbH, Niedersulzer Straße 2, 2225 Loidesthal, Austria. Questions and rights requests: office@kimsystems.at. See the imprint.
Website delivery and security
This website is hosted on a virtual server provided by easyname GmbH, Canettistraße 5/10, 1100 Vienna, Austria. Delivering the website involves processing connection information, including your IP address and browser request. Server access logs may record requested addresses and access times. Processing is based on the legitimate interest in secure, reliable operation (Article 6(1)(f) GDPR). Plesk-managed logs are configured for daily rotation with 14 retained compressed archives in addition to the active log. This retention setting applies to Plesk-managed logs, not separate application logs, and is based on the number of archives rather than an exact 14-day deletion deadline.
Contact requests
The form asks for your name, email address and message so we can reply. Providing these details is voluntary; without them the form cannot be submitted. A confirmation containing a copy of your message is also sent to the email address you provide. General correspondence is handled on the basis of legitimate interests in responding to enquiries; requests concerning a contract may fall under Article 6(1)(b) GDPR. We do not subscribe you to marketing emails through this form.
Contact messages are delivered through Google Workspace to our info@playtiss.eu group and its authorised members. We retain correspondence for 24 months after the enquiry or conversation has concluded, then delete it from the group archive and receiving mailboxes, unless applicable legal retention obligations or the establishment, exercise or defence of legal claims require longer retention.
Cookies and local assets
The application uses first-party session and security cookies for form validation and authenticated administration. The configured session lifetime is 120 minutes; session handling can renew this period. Fonts and homepage artwork are served locally. This implementation does not add analytics or advertising pixels.
Cookie preferences
We use CookieYes to display cookie choices and manage consent preferences. Loading this service connects your browser to CookieYes. The service may store your preference and a consent record. Use its cookie preferences control to review or change your choices.
Direct music playback
The homepage music player serves audio from this website when you start playback. It does not require a Spotify login or connect to Spotify to play these files. Audio requests, including requests used for seeking, are handled by the website server and may appear in its access logs. External streaming links and optional embedded players are separate.
Optional Spotify and YouTube media
Embedded players are blocked until you choose to load the relevant provider. Loading a player shares connection and browser data with that provider; it may use cookies and process data outside the EEA. Activation is optional and based on consent (Article 6(1)(a) GDPR). You can close the Spotify dialog or select “Remove video” to stop that embedded connection. Consent is not remembered across page loads. Removing a player does not erase data already processed by its provider.
Read the provider information before activating: Spotify privacy policy and Google / YouTube privacy policy, including their international transfer safeguards. A normal external link takes you to that provider’s website, where its own rules apply.
Your rights
Subject to the GDPR conditions, you may request access, correction, erasure, restriction or portability of your personal data. You may object to processing based on legitimate interests and withdraw consent for future processing without affecting the lawfulness of earlier processing. Contact the controller above. You may complain to the Austrian Data Protection Authority or your competent supervisory authority.
Contact-form abuse protection
When enabled, Google reCAPTCHA Enterprise helps protect the contact form from automated abuse. After you allow verification and submit the form, your browser connects to Google and obtains a verification token. Google processes technical and interaction signals to assess the submission. Our server checks the token, website, action and risk score before sending your message. This automated assessment can prevent submission. If you do not wish to use verification or it fails, you can contact us directly by email. Our backend does not send your message text, name or email address to the reCAPTCHA assessment endpoint.
Google's Privacy Policy and Terms of Service apply. We also limit repeated submissions to protect the form.
Last updated: 14 September 2026.