Privacy policy

LogBooklet has no developer-run server, no account and no built-in analytics. The app stores your journal on your device and shows selected content through the Apple system features you configure. Apple may also store journal data in your iCloud account through sync or device backup. I cannot read it.

What the app stores

The app stores your entries, including their text, time and optional coordinates, for a photo or video entry a copy of the photo or video and its caption, for an audio entry the recording and its length, and for a location entry only its coordinates, along with booklet names, the Siri names you give a booklet, snippets, each booklet's settings and any text you have typed into a booklet but not yet sent. Each device has its own local SQLite database in a private App Group folder. On iPhone and iPad, LogBooklet and its Share Extension and widget extension can access that folder. On Apple Watch, the watch app and its widget extension can access the watch's folder. Widget extensions read the local database without starting their own iCloud sync or changing the database. The photos, videos and recordings themselves are files beside the database: those made on the device stay in that folder until they are uploaded to iCloud, and every file on the device after that, including those downloaded when you opened their entries, is kept in the app's cache, which iOS may clear when the device needs space. Settings shows how much space they take and can remove the downloaded ones.

The share editor stores text, web links or a photo or video you choose to send from another app as ordinary entries after you tap Save. It does not fetch linked webpages. The last booklet used for sharing, the last booklet opened on watch, whether photos and videos you take are saved to your photo library, an identifier of the iCloud account the downloaded files belong to and when the app last cleaned up files in iCloud are remembered in local preferences and do not sync to other devices. The app also stores a local database-readiness receipt and a history checkpoint used to refresh entries across processes. Depending on your device settings, Apple may include local app data in a backup.

Exporting a booklet on iPhone or iPad saves a Markdown or JSON file where you choose. A booklet with photos, videos or recordings is saved as a folder holding that file and the files it links to, which the app first downloads from iCloud if they are not on the device. Export All Booklets in Settings saves one ZIP archive with a Markdown or JSON file for every booklet, and a folder with the files of each booklet that has them, also where you choose. The app writes an export to its temporary folder on the device first and deletes it there once the export is saved, cancelled, fails or is handed to the shortcut. Opening a photo full screen works the same way with a copy of the photo, deleted when the photo is closed. The Export Booklet action returns the file, or with Include Photos, Videos, and Recordings a ZIP archive of the folder, and Export All Booklets returns the archive to the shortcut, which decides where to save or send it. An export started in the app keeps running when you switch to another app, and while it runs, iOS shows its progress on the Lock Screen, with the booklet's name when one booklet is exported.

Photos, videos and the camera

An entry can hold a photo or a video. When you take one in LogBooklet, the app asks for access to the camera, and for a video also to the microphone for its sound. When you choose one, the system photo picker runs outside the app and hands it only the photo or video you pick, so the app neither sees the rest of your library nor asks for permission to read it. A photo or video you share to LogBooklet from another app or pass to the Log Photo or Log Video action in Shortcuts arrives the same way. The app stores its own copy of each photo as a JPEG of at most 2048 pixels on its long side, and of each video as an MP4 of at most 1920 by 1080 pixels, each with a smaller preview. The copy leaves out the original's metadata, such as the place and time it was taken and the camera that took it. The entry records its own time and coordinates, as any other entry does.

Photos and videos you take in LogBooklet are also saved to your photo library, as the Camera app saves them, with the coordinates the app read while it was open. For this the app asks for permission to add photos, which does not let it see the photos in your library. You can switch saving off in the app's Settings under Save Photos and Videos You Take, and the permission under Settings › Privacy & Security › Photos. Photos and videos you choose from your library or share from another app are not saved again.

Recordings and the microphone

An entry can be an audio recording. When you record one in LogBooklet, on iPhone, iPad or Apple Watch, the app asks for access to the microphone and uses it only while the recorder is open and recording. On iPhone and iPad a recording continues when you leave the app or lock the device. The system's microphone indicator shows while it records, and a Live Activity on the Lock Screen and in the Dynamic Island shows the time recorded and the booklet's name until you send or discard the recording. On Apple Watch, leaving the app pauses the recording. A phone call or Siri pauses it on every device. The app stores the recording as AAC audio, with its length and a waveform drawn from its loudness. On iPhone and iPad, an audio file you pass to the Log Audio action in Shortcuts is converted to the same format, without its metadata; on Apple Watch it is stored as it comes. You can switch the microphone off under Settings › Privacy & Security › Microphone.

