Privacy Policy
Timo Zurhove · Last updated: November 17, 2026 · Deutsche Fassung
This policy covers the apps I publish on the App Store. The first part applies to all of them. After it, each app has a section of its own: what the app stores, what it sends and to whom, and how you can stop it and delete your data.
Who is responsible
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Timo Zurhove
Imprint
Email: info@tz-develop.de
Write to this address with any question about this policy or about your data.
Downloads through the App Store
My apps are distributed through Apple's App Store. Downloads, purchases and payments are handled by Apple, on its own responsibility and under Apple's privacy policy (apple.com/legal/privacy), and through the App Store I do not receive your name, your Apple Account or your payment details. Apple gives me only the reports it gives every developer: aggregated download and sales figures and, if you have chosen to share analytics with app developers in your device's settings, usage statistics and crash reports that do not identify you.
Support requests
If you write to me, about support or anything else, I use your message and your email address only to answer you. I delete them once they are no longer needed for that, unless the law requires me to keep them longer.
Legal basis: my legitimate interest in answering your message (Art. 6(1)(f) GDPR). If your message concerns a contract with me, such as the license for one of my apps, or one you want to enter into, it is Art. 6(1)(b) GDPR. Where the law requires me to keep a message, the legal basis for keeping it is Art. 6(1)(c) GDPR.
Your rights
Under the GDPR, you have the right to ask which personal data about you I hold (Art. 15), to have it corrected (Art. 16) or deleted (Art. 17), to have its processing restricted (Art. 18), and to receive it in a common, machine-readable format (Art. 20). You can withdraw a consent you have given at any time, with effect for the future (Art. 7(3)). Write to info@tz-develop.de. What each app stores on your device, and how to delete it, is described in that app's section below.
Right to object: where I process your data on the basis of my legitimate interests (Art. 6(1)(f) GDPR), you can object to that processing at any time, on grounds relating to your particular situation (Art. 21 GDPR).
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR).
Changes to this policy
If this policy changes, I publish the new version on this page and change the date at the top.
RAG Desk
RAG Desk is a Mac app that indexes folders of documents you choose, so that you can search them and ask questions about them. This section describes what it does with your data. Who is responsible, how to reach me and your rights are at the top of this policy.
In short
- RAG Desk has no account, no analytics, no advertising and no server of its own. The app sends me nothing: not your documents, not your searches, no usage data. The only reports I get are Apple's, described under Downloads through the App Store.
- Your documents are read on your Mac, and the index RAG Desk builds is stored on your Mac.
- To create embeddings and written answers, RAG Desk sends text to OpenAI using your own OpenAI API key, and only after you have allowed it.
Data stored on your Mac
- Your data pools: their names, settings and folders, including the macOS security-scoped bookmarks that let RAG Desk reopen those folders after a restart.
- Each pool's index: the text extracted from your documents, split into passages, the embeddings of those passages, and each file's path, size and modification date, which are used to update the index when files change.
- Your settings, such as the text size, search options and whether you have allowed sending content to OpenAI.
- Your OpenAI API key, which is stored in the macOS Keychain.
RAG Desk only reads the folders you add. It never changes or deletes your documents. Apart from what RAG Desk sends to OpenAI, described below, none of this data leaves your Mac, and I have no access to it.
Data sent to OpenAI
RAG Desk uses the OpenAI API for embeddings and text generation. Requests go directly from your Mac to OpenAI, authenticated with your API key. They do not pass through any server of mine. What is sent, and when:
- Indexing: the text of the documents in a pool, to create embeddings. Whole documents are also sent to an OpenAI language model when the pool uses Semantic chunking or Contextual Retrieval. File names are sent with the text when “Embed each chunk with its filename” is switched on.
- Searching by Meaning or Hybrid: the text you search for.
- Written answers (“System Prompt” switched on): your question, your instructions for the pool, and the passages found, each with its file name and folder.
Nothing is sent for keyword searches without an answer. Scanned PDFs are read with Apple's on-device text recognition; the recognized text is then indexed like any other text.
Legal basis: RAG Desk sends this data only with your consent (Art. 6(1)(a) GDPR), which you give in the app before anything is sent and can withdraw at any time; see “Your consent” below.
OpenAI is the only third party RAG Desk sends data to. OpenAI processes it under your own agreement with OpenAI, and its terms for the API protect your data at least as well as this policy does: OpenAI does not use data sent through its API to train its models unless you have chosen to share it with OpenAI, and it keeps the data only for a limited period. What OpenAI keeps, and for how long, is set out in its policies: openai.com/policies.
Transfer to the USA
OpenAI is headquartered in the USA and processes the data there as well. For transfers of personal data from the EU to the USA, OpenAI relies on the standard contractual clauses adopted by the European Commission (Art. 46(2)(c) GDPR). Even so, US authorities may be able to access the data.
Your consent
RAG Desk asks for your consent before it sends anything for the first time, and lists what it sends. You can withdraw your consent at any time in Settings (⌘,) › Privacy, by switching off “Allow sending content to OpenAI”; RAG Desk then asks again before the next action that would send anything. Withdrawing it does not affect the lawfulness of what was sent before (Art. 7(3) GDPR). If a later version of RAG Desk sends something it does not send today, it asks for your consent again.
Deleting your data
RAG Desk sends me nothing, so I hold no data from it. Everything it stores stays on your Mac until you delete it:
- Deleting a pool deletes its index.
- “Remove” in Settings deletes your API key from the Keychain. Do this before you delete the app.
- Then delete the app. macOS may keep the app's data folder,
~/Library/Containers/de.develop.tz.ragdesk(Finder may show it as “RAG Desk”), which holds your pools, their indexes and your settings. If it is still there, delete it as well.
What you have sent to OpenAI is held by OpenAI under your account. To delete it, use the controls of your OpenAI account or contact OpenAI.
FTP-Client
FTP-Client is a Mac app that transfers files between your Mac and the FTP, FTPS and SFTP servers you choose. This section describes what it does with your data. Who is responsible, how to reach me and your rights are at the top of this policy.
In short
- FTP-Client has no account, no analytics, no advertising and no server of its own. The app sends me nothing: not your files, not your logins, not the servers you use, no usage data. The only reports I get are Apple's, described under Downloads through the App Store.
- Your logins and files go only to the servers you connect to – encrypted, unless you choose plain FTP yourself.
- Your saved servers and settings stay on your Mac. Passwords are kept in the macOS Keychain only if you switch that on.
Data stored on your Mac
- Your saved servers: name, server address, port, protocol, user name, whether you log in anonymously and whether the password is saved, the SHA-256 fingerprint of a certificate or SSH host key you chose to trust, and for SFTP the name of the private key file you chose, with a macOS security-scoped bookmark that lets FTP-Client read that file again when you connect.
- The three servers you logged in to last, listed below Quick Connect: for a saved server a reference to it and the time of the login, for a Quick Connect server its address, port, protocol, user name and the time. Never passwords.
- The folder shown on the left: security-scoped bookmarks of the folders you chose (and of Documents, if you opened it there), the path below them, and whether hidden files are shown.
- Passwords and key passphrases, only for saved servers where you switched on “Save password in Keychain” (off by default): in the macOS Keychain on this Mac, not synced to iCloud.
Other passwords, passphrases and one-time codes are kept in memory only while they are needed to log in. FTP-Client reads the names, sizes and dates of the files in the folders you open, to show them. Private key files are read when you connect; they are never copied and never leave your Mac.
Data sent to the servers you connect to
FTP-Client connects only to the servers you enter, and only when you connect or start a transfer. To each of them it sends your user name and password – or, for SFTP with a key, the public key and a signature made with your private key –, your answers when the server asks further login questions, such as a one-time code, and the files you upload. It receives the server's folder listings and the files you download. Nothing passes through a server of mine.
With FTPS and SFTP, all of this is encrypted on the way. New servers start with FTPS. With plain FTP, which you have to choose yourself, your password and files travel unencrypted, and the app warns you about it. What a server does with your data is up to whoever runs it.
Deleting your data
FTP-Client sends me nothing, so I hold no data from it. Everything it stores stays on your Mac until you delete it:
- Deleting a saved server (right-click it in the sidebar, “Delete Server…”) deletes its settings and its saved password.
- “Forget Certificate” and “Forget Host Key” in a server's settings withdraw a trust you gave. Right-click an entry of the Recent list to remove it or to clear the list.
- Then delete the app. macOS may keep the app's data folder,
~/Library/Containers/de.develop.tz.ftpclient(Finder may show it as “FTP-Client”), which holds your saved servers, the Recent list and your settings. If it is still there, delete it as well. Passwords of servers you didn't delete in the app stay in your keychain as items named “FTP-Client: user@server”; delete them with Keychain Access.
Files you uploaded stay on the servers. Delete them there, or ask whoever runs the server.
DB-Client
DB-Client is a Mac app for working with PostgreSQL, MySQL, MariaDB and Microsoft SQL Server databases. This section describes what it does with your data. Who is responsible, how to reach me and your rights are at the top of this policy.
In short
- DB-Client has no account, no analytics, no advertising and no tracking, and it contains no third-party code that sends data anywhere. The app sends me nothing. The only reports I get are Apple's, described under Downloads through the App Store.
- It connects only to the database servers you add, directly from your Mac.
- Your connections, saved queries and settings stay on your Mac, and passwords are kept in the macOS Keychain.
Connections to your database servers
The app connects only to the database servers you add, directly from your Mac. The queries you run and the data they return travel between your Mac and those servers and are never sent to me or to anyone else. How your database servers handle that data is up to whoever operates them.
Data stored on your Mac
- Connection details (name, engine, host, port, database, user name and TLS settings, including a CA certificate you choose), in a file inside the app's own sandbox container.
- Saved queries, the SQL text you save with ⌘S, in a file beside it.
- Passwords, in the macOS Keychain, never in that file.
- Settings such as appearance and font size, in the app's preferences.
- A diagnostics log, only while you have switched on “Diagnostic Logging” in the app menu. It can contain technical details of your connections and the statements you run. It stays inside the app's container until you clear it, and it is sent to no one unless you choose to send it to me yourself.
Exported files are written only to the location you choose in the save panel. Files you import are read only when you pick them in the open panel, and only to send their rows to the table you chose; the app keeps no copy.
Deleting your data
DB-Client sends me nothing, so I hold no data from it. Everything it stores stays on your Mac until you delete it:
- Deleting a connection deletes its saved queries.
- Deleting the app removes its container with the connection and saved-query files, the settings and the diagnostics log. If macOS keeps the app's data folder,
~/Library/Containers/de.develop.tz.dbclient, delete it as well. - Saved passwords can be removed with Keychain Access.
Data on your database servers stays there. Delete it there, or ask whoever runs the server.
WiFi QR Code
WiFi QR Code is an iPhone app that turns the name and password of a WiFi network into a QR code, which your guests scan to join the network. This section describes what it does with your data. Who is responsible, how to reach me and your rights are at the top of this policy.
In short
- WiFi QR Code has no account and no server of its own. The app sends me nothing: not your network names, not your passwords, no usage data. The only reports I get are Apple's, described under Downloads through the App Store.
- Your network names and passwords never leave your iPhone, unless you share or print a code yourself.
- The app shows a banner ad from Google AdMob. The ads are never personalized, and the app does not track you. In the EEA, the UK and Switzerland, Google asks for your consent first.
- If you bought one of the earlier paid versions, the app shows no ads and never starts Google's ad code.
Data stored on your iPhone
- Your saved networks: the networks whose code you saved, shared or showed to guests, with their name, security type, whether the network is hidden, and when you last used it.
- Their passwords, in the iOS Keychain on this iPhone. They are not synced to iCloud Keychain and not restored to another device.
- Whether you bought the app while it was paid (see below), so that the app doesn't have to ask the App Store again.
The network you are entering, the photo you choose as a logo and your style settings are kept in memory only, until you close the app. A logo photo is chosen with the system photo picker, so the app sees only that one photo. Codes you save are added to your photo library; the app can add photos but cannot read your library. When you copy a password on the guest card, it stays on this iPhone's clipboard, is not shared with your other devices, and is removed after two minutes.
"Use current" and your location
iOS tells an app the name of the WiFi network you are connected to only if the app has access to your precise location. WiFi QR Code therefore asks for location access the first time you tap "Use current", and only then. The app reads the network's name and security type and nothing else: it never reads, stores or shares your location. You can turn location access off at any time under Settings › Privacy & Security › Location Services › WiFi QR Code, and type the network name yourself.
Ads from Google AdMob
To pay for the app, WiFi QR Code shows a small banner ad. It uses Google AdMob, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (for users in the EEA and Switzerland), and of Google LLC, USA, everywhere else.
- Consent. In the EEA, the UK and Switzerland, the app shows Google's consent form before any ad is requested. Ads are only requested once Google's consent tool allows it. You can change or withdraw your choice at any time under Style › Ad Privacy Settings.
- No personalized ads, no tracking. Every ad request asks for non-personalized ads. The app does not ask for permission to track you, so it cannot read your device's advertising identifier, and it does not combine data with other companies' apps or websites for advertising.
- What Google receives. When the ad code runs, Google's SDK sends Google data it needs to deliver ads, measure them and prevent fraud, such as your IP address (from which Google estimates a rough location), device and app information, an identifier for this app on your device, and how you interact with the ads. Google describes this in its data disclosure for the Google Mobile Ads SDK and in How Google uses information from sites or apps that use its services. Google may process this data in the USA.
- Your network names and passwords are never shared with Google.
- The legal basis is your consent (Art. 6(1)(a) GDPR, and § 25(1) TDDDG for access to your device) where Google's consent form is shown, and otherwise my legitimate interest in financing the app with ads (Art. 6(1)(f) GDPR).
When no ad from Google is available, the banner shows an ad for one of my own apps instead. These ads are part of the app and send nothing. Tapping one opens the app's page in the App Store, which is Apple's service.
Buyers of the earlier paid versions
WiFi QR Code was a paid app until version 1.2. To find out whether you bought it then, the app asks Apple's App Store, through StoreKit, for the original purchase of the app on your Apple Account. Only the result, "bought while paid" or not, is stored on your iPhone. I receive nothing from this check.
Deleting your data
WiFi QR Code sends me nothing, so I hold no data from it. Everything it stores stays on your iPhone until you delete it:
- In the list of saved networks (the clock button), swipe left on a network to delete it and its password.
- Then delete the app. iOS may keep Keychain items of a deleted app, so delete your saved networks in the app first.
- Codes you saved to Photos, shared or printed stay where you put them. Anyone who scans such a code can read the network's password.
What Google stores about ad requests is held by Google; see Google's privacy policy at policies.google.com/privacy.