The short version: no cookies, no tracking, no analytics, nothing loaded from third parties. The app has no accounts and sends nothing to me. What the contact form does collect is listed below.
Klaus Mack Software, Nyvej 14, 6340 Kruså, Denmark.
Email: info@klausmack-software.com
Full details in the legal notice.
These pages are static HTML. They contain no analytics, no tracking pixels and no advertising, and they set no cookies. The typefaces are the ones already on your system — nothing is fetched from Google Fonts or any other third party.
One thing is stored, and in your browser rather than with me: the fact that you have seen the cookie notice, so that it stays away for 30 days. All that is kept is a timestamp in your browser's local storage — not a cookie, and nothing that travels to a server. You can clear it in your browser settings at any time; the notice then comes back.
The start page carries a visitor counter at the bottom. What the server keeps for it is a single number — no IP address, no time, no history, nothing that could be traced back to a visit. So that reloading does not count again, your browser remembers today's date in local storage; that is not a cookie either. The number is therefore an indication, not a measurement.
What does happen is what happens on every web server: the hosting provider writes an access log. It contains the IP address of the requesting device, the date and time, the page requested, the referring page and the browser identification. This is technically necessary to deliver the page and to recognise attacks. The legal basis is Art. 6(1)(f) GDPR — legitimate interest in operating the site securely. These logs are not merged with anything else and are not used to identify anyone.
If you use the contact form, the following is processed: your name, your email address, the topic you picked, your message and, if you attach one, a screenshot or log file. All of it is sent to me by email so that I can answer you. Legal basis: Art. 6(1)(f) GDPR — my legitimate interest in answering enquiries, and Art. 6(1)(b) where the enquiry concerns the app itself.
Two things worth knowing. First, there is no log file. Your message is delivered to me and stored nowhere else — no second copy with your name and address sitting on the web space. Second, a log file you attach may contain your server names and file names — have a look at it before you send it.
The arithmetic question that keeps spam out works without a cookie: the question comes with a checksum that the server recalculates when you submit. It has nothing to remember and nothing to store.
Your message stays in my mailbox as long as I need it for the matter, or longer if commercial retention rules apply. There is no ticket system and no CRM behind it. Nothing from the form is used for advertising and nothing is passed on.
The button on the start page leads to TestFlight, a service run by Apple. From that point on, Apple's privacy policy applies, not mine. Whether you install the app, on which device and with which Apple Account is handled entirely by Apple.
I do not collect email addresses for the beta. There is no sign-up form — the contact form above is for questions, not for joining. Testers who join through the public link stay anonymous to me: App Store Connect does not show me their names or email addresses.
If you send feedback from inside TestFlight, I receive what you wrote, any screenshot you attached, plus the device model and system version. That comes from Apple and is used for one purpose: fixing the problem. Apple's privacy policy: apple.com/legal/privacy
FileFerry is a file transfer program. It talks to your servers, not to mine. Concretely:
In other words: I have no way of learning which servers you connect to or which files you move.
Under the GDPR you have the right to information about data concerning you, and to correction, erasure and restriction of processing. If you have written to me through the contact form, that means your message and my reply — ask and it goes.
You may also complain to a supervisory authority. The competent one for me is the Danish Data Protection Agency (Datatilsynet), datatilsynet.dk.
Last updated: 5 August 2026