Location

If you allow it, the app reads your position while it is open and uses the latest coordinates for entries you create. Log Location saves that position as an entry of its own. On watch, it requests a foreground fix while a booklet is open, while you compose, record or prepare to log a snippet, and when you tap Log Location. Saving does not wait for a fix and stores no coordinates if a recent fix is unavailable. In the iPhone and iPad entry editor, tapping the current-location button requests one location fix to center the map. The coordinates are saved with the entry only after you confirm the map position and save the entry. Location access is optional. You can decline it or switch it off later under Settings › Privacy & Security › Location Services, or in the watch's privacy settings.

The app does not read your position in the background. While the share editor is visible, it attempts to read your position using existing location permission. Saving uses a valid fix from the past minute if available and otherwise stores no coordinates. It does not wait for location or request new location permission from the share editor. An entry created through Shortcuts or Siri uses the action's location option. The default, Automatic, uses the location the shortcut passes in, or the position the app read while a booklet was open if that fix is no more than a minute old. Without either, an ordinary entry has no location. Log Location requires coordinates. On iPhone and iPad, if no location was supplied and no recent fix is available, it asks to open the app to request a single current location using foreground permission. It saves only if that request succeeds. No Location stores no coordinates even if a location was passed in. Chosen Location requires a location from the shortcut. Direct snippet actions from iPhone, iPad and watch widgets and controls can use a location the app read in the foreground during the past minute. They do not request permission or start background location tracking.

The map

The iPhone and iPad entry editor, the map previews of location entries in a booklet and on Apple Watch, and the read-only entry map on Apple Watch use Apple's MapKit. Displaying a map can send the area shown, coordinates and connection data to Apple and its map-data providers. Searching for a place in the iPhone or iPad editor can also send the search text. The watch map shows the entry's saved location; it does not search for places or look up an address. This data does not come to me. Apple's Maps privacy notice explains how Apple handles it.

Siri and Shortcuts

LogBooklet offers actions to the Shortcuts app and to Siri, such as logging an entry, logging your location or reading entries back. They run on your device. So that phrases like "Log in Food with LogBooklet" and "Log my location in Travel with LogBooklet" can name a booklet or a snippet, the app gives the Apple operating system the names of your booklets, the Siri names you set for them and the text of your snippets. This also applies to Siri and Shortcuts on Apple Watch. The entities offered to system actions also expose their properties, including draft text, latest-entry previews, entry counts and dates, settings, and the kind, text, time, coordinates and length of entries returned by an action. The Get Media of Entry action, and a photo, video or audio entry passed on to another action, hand over the app's copy of its file, downloaded from iCloud first if it is not on the device. When you log a snippet in the app, the app tells the system so that it can suggest logging it again. Apple states that it may extract anonymized App Shortcuts data, such as the phrases and the names shown for their parameters, to train the models behind the feature. None of it comes to me.

A shortcut you build can pass entries on to other apps or services. Where they go from there is up to that shortcut. What you say to Siri or to system dictation is handled by Apple. Dictation on watch returns text to LogBooklet. Depending on your device and settings, Apple may process voice input to Siri and dictation on the device or send it to its servers, as its Siri, Dictation & Privacy notice explains.

Widgets and controls

Apple stores your configuration for Home Screen and Lock Screen widgets, watch-face complications, Smart Stack widgets and controls. The configuration identifies the booklets and snippets you select and your display preferences. LogBooklet provides booklet and snippet entities to the system's configuration picker. These include names, snippet text and the booklet properties described above. Snippet configurations ask you to choose a booklet first, then offer global snippets and snippets belonging to that booklet. Before logging, the app checks that the snippet still belongs to the selected booklet or is global.

Apple renders widget snapshots from the content the extension supplies. Widgets can display booklet names, entry previews, dates, counts and snippet wording in layouts that have room for them. Recent Entries on iPhone and iPad displays entries from the booklets you select. Quick Entry indicates whether a draft exists without showing its text. The app marks journal text for system privacy redaction. There is no separate text visibility setting. Watch widget suggestions use entry timestamps and draft activity, without health access or background location tracking.

