BookletMaker

Privacy

Last updated: 14 October 2026

BookletMaker is designed around the principle that your documents are yours and should never leave your devices. This page describes exactly what data the app touches and what it does with it.

Data we don't collect

What runs on your device

All imposition, OCR, find & replace, annotation, and export operations are performed locally using Apple's PDFKit, Vision, and Core Graphics frameworks. Output PDFs and exported images stay in the location you choose via the system file picker.

Saved presets

Print-setting presets you save in BookletMaker (My Presets) are stored only on your device, in BookletMaker’s application data. They are not sent to us and are not synced through iCloud. A preset holds print settings and the name you give it, never document content.

Crash logs

If you opt in to share diagnostics with Apple via Settings → Privacy & Security, Apple may collect crash reports for BookletMaker like any other app. Mobile Alchemy receives these reports anonymized via App Store Connect to fix bugs.

If BookletMaker crashes, the Mac, iPhone and iPad apps also send a crash report to our own server (api.bookletmaker.app) using Apple’s MetricKit, at most once a day. A report contains the app version and build, the system version, the type of device (Mac, iPhone or iPad) and its processor, the technical kind of crash (exception type, signal and termination reason), and the call stacks at the moment of the crash: only the names of the program libraries, their build IDs and the positions inside them, which is what we need to find the faulty code. If the crash was caused by a system exception, the report also holds the exception’s name and its message template, with file paths, web addresses, e-mail addresses and long numbers removed. A crash report contains no personal data, no document contents or file names, nothing you typed, no install ID, and no device name or model. Your IP address is not stored with it (only a one-way hash of the connection address is kept for up to 24 hours, solely to limit abuse). It is not linked to you or your Apple Account, is never used for advertising and is never shared with anyone. It follows the setting for anonymous usage data: if you turn off Settings → Privacy → Share Anonymous Usage Data, no crash reports are sent.

Anonymous usage data

To learn what people make with BookletMaker and where they get stuck, the Mac, iPhone and iPad apps send a small number of anonymous events to our own server (api.bookletmaker.app). An event records, for example, that a PDF was opened, or that a booklet was printed or exported, together with the layout, paper size and page-count range used (for example “9–16 pages”), which tools were used, which template was previewed or used (its ID in the public template catalog), whether opening it succeeded, whether BookletMaker Pro is active, the type of error if something went wrong, and the answer if you choose to tell us what you’re making. Each event also carries a random install ID created on your device, the app version, the OS version and the app language; the country is derived from the connection, and your IP address is not stored with the events. Events never include the contents or names of your files, or anything you type. They are not linked to your Apple Account, are never used for advertising and are never shared with anyone. You can turn this off at any time in Settings → Privacy → Share Anonymous Usage Data.

If you install BookletMaker from an Apple Search Ads ad, the iPhone and iPad apps send Apple’s anonymous attribution token (it names no person or device) to our server once, in your first day, without the install ID. Our server asks Apple which campaign and keyword the ad came from and answers with one word that sets which booklet layout the app starts on (for example church or zine). The token and the campaign are not stored, never linked to you or your documents, and not used for advertising. The app then records one anonymous event, install_intent, with how that start was chosen (an ad, a link, a custom App Store page or none) and the layout word, both from a fixed list. Nothing is used for tracking across other companies’ apps and websites, so no tracking permission is needed. All of this is skipped if you switch off Share Anonymous Usage Data.

When you edit a template or use My Templates, the same rules apply. The events record only the kind of edit (template_text, template_style, template_photo, template_color, template_hide, template_delete, template_move, template_resize, template_add, template_layer, template_duplicate, template_recolor_art, template_page; once per document), what was done to one of your saved templates and whether it worked (my_template: save, save as, duplicate, rename, delete or use; ok, Pro screen shown or failed). They never include a template’s name, the text you typed, your photos or any file name.

Seasonal content

For seasonal events such as Christmas cards, the apps check bookletmaker.app every few hours for a small public file that describes the current event (its dates, a short message and an optional sample PDF). This is a plain download: nothing about you or your documents is sent.

Templates

The apps download a small public catalog of the available templates from bookletmaker.app every few hours and whenever you open Templates, followed by the files of the templates you look at or use (their PDFs, thumbnails and fonts). With each of these downloads the app sends its name, version and build number, the platform and type of device (Mac, iPhone or iPad), the system version, the app language and your device’s region, the catalog format it reads, and whether BookletMaker Pro is active. It contains no ID of any kind, no device name or model, and nothing about you or your documents. We use it only to decide whether templates are available for your version and to serve the right files. It is not linked to you, and it is separate from the anonymous usage data above, so turning that off does not stop it.

My Templates

Editing a template changes only your own copy. Saving your own templates (a BookletMaker Pro feature) stores them on your device, in BookletMaker’s application data. They are not sent to us and are not synced through iCloud or any other service, so they do not appear on your other devices. A saved template holds its design, the text you typed and any photos you put in it. Photos stay on your device and are never sent to us; their location and other metadata are removed when you add them. Deleting a template removes it from this device. Templates may be part of your own device backup, which is controlled by you and Apple, not by us.

Third-party services

BookletMaker uses no advertising services and no third-party analytics. In-app purchases go through Apple’s StoreKit. The upgrade screen uses the Adapty SDK, which is contacted only once that screen is opened and receives purchase and subscription events — never document data — so we can see which plans people choose.

Purchases on this website

Pro bought at bookletmaker.app/buy (for the Windows and Android apps and the web tool) is paid on a page hosted by Stripe, our payment processor. Stripe receives your name, email address, billing address, payment details and the location used to calculate tax, and handles them under its own privacy policy; we never see your full card number. From Stripe we receive and keep only what is needed to issue and support your licence: the plan, the payment and subscription status, your email address and Stripe’s customer reference. Your documents are never part of this. Purchases made in the App Store go through Apple and are not affected.

Children's privacy

BookletMaker is not directed at children under 13 and does not knowingly collect personal data from anyone, including children.

Contact

Questions or concerns: [email protected]