Form · Legal informationREV. 2026-A
Privacy policy (Datenschutzerklärung)
Nil return
Without your consent, this website loads nothing from third-party servers apart from our delivery service, Cloudflare.
Questions? Give us a call: +49 3744 4399760
Third-party analytics and advertising services: none embedded · Counting: our own server, page views only as totals · Third-party services: the booking calendar, which asks first, and the spam check, only once you start typing in the form
Two third-party services are embedded, both described below: the booking calendar on the appointment page, which asks first, and the spam check in the contact form, which loads only when you start typing there. The remote support program is hosted on our own server and is transferred only when you download it yourself. Everything else comes from our own server, delivered via Cloudflare; what Cloudflare adds at the edge (four insertions, all loaded from this website's own address) is described under “Delivery via Cloudflare”. All the data that arises when you visit this site is set out in full on this sheet.
Controller
The controller within the meaning of Art. 4(7) of the General Data Protection Regulation (GDPR; in German: DSGVO) is:
Aureum Technology GmbHStraße der Jugend 5
08228 Rodewisch
Managing director: Felix Götz
+49 3744 4399760 · [email protected]
Server log files
When you visit this website, our server writes one line to its operating log for every request: date and time, the address requested (without parameters), response status, amount of data transferred, duration, the browser identifier (user agent), a country code added by Cloudflare, and the other technical details your browser sends with the request. This data is needed to deliver the page and to keep the service secure, for example to detect attacks and faults.
Your IP address is not in our own log. The address of the peer that our server itself sees is not yours but that of the network edge in front of it (Cloudflare and our host, see below); even that address is stored only in shortened form, with the last part set to zero. The headers in which Cloudflare passes on your own address are deleted by the server before the line is written. Also not logged are the address of the page you came from (referrer), parameters in the address requested, the content of cookies, your preferred language and the device details that newer browsers send in addition (client hints). All of this applies to the log that our server writes itself. Our host keeps its own access log alongside it, and that log does not shorten addresses; see “Hosting with Railway”.
The legal basis is Art. 6(1)(f) GDPR (legitimate interest in stable and secure operation). The log is not combined with other data and is not used to analyse your behaviour; the counting described below does not read from it either. It is not stored as a file on our server but in our host's log view (see “Hosting with Railway”), where it is deleted automatically after a short period, after 30 days at the most.
Hosting with Railway
Our server runs on Railway (Railway Corporation, San Francisco, USA), in its data centre in Amsterdam (EU West region). That is where the website, the service behind the forms and the counting totals described below are stored; according to its own statements, Railway makes no backup copy of this storage. Railway processes this content and the operating log of our server on our behalf (Art. 28 GDPR); Railway collects the operating log and keeps it for the period stated above.
In addition, Railway keeps an access log for each request at its own network edge: time, host, address requested (without parameters), response status, the browser identifier and, unlike in our own log, your full IP address. Railway is itself responsible for this, not us; we cannot switch it off. According to our host, it serves to operate its platform and to trace faults; it is deleted there automatically after 30 days at the most. What Railway relies on for this is set out in Railway's own privacy policy, linked at the end of this section.
We rely on Art. 6(1)(f) GDPR (legitimate interest in stable and secure operation) for engaging a host to operate this website and thereby disclosing your IP address to it. A transfer to the USA is possible. Railway is certified under the EU-US Data Privacy Framework (adequacy decision of the European Commission, Art. 45 GDPR). Should that certification ever cease to apply, the standard contractual clauses of the European Commission that we have agreed with Railway apply (Art. 46(2)(c) GDPR). You can obtain a copy of these clauses on request to [email protected]. Further information on data processing at Railway: railway.com/legal/privacy.
Delivery via Cloudflare
This website is delivered via the network of Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA. Cloudflare protects the site from attacks and delivers it faster; as a result, every visit technically runs through Cloudflare servers. In doing so, Cloudflare processes your IP address and the other access data that your browser sends with the request.
Cloudflare works on our behalf (Art. 28 GDPR); the legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and fast operation). Cloudflare is certified under the EU-US Data Privacy Framework; processing in the USA is nonetheless possible.
When delivering our pages, Cloudflare adds four things that do not come from our own code. All of them load from this website's own address, not from a third-party server:
- Bot detection. A short script in the head of every page that would load a second file from /cdn-cgi/challenge-platform/… in order to detect automated requests. Our security policy (Content Security Policy) does not permit this inserted script; it therefore does not run in your browser, and on an ordinary visit Cloudflare sets no cookie. If Cloudflare detects an attack or automated requests, it may first show a check page of its own and run a short check in your browser before delivering the page and, once the check is passed, set the cookie cf_clearance, which records the result for this website. It serves solely as a defence and not to recognise you across other websites.
- E-mail obfuscation. To protect against address harvesters, Cloudflare replaces e-mail addresses in the source code and inserts a small script (email-decode.min.js) that makes them readable again in your browser. It transmits nothing to third parties.
- Preloading our own pages (Speculation Rules). A response header pointing to a rules file under /cdn-cgi/speculation; with it, your browser can load the next page of this website before you click on it. The request goes to our own server; we do not count pages loaded in advance (see “What we count on our server”).
- A script file for machine-readable interfaces (WebMCP, /.webmcp/bridge.js), which Cloudflare inserts into the head of every page. It loads from this website's own address.
In addition there is the spam check in the contact form (Cloudflare Turnstile). Unlike the four insertions, it loads from challenges.cloudflare.com, and only once you start typing in the form; it is described below under “Contacting us”.
Further information on data processing at Cloudflare: cloudflare.com/privacypolicy.
Contacting us
If you phone us, write us an e-mail, or use the contact form or the e-mail form on the PC help page, we process the details you give us in doing so, such as your name, phone number, e-mail address and your enquiry, solely in order to deal with your request. The legal basis is Art. 6(1)(b) GDPR (initiating or performing a contract).
We do not pass this data on, and we delete it as soon as it is no longer needed to deal with your request and no statutory retention obligations stand in the way.
How the form works in detail: your entries go to our own server, encrypted. It turns them into an e-mail to our inbox and keeps nothing of what you enter: there is no database and no copy beyond sending. It merely counts that an enquiry arrived, as a total per day, page and form type and in the weekly grid for the whole website, described in more detail under “What we count on our server”. From our server onwards, your message takes the same route as any other e-mail to us: our inbox is hosted on Google Workspace (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Google processes the messages on our behalf (Art. 28 GDPR); processing in the USA is possible. Google is certified under the EU-US Data Privacy Framework. The same applies if you write us an e-mail of your own accord. If JavaScript is switched off in your browser, your entries likewise go to our server. If it then cannot carry out the spam check described below, you receive your entries back as a ready-made draft for your own e-mail program; nothing is stored in the process.
The e-mail form on the PC help page takes the same route. It manages without the spam check described below: your browser merely sends along how much time passed between loading the page and submitting. This figure serves only to fend off scripts and is not stored. If JavaScript is switched off, this form instead opens your own e-mail program; you alone then decide which provider the message goes out through.
Spam check on the form. So that the form is not misused by scripts, we check once before sending that a human is writing. For this we use Cloudflare Turnstile (Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA). The check is loaded only when you start typing in the form; anyone who merely reads the page makes no connection to Cloudflare. In the process, your IP address and technical details about your browser and device are transmitted to Cloudflare; according to its own statements, Cloudflare does not use cookies for advertising purposes here. The legal basis is Art. 6(1)(f) GDPR, our legitimate interest in protecting our inbox from automated messages. When we fetch the result of the check from Cloudflare, we deliberately do not send your IP address. Further information: cloudflare.com/privacypolicy.
If you wish, you can attach a file to the form, for example an image of an error message. The attachment takes the same route as the rest of the text and ends up as an attachment to the same e-mail in our inbox; it is not stored on the website's server. Your browser reduces the size of images before they leave your computer. In doing so, it removes the metadata stored in phone photos, including the location where the photo was taken. If at all possible, please do not send us documents containing third-party data through this field; an attachment cannot be retrieved after sending.
On the form you decide how we reply: phone number or e-mail address, one of the two is enough. If you give an address, we use it for two things: it appears as the reply address in the enquiry so that we can also answer you in writing, and you receive a short confirmation that your enquiry has arrived. This confirmation deliberately contains nothing of what you wrote, as otherwise the form could be misused to deliver texts to strangers. We send no advertising through it. Without an address, both are omitted; we then need your phone number. Only your name and one of the two ways of replying are mandatory. This also applies to the e-mail form on the page for home users; there, however, we send no confirmation but reply directly.
To prevent the form from being misused on a large scale, we limit the number of submissions per connection. Your IP address is not stored for this: it is only turned into a check value that cannot be reversed, is held in memory, expires after one hour and becomes worthless anyway when the service restarts. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in a functioning means of contact).
Free website check (SpotLens)
On the page /spotlens you can start a free website check. For this we process the address of the website to be checked, your e-mail address for the report and, only if you provide it, your phone number for questions about the check. The details go to our own server, encrypted; it passes them on to SpotLens and keeps nothing of what you enter. It merely records that a check was submitted in this hour and, if SpotLens accepted it, started: one line each, with the time rounded to the full hour, without your data, without the address checked and without an IP address. It also counts a started check as a total per day and page, like an enquiry through a form (see below under “What we count on our server”). From this we see only how often the form is used. The recipient is ArrowTrade AG, Nordstrasse 2, 3900 Brig-Glis, Switzerland; we operate the checking tool together with it, and an adequacy decision of the European Commission exists for Switzerland (Art. 45 GDPR). The legal basis for the transfer, the check and the result e-mail is Art. 6(1)(b) GDPR: you request the check, and it is delivered. SpotLens keeps the details only for as long as it needs them to carry out the check and deliver the report.
By ticking the box in the form, you consent to the operators of SpotLens (Aureum Technology GmbH and ArrowTrade AG) contacting you about suitable offers: by e-mail, and by phone only if you gave a number. The legal basis is your consent (Art. 6(1)(a) GDPR). Starting the free check requires this consent; this is also stated on the form. You can withdraw it at any time with effect for the future; a report already delivered is not affected. If you have consented, your e-mail address and, where applicable, your phone number remain stored until you withdraw your consent. A message to us is enough to withdraw it; we pass it on to SpotLens, and every e-mail from SpotLens also contains a way to unsubscribe.
We are joint controllers with ArrowTrade AG for the check (Art. 26 GDPR). We are the point of contact for exercising all your rights; you can equally contact ArrowTrade AG directly. To prevent large-scale misuse, the same submission limit applies as for the contact form (check value instead of a stored IP address, see above); in addition, your browser transmits the time between filling in and submitting the form, which is evaluated without any link to you and is not passed on to SpotLens. If JavaScript is switched off in your browser, a link at this point leads directly to spotlens.ai; the privacy notices there then apply.
Free tools under /tools
With the exceptions named below, the tools at /tools run entirely in your browser. What you enter or open there, such as an XRechnung, a password or the details on the planning sheet, does not leave your device and does not reach our server.
E-mail check (/tools/e-mail-check): when you check a domain, your browser sends that domain to our server. It looks up public DNS records and sends the result back. The domain and result are not logged. For follow-up checks, both are held in memory for up to five minutes without being linked to a visitor.
Speed test (/tools/speedtest): when you start the measurement, your browser loads test data from our server and sends test data back, around 200 MB at most per run. The evaluation takes place in your browser; measurement results are not stored.
Third-party check (/tools/drittanbieter-check): our server retrieves the page whose address you enter once, along with up to eight of its stylesheets, and sends you back the third-party services it finds. The address and result are not logged. For follow-up checks, both are held in memory for up to five minutes without being linked to a visitor. The operator of the page checked sees a request from our server, not from you.
AI crawler check (/tools/ki-crawler-check): when you enter a domain, your browser sends it to our server. It retrieves the robots.txt and llms.txt files from that domain, as well as the start of the home page, and sends the analysis back. The domain and result are not logged. For follow-up checks, both are held in memory for up to five minutes without being linked to a visitor. If you paste the text of a robots.txt file instead, it remains in your browser.
Link preview check (/tools/link-vorschau-check): the address you enter goes to our server. From there it retrieves the beginning of the page (2 MB at most) and its preview image and sends back the evaluation. The third-party website sees the address of our server, not yours. The address and result are not logged. For follow-up checks, both are held in memory for up to five minutes without being linked to a visitor. If you paste in the source code instead, it stays in your browser.
Gas calculator (/tools/gas-rechner): on loading, your browser asks our server for current network fees and prices; your entries are not transmitted in the process. Our server fetches these values no more than once a minute from public blockchain access points (PublicNode/Allnodes, dRPC, Offchain Labs, Optimism Foundation, Coinbase) and reads prices from Chainlink contracts. These providers see only our server, not you.
The following applies to these tools: as protection against misuse, the server forms an irreversible check value from your IP address, which our delivery service Cloudflare passes to it (HMAC with a key generated anew at every restart). It remembers only how many requests and how much data went through this check value in the last few minutes; after eleven minutes at the latest, the entry is deleted. IP address, domain, address checked and measured values do not end up in the log. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in a service that works and is protected from misuse).
Digital legacy planning sheet, e-mail signature generator and IT checklist for staff: if you wish, and only after you tick a box, your browser stores your entries in localStorage on your own device so that you can carry on later. If you untick the box or use the delete button, they are removed again. Export and import as a file also take place only on your device; nothing is transmitted to us.
Access by AI assistants: the tools can also be called through our MCP server at /mcp, for example by Claude or ChatGPT. The assistant then sends the entries to our server, which carries out the same calculation and returns the result without storing it. Our server likewise processes calls through the A2A endpoint at /a2a, through which agents use the same tools under the A2A protocol. What the assistant itself does with your entries is governed by its provider.
Local settings on your device
If you change the colour scheme in the footer or reduce motion, your browser remembers this choice in what is called localStorage, as two small entries on your own device. They contain no personal data, are not transmitted to us or to third parties and never leave your device. They are not cookies: nothing is sent to a server. You can delete the entries at any time through your browser's settings.
Consent and cookie settings
On your first visit we ask whether services that require consent may be loaded. As long as you have not agreed, this website loads no such service. This is technically enforced and not merely a promise: a service that requires consent is embedded only if consent has been given for it. What runs without consent is described above: delivery via Cloudflare including its insertions, and the spam check as soon as you type in the contact form.
You have three options: Decline (nothing is loaded), Settings (you choose individually) or Accept all. Decline and Accept are deliberately placed side by side with equal weight.
We store your decision not in a cookie but as one entry in your browser's local storage (key at-consent). It does not leave your device and is never sent to a server. The legal basis for the services you have approved is your consent under Art. 6(1)(a) GDPR.
Withdrawal at any time: you can change your choice through “Cookie settings” in the page footer. A withdrawal takes effect immediately; content already loaded is removed without your having to reload the page.
Appointment booking via Google Calendar
On the page Book an appointment we offer you the option of booking an available slot yourself. The calendar comes from Google (Google Calendar Appointment Scheduling). The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
The calendar is not loaded without your permission. As long as you have not consented, no connection to Google is made when you visit the page. Only when you expressly click “Load calendar from Google”, or if you have already consented earlier, does your browser load the calendar. In the process, data is transmitted to Google, in particular your IP address, details of your browser and device, and any cookies set by Google. A transfer to third countries cannot be ruled out.
The legal basis is your consent under Art. 6(1)(a) GDPR, which you give by clicking. We remember your decision in your browser's local storage (key at-consent, see the section “Consent and cookie settings”); it is not a cookie, and it never reaches our server. As long as consent is in place, the calendar on the appointment page loads without asking again; you can withdraw it at any time through “Cookie settings” in the footer, after which the calendar stays off again. If you do not click, nothing happens.
If you do not want to transmit any data to Google at all, arrange the appointment by phone on +49 3744 4399760. Through our contact form your browser loads nothing from Google, but the message ends up, like any e-mail, in our inbox at Google Workspace; see above under “Contacting us” for details. Further information on data processing at Google: policies.google.com/privacy.
Remote support
On the page Remote support we offer a small program to download that lets us help you on your screen once we have agreed this by phone. It is based on RustDesk 1.4.9, open-source software under the AGPL-3.0-or-later; we distribute a version built by us.
The file is on our own server. It is transferred only when you click the button; the same server log data arises as with any other visit to this website (see above). No third-party provider learns of this download.
So that two computers can find each other, the program connects to a relay server when it starts: our own, at fernwartung.aureum-tech.com, located in Nuremberg, Germany. No third-party provider is involved in the connection.
The following data arises there: the IP address of your device, its ID in the program, and the time and duration of the session. This information is kept in our server log and is deleted automatically after eight weeks. It is used for operation and troubleshooting only; it is not evaluated in any other way.
We run the server itself at netcup GmbH (Karlsruhe, data centre in Nuremberg). It is our processor under Art. 28 GDPR and sees encrypted traffic only. No transfer to a third country takes place.
The content of the session is additionally protected: the transmission is end-to-end encrypted. Your screen content is encrypted on your computer and decrypted only at our end; the relay server merely passes it on and could not read it even if we wanted it to.
The session itself only starts once you give us the ID and the one-time password that the program shows on your screen. During the session we see your screen content and, as far as you allow it, can operate the mouse and keyboard; you watch the whole time. When the program is closed, the session ends, the password expires, and nobody can reconnect without new details. We do not set up permanent remote access.
The legal basis is Art. 6(1)(b) GDPR (performance of the support contract). We process whatever data arises solely to solve your problem; we look only at what is needed for that. If you do not want remote support, we come to you on site or help by phone; call us on +49 3744 4399760.
Your rights
Under the GDPR, you have the following rights against us as the controller:
- Access to your stored data (Art. 15 GDPR)
- Rectification of inaccurate data (Art. 16 GDPR)
- Erasure (Art. 17 GDPR)
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR)
- Objection to processing (Art. 21 GDPR)
An informal message to [email protected] or a phone call on +49 3744 4399760 is enough. You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is the Saxon Data Protection and Transparency Commissioner (Sächsische Datenschutz- und Transparenzbeauftragte) in Dresden.
What we count on our server
This website embeds neither analytics and statistics services from third-party providers nor advertising networks or their tracking pixels. It does not load external fonts, maps or videos either. It embeds only two things from third-party providers, both described above: the booking calendar, solely after your consent, and the spam check in the contact form, only once you start typing there. Everything is delivered via Cloudflare, see above.
We do the counting ourselves, on our own server and at the moment it delivers a page, even if your browser already knows the page and merely asks the server whether it has changed. Nothing is stored in your browser for this, and no counting script runs. The counting itself sets no cookie and does not make your browser send us anything extra. Only two cookies are read, and they exist solely at your express request: the objection cookie, if you object below, and, on our team's devices, the login cookie for the internal area. Both only ensure that a request is not counted. When a request arrives, the server sees in any case which page your browser is asking for and, if your browser sends it, which page the request came from. It immediately reduces this information to one of four values: the path of one of our own pages, “search engine”, “other website” or “no referrer”. It discards the address of a third-party website and any search term; neither is stored or logged. The server tells from the technical details of the request whether it comes from a browser that displays the page: search engine robots, checking tools, pages loaded in advance and requests from devices logged in to our internal area are not counted.
Only totals are stored, in one file on our server: per day, page and origin, the number of views; per month, page, weekday and three-hour block, the number of views; per day, page and form type, the number of enquiries submitted; per day, ad campaign and advertised page, the number of ad clicks described below; and per month, weekday and three-hour block, the number of enquiries and ad clicks for the whole website. We do not store individual views, their exact time or sequence, IP addresses, browser identifiers or any other identifier. These totals are evaluated only internally and only as totals: which pages are viewed how often, from which kind of source (for our own pages: from which one), and on which weekdays and at which times of day. We merged the counting data from before 15 September 2026, which at the time consisted of one line per view with page and time, into daily totals in a one-off step and deleted the individual lines.
If you submit a form, the server counts that on this day an enquiry of this type (contact form, e-mail form on the PC help page or started website check) arrived via this page; it takes the page from the request itself, not from your entries, and stores nothing of what you enter. It records visits to our printed short links (addresses under /qr/…) and the start of the website check as individual lines with the respective identifier and the time rounded to the full hour, without further details.
We place ads with Google. Some ads lead to dedicated entry addresses on this website (addresses under /a/…). When you click, your browser goes through this address and is forwarded from there to the advertised page. In doing so, the server counts the campaign, the advertised page and the day, and also the click in the overview by weekday and time of day for the whole website (see above). It recognises the campaign by the entry address that we set up ourselves, not by an identifier from Google.
The server then counts the view of the advertised page like any other, that is, by page, origin and day. A click through an entry address is therefore counted twice: once as an ad click, once as a page view. If an ad leads directly to a page, only that page view is counted. Identifiers that Google appends to the addresses are not evaluated by the server, are not passed on, and are neither stored nor logged.
Retention period. We delete the daily totals and the weekday grids after 90 days at the latest; what remains are monthly totals per page and origin, per page and form type, and per ad campaign and advertised page, which we delete after 13 months at the latest. We likewise delete the lines on short-link visits and on the start of the website check after 13 months at the latest. Deletion runs automatically once a day.
Legal basis. Nothing is stored on your device for the counting. Only the two cookies named above are read, and only so that a request is not counted. Both exist only at express request: the objection cookie if you object, the login cookie when someone from our team logs in to the internal area. For this reason no consent under § 25 TDDDG is needed. Insofar as personal data is processed on a request (for the moment of delivery the server knows your browser's request), we base the counting on Art. 6(1)(f) GDPR. Our legitimate interest: detecting malfunctions, placing frequently used content better and judging the effect of our own ads. We do not combine the counting data with enquiries, calls or other data.
Right to object. You can object to this counting at any time (Art. 21 GDPR), directly here, without a message to us: the first button sets a cookie with which our server no longer counts your requests; the second reverses that. Whichever button you pressed last applies; afterwards you are brought back to this spot. Both work without JavaScript.
If your browser sends the Global Privacy Control or Do Not Track signal, we also treat that as an objection and do not count the request; no cookie is needed in that case. Because the counting works without an identifier, we can neither recognise your earlier views in the totals nor remove them. You can also object informally at any time, by the contact routes under “Your rights”; we reply to such an objection and keep a record of it.
In addition, the page measures itself: loading time and page weight are determined and displayed solely in your browser, transmitted nowhere and not stored.
Parts list of this website
So that you do not have to take our word for it but can check: this table lists every file that this website consists of. Every item is on our own server and is delivered via Cloudflare, which adds scripts of its own at the edge; these are listed above under “Delivery via Cloudflare”.
| Item | Part | Type | Measured at build time |
|---|---|---|---|
| 01 | index.html | Document | ≈ 29 kB |
| 02 | styles.css | Stylesheet | ≈ 20 kB |
| 03 | scripts.js | Script | ≈ 13 kB |
| 04 | archivo-variable.woff2 | Font | ≈ 58 kB |
| 05 | ibm-plex-mono.woff2 | Font | ≈ 30 kB |
| 06 | favicon.svg | Image | < 1 kB |
With JavaScript enabled, you can check this live: footer → Parts list for this page.