On iPhone and iPad, direct snippet buttons and opening controls require local device authentication. Control labels identify their configured destination and use system privacy redaction while unauthenticated. Direct logging buttons run an action in the app's process, which can save an entry in the background without opening the app's screen. They save to the same local database as the app, leaving its draft intact. Widget extensions do not send a second copy of the entry to another device.

Handoff

Handoff gives Apple's Continuity system the identifiers of the current booklet and, when applicable, the current entry, together with whether you are composing a draft. This lets a nearby iPhone or iPad continue the same view. The activity does not include entry or draft text. The receiving device reads its own database, so it may need to wait for iCloud sync before showing new content. Handoff does not send journal data to the developer.

iCloud

With iCloud switched on for LogBooklet, each app mirrors its database to the same private database of your Apple Account so it can sync across your devices. The Apple Watch app syncs directly with iCloud and does not require the iPhone app to be installed. The Share Extension saves locally; those entries upload when the phone app's normal sync cycle runs. Saving means the entry is stored on that device, not that another device has received it. Offline entries remain local until a connection and iCloud sync are available. Without usable iCloud, the app can still save locally.

Photos, videos and recordings are not part of that mirrored database, because it would copy every file to every device. Each is a separate record in a zone of the same private database, which the app uploads from the device that made it. Another device, Apple Watch included, downloads a file only when you open its entry, copy it, export it or pass it to a shortcut. Until the device that made it has uploaded it, other devices show its preview and say so. Deleting an entry, or giving it a new photo, video or recording, deletes the old file from iCloud, once the device that did it is online. Once a week at most, iPhone and iPad also delete files in iCloud that are more than 30 days old and that no entry refers to any more.

Apple does not expose that private database to developers, and it counts against your iCloud storage. To stop syncing, turn LogBooklet off under Settings › your name › iCloud. The app does not share your database with other users or use a public CloudKit database.

What it never does

• No analytics, advertising or tracking built into the app.
• No third-party SDK or crash reporter. Apple frameworks only.
• The app does not connect to a server run by the developer.
• No account, no purchases, no payment details.
• No app access to your contacts or health data. The microphone is used only while you record audio or a video in the app, including a recording that continues after you leave it, and the camera only while you take a photo or video. The app adds photos and videos you take to your photo library and otherwise receives only the photos and videos you choose in the system picker. Voice input to Siri and dictation uses Apple's services as described above.

Deleting it

Deleting an entry or booklet removes it locally and sends the deletion to iCloud, together with the deletion of its photo, video or recording. Other devices apply it when they next sync. Deleting the app removes its local database on that device, while offloading the iPhone or iPad app preserves its data. Deleting the watch app does not delete entries from the phone or iCloud. Apple manages complication, widget and control choices in the system's configuration. To clear LogBooklet's iCloud data, use Settings › your name › iCloud › Manage Account Storage › LogBooklet › Delete Data. Files you exported, photos saved to your photo library and device backups are managed separately where you saved or configured them. Deleting a photo or video entry does not delete the photo or video from your library.

This website

logbooklet.com sets no cookies and runs no analytics. Cloudflare, Inc. serves the site through Cloudflare Pages. It processes the IP address, requested page, time, browser and network information needed to deliver and protect the site. The site cannot be delivered without this data. The legal basis is Art. 6(1)(f) GDPR, with a legitimate interest in secure and reliable operation. Cloudflare processes data in Europe and the United States. For transfers to the United States, it uses the EU-U.S. Data Privacy Framework and EU Standard Contractual Clauses. Cloudflare keeps the data under the retention rules in its privacy policy.

Contact and your rights

Leon Eck is responsible for the processing described here. If you write to [email protected], the email address, message and delivery data are used to answer you and kept only as long as the request or a legal retention duty requires. The email provider processes them to deliver and store the message. The legal basis is Art. 6(1)(b) GDPR for requests about the app and otherwise Art. 6(1)(f) GDPR, with a legitimate interest in answering correspondence.

Where the GDPR applies, you may request access, correction, erasure, restriction or portability of your data. You may object to processing based on legitimate interests and complain to a data protection authority. Send requests to the email address above. Last updated 29 October 2026.