Legal and fair dealing
Privacy policy
This is a translation for convenience. The German version is legally binding.
This Privacy Policy applies to the Lumeya platform at https://web.lumeya.ai (website and app, together the "Platform"). For the websites that our customers create with Lumeya (customer sites), the respective customer is the controller and their privacy policy applies; we process this data on their behalf (Sections 7 and 11). The exception is the server logs under Section 3: we also keep these for the customer sites as an independent controller.
1. Controller
Luminant Mind e.U.
Owner: Youns Murhidj
Johannagasse 29-35/14/5
1050 Vienna, Austria
Email: office@luminantmind.com
No data protection officer has been appointed because the requirements of Art. 37 GDPR are not met. Please direct data protection enquiries to office@luminantmind.com.
Legal bases: General Data Protection Regulation (Datenschutz-Grundverordnung, GDPR) and the Austrian Data Protection Act (Datenschutzgesetz, DSG).
2. Summary
- We host the Platform on our own servers at Hetzner in Germany (EU).
- We use only two technically necessary cookies, and only once you log in. There is no advertising, no tracking and no sale of data.
- The onboarding assistant and the website texts use a language model from an external provider; your details go to this provider for that purpose. The “Ask Lumeya” chat works rule-based on our own servers.
- Enquiries that visitors send through the contact form of your customer site are processed by us on your behalf (data processing on behalf of a controller).
3. Hosting and server logs
What: When the Platform and the customer sites are accessed, our server processes, as technically necessary, the IP address of the requesting device, date and time, the requested address, the status code, the amount of data transferred, the browser identifier (user agent) and the previously visited page (referrer), in order to deliver the page and to detect and defend against attacks.
Role: We keep these server logs for the entire Platform, including the customer sites, as an independent controller. They are not part of the data processing we carry out for our customers.
Storage: The access log of our web server contains the IP address. It is rotated daily; older files are deleted, so that no entry is older than about 7 days. It contains requests to the Platform and to customer sites under the Lumeya address (https://web.lumeya.ai/s/…); for customer sites under their own domain, the web server keeps no access log. Error messages of the web server and security messages of the operating system (e.g. firewall, protection against login attacks on the server) may also contain IP addresses. They are located in the system log of the server, which is rotated daily and deleted after about 7 days at most; if it exceeds 1 GB, the oldest entries are deleted earlier. We do not create further copies of these messages in other log files. The protection against login attacks additionally maintains a block list with the IP addresses of blocked senders; entries in it are deleted after one day at most. The application logs (error and operating messages) do not contain IP addresses; they are rotated daily and deleted after 14 days.
Legal basis: Art. 6(1)(f) GDPR (secure, stable operation).
Service provider: Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, Germany (data centre in Germany), with a data processing agreement under Art. 28 GDPR. Administrative access to the server is possible only with a cryptographic key; the administration area of the application can be reached only through a private, encrypted network (VPN).
4. Account and registration
What: Name, email address, password (stored only as an Argon2id hash, never in plain text), time of registration and of the last login, your settings (e.g. how often Lumeya asks follow-up questions) and your consent to the Terms of Use and the data processing agreement, with the time and the version of these texts and of the Privacy Policy in force at that time (as a checksum). For the "Logged-in devices" list, we store for each login a session identifier (as a hash only), the browser identifier, and the start and last use. We record security-relevant and contract-relevant actions with a timestamp in a log (e.g. registration, consent, login, change or reset of the password, logging devices out, connecting or disconnecting a custom domain with the identifier of the website, without the domain name). We also log measures taken by our team on your account (e.g. block, credit, password reset), there only with the random identifier of your account.
Subscription: Plan, status, price, billing period, credit with bookings, whether it is a free beta subscription, whether you ordered as a business or as a consumer, for consumers the consent to immediate commencement, and the subscription history (e.g. conclusion with plan, price and the version of the Terms of Use, withdrawal information and Privacy Policy as a checksum; cancellation with time, channel and a reason given voluntarily; withdrawal with time and channel, and for a withdrawal without login also receipt and confirmation; announcement of the end of the beta phase).
Purpose: Providing the account, performing the contract, proving the conclusion of the contract and consents, protecting the account.
Legal basis: Art. 6(1)(b) GDPR (contract); for records of proof and security logs, Art. 6(1)(c) and (f) GDPR.
Duration: Until you delete your account. If your subscription ends (through cancellation, withdrawal or the end of the beta phase), the account and data remain until you delete the account; there is currently no automatic deletion of inactive accounts. Deletion in the settings takes effect immediately. We then delete all data of your account: account, sessions, links for resetting the password and for confirming a withdrawal, credit with bookings, subscription and subscription history (including any reason for cancellation given), the entire log from this Section, projects with onboarding conversation, websites with all versions, blog posts, SEO settings, enquiries, statistics and check results, images including image files and image jobs, your chats with "Ask Lumeya" (including archived ones), the delivery records of the emails relating to your account (with delivery status), undelivered confirmation emails, as well as the isolated environment and the cache from which your websites are served. There are currently no invoices that we would be required to retain (Section 9). Login attempts and entries of our internal usage statistics lose their link to your account and to your email address; login attempts are deleted once their retention period expires (Section 5). Only a record of the deletion (random account identifier, number of deleted websites, enquiries and images, time) and the entries on measures taken by our team on your account are retained, both without your name and your email address, only with the random account identifier. We keep them in order to be able to demonstrate that and how we acted (Art. 6(1)(f) GDPR); no automatic deletion period is currently set up for them. Reports by third parties about content of your website expire after their own period (Section 13). Backup copies expire according to the periods in Section 16.
5. Login protection and password
What: For every login attempt, we store the time, the identifier entered (email address), the result (successful or reason for failure) and a key of your IP address. We do not store the IP address itself, only a hash formed with a secret server key (HMAC-SHA-256, truncated). It cannot be reversed without this key, but it shows us whether attempts come from the same address. In addition, we limit the number of attempts per address and per account.
Forgotten password: If you request a link to reset your password, we store only a hash of it in the database. The link is valid for one hour and only once; the hash is deleted one day after expiry at the latest. The link carries the key behind a "#": this part is not sent by the browser to our server and therefore does not appear in the access log (Section 3). The delivery record of the email (Section 10) does not contain the link: we make it unreadable before storing.
Legal basis: Art. 6(1)(f) GDPR (security of the account) and Art. 32 GDPR; for the reset, Art. 6(1)(b) GDPR.
Duration: Login attempts 30 days, then automatic deletion.
6. Cookies and local storage
We use only cookies that are strictly necessary so that you can stay logged in and use the Platform securely (Section 165(3) of the Austrian Telecommunications Act 2021 (Telekommunikationsgesetz 2021, TKG 2021); for users in Germany, Section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz, TDDDG)). No consent is required for this, which is why there is no cookie banner. Both cookies are created only upon login or registration:
- __Host-lumeya: keeps you logged in (random session identifier; only via HTTPS, not readable by scripts). Duration: 30 days from login, 12 hours for admin accounts. It is deleted when you log out.
- lumeya_csrf: protects your inputs against forged requests from third-party sites (CSRF protection), bound to the session. It is transmitted only via HTTPS and not with requests originating from third-party sites; the Platform's script must be able to read it, but it contains no login secret. Duration: same as the session.
There are no analytics, advertising or third-party cookies. We do not permanently store anything in your browser's storage (no Local Storage). Only as long as the browser tab is open, Lumeya remembers in a temporary storage that your browser deletes when the tab is closed which chat was last open (for two hours at most) and whether the chat window is open, and, when Lumeya takes you to another page, for 60 seconds at most, what is to be shown there next. No content, no tracking. We load fonts and all other files from our own server, not from third-party services.
7. Visitor statistics of customer sites (without cookies)
On the Platform itself, we do not collect visitor statistics. For customer sites, on behalf of the respective customer, we count how often a page was delivered (home page, blog overview and blog posts) and how many enquiries were submitted through the contact form. Only daily totals per website are stored: page views in total, per page and by rough origin (search engine, AI assistant, social network, other website, direct or within the website) as well as by device category (mobile phone, tablet or computer) and enquiries.
Counting takes place on our server at the moment it delivers the page. In doing so, it processes only information that every request brings with it anyway (Section 3): the requested address; the browser identifier, in order not to count search engines and other programs and to roughly classify the device as mobile phone, tablet or computer (we do not store the identifier itself); the previously visited page, only to derive the rough origin from it (we do not store its address); and the IP address, for the statistics only truncated to the network (IPv4: the first three blocks, IPv6: the first 48 bits). The truncated address serves solely to avoid counting mass requests from the same network; it is held in working memory for about one hour at most and is not stored. The customer sites contain no statistics script, set no cookies and store nothing in the browser's storage. We do not create an identifier that recognises visitors, not even for one day; we therefore do not record how many different people have visited a website. We do not count clicks on buttons or telephone numbers.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest of the customer in data-minimising audience measurement); we act as processor under Art. 28 GDPR.
Duration: We delete the daily totals after 25 months (counted in full calendar months), and immediately upon deletion of the account.
8. Onboarding conversation, "Ask Lumeya" chat and website creation
What: Your input in the onboarding conversation (e.g. business, services, opening hours, desired texts) with the conversation history, content and settings of your websites, blog posts, uploaded images, the saved versions of your website and the results of checks of your website (e.g. Neurodesigntest).
Processing: The onboarding assistant and the website texts use a language model from an external provider; your details go to this provider for that purpose. The website is created from templates on our own servers.
Uploaded images: Each image is checked and re-encoded in an isolated environment without network access. In doing so, we remove embedded metadata (e.g. camera data and GPS position). We do not store the original image. When uploading, you confirm that you hold the rights to the image; we store this confirmation with a timestamp.
AI images: If the image generator is enabled on the Platform, it creates images for your website on our own server. The image description (subject, style) does not leave our server in the process; we store it with the image job. AI images carry in their metadata (IPTC/XMP) the note that they were created with AI. If an AI image is visible on a page of your website, the footer of that page also points this out ("Some images were created with AI"); this also applies to AI cover images of blog posts on the home page, in the blog overview and in the post. An exception and what you should do in that case can be found in the Terms of Use (Section 7.6).
"Ask Lumeya" chat: In the “Ask Lumeya” chat, an assistant answers your questions and, at your request, carries out tasks in your account. Whatever it cannot answer using fixed rules is phrased by a language model from an external provider; your message and the necessary context go to this provider for that purpose. We store your messages and the replies as chats in your account so that you can find them again later. You can hold several chats, rename them, pin them and archive them. "New chat" deletes nothing. You can permanently delete individual chats or all chats at any time; open follow-up questions lapse as a result. Your chats are included in your data export.
If you have enquiries displayed in the chat or process them there (e.g. "Mark the enquiry from … as won"), Lumeya's replies mention details of the people making the enquiry: the name, and in the overview also the contact detail and the beginning of the message. For this, as with the enquiries themselves, we act as your processor (Section 11). If you delete such an enquiry (or we delete it on suspicion of spam after 30 days), we replace Lumeya's replies and follow-up questions that mention it with a notice; an automatically assigned chat name that originates from your message is reset. What you yourself wrote in the chat remains until you delete the chat. Irrespective of this, we replace the text of replies containing third-party details with a notice 90 days after the reply.
We automatically delete chats without a new message 12 months after the last message, including archived ones. Queued follow-up questions (e.g. "Really publish?") are deleted 90 days after they are resolved; unconfirmed ones lapse after 30 minutes and are marked as cancelled after one day.
Legal basis: Art. 6(1)(b) GDPR.
Duration: We store websites with all versions, the onboarding conversation, check results and image jobs until you delete your account. You can take a website offline yourself but cannot delete it individually; we do that on request to office@luminantmind.com. You can delete blog posts and images individually yourself. We store "Ask Lumeya" chats for up to 12 months after the last message, until you delete them or until you delete your account (see above). We keep all versions of your website (every saved state of the draft and every version that was online) until you delete your account, but for at least 90 days; this way you can restore an earlier version.
9. Payments and invoices
During the beta phase, Lumeya is free of charge. No payment provider is connected, and we do not collect payment data (e.g. card number or IBAN). Before paid subscriptions start, we will name the payment service provider in this Section and inform you in good time by email.
Once we bill paid subscriptions, we retain invoices and the contract data required for them for 7 years (Section 132 of the Austrian Federal Fiscal Code (Bundesabgabenordnung, BAO), Section 212 of the Austrian Commercial Code (Unternehmensgesetzbuch, UGB)); the legal basis is then Art. 6(1)(b) and (c) GDPR.
10. Emails and support
- Transactional emails (order confirmation with Terms of Use and, for consumers, withdrawal information as a text file, confirmation of a plan change, cancellation confirmation, confirmation of the revocation of a cancellation, acknowledgement of receipt of a withdrawal, for a withdrawal without login with a link for confirmation, confirmation of a withdrawal, announcement of the end of the beta phase, link for resetting the password, notice of new enquiries to your website, acknowledgement of receipt and decision on reports) are sent by us through the email service of our mail provider (processor), and only over encrypted connections. Notices of new enquiries contain no details of the person making the enquiry; you see these only in Lumeya. Legal basis: Art. 6(1)(b) GDPR, for reports Art. 6(1)(c) GDPR in conjunction with Art. 16 DSA.
- Delivery records: Of every email sent, we store the recipient, subject, text, the names of the attachments (not their content) and the time, in order to be able to prove, for example, that a cancellation was confirmed. In addition, we record which mail provider accepted the email and when, its identifier of the email and the delivery status it reports (e.g. delivered or undeliverable); the recipient address appears there only as a checksum. Links with keys (e.g. the link for resetting the password, for confirming your email address or a withdrawal) are made unreadable before storing; the email itself contains them in full. We assign each record at the time of sending to the account for which the email was sent, never subsequently via the recipient address. We delete records of emails relating to an account after 730 days (two years), and immediately upon deletion of the account. We delete records of emails without a link to an account (e.g. to persons who reported content) after 365 days. Legal basis: Art. 6(1)(c) and (f) GDPR.
- Retry after sending errors: If sending a confirmation (order, plan change, cancellation, withdrawal, end of the beta phase) fails, we store the email (recipient, subject, text and attachments) and try to deliver it again for about 4 days; if that does not work, the administration area shows us this. Once the email is delivered, we delete the entry immediately, otherwise 30 days after the first attempt at the latest, and immediately upon deletion of the account. Legal basis: Art. 6(1)(b) and (c) GDPR.
- No promotional emails: We send no newsletter and no advertising by email.
- Support enquiries by email are stored by us for as long as necessary for processing and traceability, for 24 months at most. Legal basis: Art. 6(1)(b) and (f) GDPR.
11. Contact form enquiries on your customer site (data processing on behalf)
When visitors use the contact form of your customer site, we store their details (name, email address or telephone number, message and, where applicable, desired appointment and selected service) with a timestamp and spam score on our server and show them to you in Lumeya under "Enquiries". You are the controller for this; we process this data only on your behalf under the data processing agreement (Art. 28 GDPR). We automatically delete enquiries identified as spam after 30 days. We delete all other enquiries by default after 12 months; the period can be set per account to between 1 and 120 months. You can export them as a CSV file at any time. If you have enquiries displayed in the "Ask Lumeya" chat or process them there, Section 8 applies to these replies. If you delete the enquiry, we also replace Lumeya's replies in the chat that mention it with a notice. Your own messages in the chat remain until you delete the chat. You inform visitors to your customer site in your own privacy policy; for the server logs you can refer there to Section 3 of this policy.
12. Custom domain and certificates
If you connect a custom domain to your customer site (provided this function is enabled on the Platform), we store the domain name and the status of the check, and we query the public DNS to see whether the domain is set up correctly. Once it is connected, our server requests a TLS certificate for the domain from the certification authority Let's Encrypt (Internet Security Research Group, USA) upon the first request. Only the domain name is transmitted in the process; as with every public certificate, it appears in public certificate logs (Certificate Transparency). Because the certification authority is based in the USA, this is a transfer to a third country; it is necessary for the connection of the domain that you requested (Art. 49(1)(b) GDPR). Legal basis: Art. 6(1)(b) GDPR. If you disconnect the domain or delete your account, the certificate (which contains only the domain name of your details) may remain in the certificate storage of our web server until it has expired and is cleaned up.
13. Reports on content (DSA)
Anyone who reports content through our reporting form provides the address concerned (URL), a category and a justification; name and email address are optional. With an email address, we send an acknowledgement of receipt and later our decision (Art. 16 DSA). We use the data to process the report and to detect misuse of the reporting procedure. We retain open reports until they are closed, and closed cases for 365 days (12 months) from the last processing; after that we delete them automatically. We retain the emails to the reporting person (acknowledgement of receipt and decision, with case number, reported address and justification) as a delivery record for 365 days (12 months), even if the address belongs to a Lumeya account: they belong to the report, not to the account (Section 10). Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 16 DSA and Art. 6(1)(f) GDPR. We do not disclose the identity of the reporting person to the customer concerned unless this is legally required.
14. Cancellation and withdrawal without login
Via Cancel contracts here you can cancel without logging in and, as a consumer, declare your withdrawal under Withdraw from contract. For this, we process your name, the email address of your account, voluntarily the contract number, for a cancellation a desired termination date and a further email address for the confirmation and, for an extraordinary cancellation, the reason given, in order to assign the declaration to your account and to confirm receipt to you by email. In the subscription history of your account, we record the type of declaration, channel and time of receipt, and for a cancellation also the reason (Section 4). We do not store the name entered in the form there; for a withdrawal it appears, marked as your information, in the confirmation email and thus in the delivery record (Section 10). If email address and contract number match, a withdrawal without login takes effect immediately. Without a matching contract number, we record the declaration with its receipt until it is assigned (it does not lapse; after assignment, we delete the entry after 30 days); this way nobody who knows only your email address can end your subscription. A cancellation without a contract number takes effect if name and email address match an account; the confirmation to the address of the account contains a link with which the cancellation can be revoked until the end of the contract. Of this, we store only a checksum with the receipt and the validity. So that nobody can trigger mass emails to a third-party address through the forms, they send at most 3 emails per hour and 10 per day per account and per address; we nevertheless record further declarations with a timestamp. If a declaration cannot be reliably assigned to an account (no account for the address, or, for a cancellation, the name does not match the account), we store it with name, addresses given, contract number and receipt, confirm receipt to the address given and assign it; we delete processed declarations without an account after 12 months, and those relating to an account after 2 years or together with the account. Legal basis: Art. 6(1)(b) and (c) GDPR.
15. Recipients and third countries
Recipients of your data are only our processors: Hetzner Online GmbH (hosting and backup copies) and our mail provider (sending emails). For texts and the getting-started conversation and the “Ask Lumeya” chat, the provider of the external language model also receives your details. We will name a payment service provider here before paid subscriptions start. If you connect a custom domain, the certification authority Let's Encrypt receives the domain name (Section 12). Authorities receive data only if we are legally obliged to provide it.
Hosting and backup copies are located exclusively in the EU. Data may be processed outside the EU or the EEA in these cases: at the provider of the external language model (for texts and the getting-started conversation and the “Ask Lumeya” chat). For your own domains, section 12 applies.
16. Retention periods at a glance
Unless stated otherwise, an automatic deletion run enforces the following periods; it runs at application start and every six hours thereafter. Log files and backups are rotated by the server itself.
- Access log of the web server (with IP address): rotated daily, about 7 days at most; none is kept for customer sites under their own domain (Section 3)
- System log with error messages of the web server and security messages of the operating system (may contain IP addresses): about 7 days at most, earlier if over 1 GB
- Block list of the protection against login attacks on the server (IP addresses of blocked senders): 1 day at most
- Application logs (without IP address): 14 days
- Login attempts (IP address only as HMAC key): 30 days
- Sessions (logged-in devices): until logout or expiry (30 days, admin accounts 12 hours); expired sessions are deleted automatically
- Links for resetting the password: valid for 1 hour, deleted 1 day after expiry at the latest
- Withdrawal declarations without login for an account without a matching contract number (only checksum, receipt and start of contract, no details from the form): remain until they are assigned (they do not lapse); deleted 30 days after assignment or after we have discarded them, immediately upon deletion of the account
- Cancellation and withdrawal declarations without login that could not be reliably assigned to an account (name, addresses given, contract number, type of cancellation, desired date, reason for an extraordinary cancellation, receipt): until we have processed them; thereafter 365 days (12 months) without an account, 730 days (2 years) for an account, immediately upon deletion of the account
- "Revoke cancellation" links (only checksum, receipt, start of contract and end of contract): usable once until the end of the contract, deleted 30 days after the end of the contract stated in the confirmation, immediately upon deletion of the account
- Visitor statistics of customer sites (only daily totals, without identifier per visitor): 25 months, counted in full calendar months (Section 7)
- Temporary working files of image processing: after 1 hour at the latest
- Suspected spam (contact form): 30 days
- Versions of your website (draft states and published versions): until you delete your account, at least 90 days; there is currently no automatic deletion of individual versions
- Account, websites with all versions, onboarding conversation, check results and image jobs: until you delete your account (account deletion takes effect immediately), even if your subscription ends; we delete an individual website on request
- Blog posts and images: until you delete them individually or delete your account
- Genuine contact form enquiries: 12 months by default, adjustable per account to between 1 and 120 months; suspected spam 30 days (Section 11)
- "Ask Lumeya" chats (including archived ones): 12 months after the last message, earlier if you delete them or your account
- Replies in the chat with third-party details (e.g. displayed or processed enquiries): text replaced with a notice after 90 days, immediately if the enquiry is deleted
- Queued follow-up questions in the chat: 90 days after resolution; unconfirmed ones marked as cancelled after one day
- Log of security-relevant and contract-relevant actions, credit and subscription history: until you delete your account
- Record of account deletion and entries on measures taken by our team on an account (without name and email address, only with random account identifier): no automatic deletion period (Section 4)
- Delivery records (with delivery status) of emails relating to an account: 730 days (2 years), immediately upon deletion of the account
- Delivery records (with delivery status) of emails without a link to an account: 365 days (12 months)
- Confirmation emails whose sending failed: new attempts for about 4 days, deleted after delivery, otherwise after 30 days
- Reports on content: until closed, then 365 days; emails to the reporting person as delivery record 365 days
- Support emails: 24 months at most
- Invoice and contract data (once paid subscriptions are billed): 7 years
- Backup copies: daily on the server, kept there for 14 days; an encrypted second copy on separate storage at Hetzner in the EU for 12 months at most (daily snapshots 14 days, weekly 8 weeks, monthly 12 months)
Deleted data may still be contained in backup copies until these periods expire. We use these only to restore operation after an outage or error.
17. Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and the right to object to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR). Consents, if we ask you for one, can be withdrawn at any time with effect for the future.
You can do a lot yourself in the Settings: Under "My data" you download the data of your account as a JSON file: account and settings, subscription and subscription history, credit with bookings and reservations, projects with briefing, onboarding conversation and build runs, websites with all versions, design characteristics (e.g. industry, location, characteristics against look-alikes), legal texts, blog posts, SEO settings, check results and daily statistics (also per page), enquiries, images with description and image jobs, "Ask Lumeya" chats (including archived ones) with all messages and queued follow-up questions, logged-in devices (times and browser identifier), links for resetting the password and withdrawal declarations without login (times only), login attempts (including those with your email address that are not assigned to any account; from the time before registration only if you have confirmed the address), the log from Section 4 including the measures taken by our team on your account, the delivery records of the emails relating to your account (with delivery status), undelivered confirmation emails and the entries of the internal usage statistics. The file is generated without indentation and is transmitted piece by piece during download. The image files themselves are listed in the export with their identifier and can be retrieved individually in the account. Not included are security secrets (password hash, session and protection identifiers, keys in links, the key of your IP address) and data that is not assigned to your account, such as reports by third parties about your content and the server logs (Section 3); for these you receive information on request to office@luminantmind.com, insofar as the rights of third parties do not prevent this. Under "Logged-in devices" you see your sessions and log devices out, and under "Delete account" you delete your account, with the exceptions named in Section 4. You can export your enquiries as a CSV file under "Enquiries". For everything else, write to office@luminantmind.com; we reply within one month.
You can lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Austrian Data Protection Authority (Datenschutzbehörde), Barichgasse 40-42, 1030 Vienna, email dsb@dsb.gv.at, www.dsb.gv.at. You can also contact the supervisory authority of your place of residence (Germany: list of supervisory authorities; Switzerland: Federal Data Protection and Information Commissioner (Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter)).
18. Obligation to provide data, automated decisions
For an account, we need at least name, email address and password. Without this information, we cannot perform the contract. We do not make automated decisions with legal or similarly significant effect (Art. 22 GDPR). The spam filter of the contact form only pre-sorts; the decision on enquiries is yours.
19. Users in Switzerland
For persons in Switzerland, the rights under the Swiss Federal Act on Data Protection (Datenschutzgesetz, DSG) also apply. Austria and Germany are regarded as states with adequate data protection for data transfers from Switzerland.
20. Changes
We amend this policy when our services or the laws change. The current version is always available on this page.
As of: 27 September 2026