Privacy Policy
App and pages: OnDevice OCR Business · Provider: Christian Schröder · This translation is provided for convenience; the German version prevails.
Controller
The party responsible for processing personal data in connection with the App, these pages, and license delivery is:
Christian Schröder
Marktstraße 242
47798 Krefeld
Germany
Email: [email protected]
1. General
This policy informs you about the nature, scope, and purpose of the collection and use of personal data when you use OnDevice OCR Business and visit these pages.
2. App: local processing and no telemetry
OnDevice OCR Business contains no tracking and no telemetry. Documents and recognized text are not transmitted to us automatically.
Local processing: All documents (PDFs, images) are processed exclusively on your device. Text recognition is performed by Apple’s Vision components directly on your Mac. For file naming, you can additionally use Apple’s on-device language model on Macs with Apple Intelligence (macOS 26 or later). The feature only runs if you select it in a template. Processing takes place on your Mac; nothing is transmitted to us. For the optional Ollama connection, see section 8.
No tracking: We do not use any analytics tools in the App.
No transmission of content: Neither your documents nor the recognized text, file names, or your folder structure are transmitted by the App to us or to third parties; for the optional Ollama connection, see section 8.
Processing history: The App keeps a history of processed documents on your Mac, including file names, time, and result. It stays on your Mac. You set the retention period in the App and can delete the history there at any time.
Local technical diagnostics: To display the operating status and to help with troubleshooting, the App keeps a rotating diagnostic log on your Mac. In particular, it may contain timestamps, types of operations, technical identifiers, document and page counts, run times, results, and error states. The local logs may also contain file and folder names as well as paths. They remain in the App’s data folder on your Mac, are overwritten automatically once they reach the intended size, and can be deleted by you in the App settings.
Voluntary diagnostic export: The App does not transmit the diagnostic log automatically. For a support request, you can create a diagnostic file yourself and then send it to us voluntarily. Before the file is saved, file and folder names, paths, and server names are replaced with placeholders; document contents are not included. The exported file still contains technical information such as timestamps, counters, states, and pseudonymous identifiers. If you send us such a file, we use it exclusively to handle your support request. The legal basis is Art. 6(1)(b) or (f) GDPR. We delete the file once the request has been resolved.
Crash reports: If you have allowed macOS to share crash data with app developers in System Settings, Apple provides us with crash reports for the version obtained through the Mac App Store. They contain technical information about the crash, such as app version, macOS version, and device type, but no document contents. You can change this setting in macOS at any time.
Update check: The version you obtain directly from us uses the update service Sparkle to check whether a newer version is available. This establishes a connection to our server, which involves technically necessary connection data (IP address, time, requested file, app and system version). The legal basis is our legitimate interest in delivering updates securely pursuant to Art. 6(1)(f) GDPR. Your documents are not transmitted in the process. You can turn off the automatic check for updates in the App’s settings. The version obtained through the Mac App Store is updated by Apple; we do not receive any data in that case.
Price display: As long as the directly obtained version has not been unlocked, it may contact our license service to display the purchase price for your country. No documents, recognized text, or diagnostic information are transmitted. As with any internet connection, technically necessary connection data is involved, in particular IP address, time, and requested address; Cloudflare processes this data on our behalf (see section 4). From the IP address, Cloudflare determines the country the request comes from. Our license service queries the price from Paddle (see section 6) using only this country code; we do not pass your IP address or any other information about you on to Paddle. If no country can be determined, the App shows the standard price. We cache the price per country for up to ten minutes so that not every display triggers a new query to Paddle; only the amount and currency are stored, no information about you. The legal basis is our legitimate interest in displaying an accurate price, including the taxes and currency applicable in your country, pursuant to Art. 6(1)(f) GDPR.
Mac App Store: In the version obtained through the Mac App Store, price display and purchase are handled by Apple. We do not receive any personal data of purchasers. Apple’s privacy policy applies to processing by Apple.
3. License file
The full version is unlocked with a license file. It contains the name of the licensed company or person, the email address provided at purchase, a license number, the date of issue and – for licenses covering several seats – the number of seats. This file is verified on your Mac; the App does not report to us where or when it is used.
4. Hosting and license service via Cloudflare
These pages are hosted and delivered using services of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA (“Cloudflare”). When you visit them, Cloudflare may process technically necessary connection data: IP address, requested address, date and time of the request, browser and device information, referrer information, and other technical details required for delivery and protection.
The purpose is the availability, speed, and protection of the pages. The legal basis is our legitimate interest pursuant to Art. 6(1)(f) GDPR. The connection data is processed only for as long as necessary for this purpose and is then deleted.
Cloudflare may process data outside the European Union, including in the United States. Such transfers are safeguarded by the European Commission’s Standard Contractual Clauses and, where applicable, by Cloudflare’s certification under the EU–U.S. Data Privacy Framework. Details: Cloudflare’s privacy policy and Cloudflare’s data processing addendum.
Our license service, which receives purchase notifications and issues license files, and its database are also operated at Cloudflare. Cloudflare acts as a processor on our behalf; the preceding paragraph applies to transfers to third countries.
The program file (DMG) available for download is also stored at Cloudflare and delivered via download.ondeviceocr.com. The update check of the version obtained directly from us and the download of updates (Section 2) also run through Cloudflare. Cloudflare acts as a processor on our behalf. The information at the beginning of this section on the legal basis, retention, and transfers to third countries applies accordingly to the connection data involved; the purpose here is to provide the program file and its updates.
5. Audience measurement
We use Cloudflare Web Analytics to understand, in aggregated form, how these pages are used and how fast they load. No cookies are set, no persistent user identifiers are created, and neither localStorage nor sessionStorage nor IndexedDB is used. The data processed is the page visited, date and time, referrer information, the approximate country, browser and device type, and technical performance values. According to Cloudflare, IP addresses are not used to identify individual visitors and are not stored in the analytics data. The legal basis is our legitimate interest in a secure, fast, and user-friendly offering pursuant to Art. 6(1)(f) GDPR. You may object to this processing on grounds relating to your particular situation pursuant to Art. 21 GDPR.
In addition, we count page views in our own statistics. For each view we store the page visited, the country, the referring website (domain only), and the type of browser. The country is derived from the IP address at the time of the request; the IP address itself is not stored, no cookies are set, and individual visitors cannot be identified. Entries are deleted after 24 months. The legal basis is our legitimate interest in an overview of how our pages are used, Art. 6(1)(f) GDPR. You may object to this processing under Art. 21 GDPR.
We count clicks on the Mac App Store buttons and the buttons to download the program file (DMG) in the same way; instead of the domain only, we store the address of the page without additional parameters, as well as the position on the page where the click occurred and the page language. On the English and German homepages, we are also trying out two designs. Which one is shown depends solely on the time of day: all visitors within the same half hour see the same design. No cookies are set, no identifiers are assigned, and no additional data is stored for this; which design belonged to a page view is determined in the analysis solely from its time.
If you reach these pages through an ad, for example on Google, we recognize this from an addition to the address. We then store only the information “accessed via an ad: yes/no” together with the page view or the click on a button to the Mac App Store or to the download. The addition itself is not stored; no cookies are set, no scripts from Google are loaded, and we do not transmit any data to Google in the process. The purpose is to assess whether our ads are worthwhile. The legal basis is our legitimate interest in this, Art. 6(1)(f) GDPR. Like the rest of the statistics, the entries are deleted after 24 months. You may object to this processing under Art. 21 GDPR.
We ourselves do not use advertising trackers, profiling, or cookie-based analytics tools. Section 6 applies to the purchase page, where program components from Paddle are loaded. There are no user accounts, contact forms, or newsletters here.
6. Purchase and license delivery (Paddle, Resend)
Purchase page: Merely opening the purchase page does not load anything from Paddle. Only when you click the buy button (“Buy Now”) or open the page via a payment link from Paddle are program components from Paddle loaded so that the checkout window can be displayed; Paddle also includes its ProfitWell service of its own accord, which we do not use for analytics. Your IP address is transmitted to Paddle. Paddle sets a cookie (__cf_bm, lifetime 30 minutes) that wards off automated access and is strictly necessary for the purchase process (Section 25(2) no. 2 TDDDG). Otherwise, the legal basis is the performance of pre-contractual measures at your request, Art. 6(1)(b) GDPR. The checkout window itself is provided by Paddle; Paddle’s privacy policy applies to the cookies set and data processed there.
Purchase: If you buy a license directly through these pages, our payment provider Paddle.com Market Ltd, Judd House, 18–29 Mora Street, London EC1V 8BT, United Kingdom (“Paddle”), processes the purchase as merchant of record. Paddle acts as the seller, processes the data required for the transaction, such as name, email address, billing address, VAT ID where applicable, and payment data, and issues the invoice. Paddle processes this data as an independent controller. The European Commission has adopted an adequacy decision for the United Kingdom; where Paddle transfers data to other third countries, Paddle states that it relies on standard contractual clauses. We receive from Paddle the information needed to provide and manage your license (such as name, email address, and order data), but no complete payment data. The legal basis is the performance of a contract, Art. 6(1)(b) GDPR. Details: Paddle’s privacy policy.
Our storage: For each purchase we store the email address, the company name and the name of the purchasing person, the license number, the number of seats, Paddle’s purchase identifier, the language, the status of license delivery, and the issued license file. The legal basis is performance of the license agreement, Art. 6(1)(b) GDPR, and our legitimate interest in handling support requests and documenting issued licenses, Art. 6(1)(f) GDPR. We keep this information for as long as the license exists, so that we can resend your license file at any time and verify your entitlement for support requests or a transfer of the license. On request we delete the entry earlier; we can then no longer resend the license file. Where individual details are subject to statutory retention obligations, we keep them until those periods expire.
The purchase notification sent by Paddle also contains further order and payment details, such as amounts, taxes, currency, invoice number, and payment method, and for card payments also the card type, the last four digits, the expiry date, and the cardholder’s name. We store it for troubleshooting license delivery and delete its content 30 days after receipt, once the transaction is complete.
If you request your license file again, we limit the number of requests per email address and per IP address. The counters used for this do not contain addresses in plain text, only irreversible hash values. They are no longer taken into account after one hour and are then deleted during the next cleanup.
The details requested by Paddle are required for the purchase; without them, no license can be issued. No automated decision-making, including profiling, takes place.
License delivery: After a successful purchase, your license file is sent to you by email. For this we use the email delivery service Resend of Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA (“Resend”), which acts as a processor on our behalf. The data processed are your name, your email address, the text of the email, and the license file. If a problem occurs while issuing or sending the license, we receive an internal notice via the same service containing your email address and the license number. The legal basis is the performance of a contract, Art. 6(1)(b) GDPR. This involves a transfer of data to the United States; it is safeguarded by Resend’s certification under the EU–U.S. Data Privacy Framework and by the Standard Contractual Clauses in Resend’s data processing agreement. Details: Resend’s privacy policy and Resend’s data processing agreement.
7. Access to files in the App
The App accesses the files you hand over to it: documents you load by drag and drop or through the file dialog, and the folders you explicitly set up for monitoring — including on network shares. The App itself does not transfer these files off your device or out of your network; for the optional Ollama connection, see section 8.
If you use the App to process personal data of third parties, such as your customers’ documents, you are the controller for that processing within the meaning of the GDPR. We do not receive this data and are therefore not a processor in this respect.
8. Use with AI agents and automation tools
OnDevice OCR Business itself does not upload any documents, recognized text, or file names and does not automatically transmit any usage or diagnostic information to us. If you use external AI agents or automation tools with access to the App or to folders containing your documents, you decide which files and data these tools may access. Any processing by such tools is outside our control and is subject to the respective provider and to your configuration of the tool.
Ollama (optional): You can connect the App to Ollama, a separate program that you install yourself. You set up the connection in the App under “Integration”; it is not set up by default. Only after you agree does the App pass text and, where applicable, image excerpts of the areas you have marked for file naming and set to “Read by AI”, together with your instruction for that area, to Ollama on your Mac (address 127.0.0.1). This also applies to documents the App processes in the background in monitored folders. The App does not send anything to the internet or to us. If you choose a cloud model in Ollama, Ollama sends this data to Ollama’s cloud service through your Ollama account; Ollama’s terms and privacy policy apply. If the marked areas contain personal data, for example of your customers, you as the controller (section 7) decide whether you may pass this data to a cloud service and which agreements you need with the provider for this.
9. Disclosure to third parties
The App does not pass your documents, recognized text, or file names on to third parties and contains no tracking or telemetry. Section 8 describes what is passed to Ollama if you use the optional Ollama connection. Technically necessary connection data for updates and the price display is described in section 2. For these pages, Cloudflare processes technically necessary connection data as described above; section 6 applies to purchases and license delivery.
10. Contact by email
If you write to us by email – including via the App’s feedback function, which merely opens your email program – we process your email address and the content of your message in order to handle the request. The legal basis is Art. 6(1)(b) GDPR where your purchase or license is concerned, otherwise our legitimate interest in responding, Art. 6(1)(f) GDPR. We delete messages when they are no longer needed, at the latest after three years. Our mailbox is hosted by Apple (iCloud Mail, Apple Distribution International Ltd., Ireland).
11. Your rights
Subject to the applicable legal requirements, you have the right to request access to your personal data as well as its rectification, erasure, restriction of processing, and data portability. Where we process data on the basis of Art. 6(1)(f) GDPR, you may object to this processing at any time on grounds relating to your particular situation. An informal email is sufficient. In addition, you have the right to lodge a complaint with a data protection supervisory authority. The competent supervisory authority is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia.
12. Contact
If you have any questions about data protection, please contact Christian Schröder, [email protected].
Last updated: October 14, 2026