Privacy Policy — Sheaf

Last updated: 17 May 2026

Applies to: Sheaf — Document Review (iPhone and iPad app, bundle identifier com.mobiledrafter.app)

Supersedes: this policy replaces the general Linclaw Labs privacy policy at /legal/privacy for any use of Sheaf. Where the two conflict, the Sheaf-specific policy below applies.

Summary

Sheaf does not collect any data.

The app runs entirely on your iPhone or iPad. There is no Sheaf account, no Sheaf server, no analytics pipeline, no advertising SDK, and no telemetry. Documents, flags, voice memos, photos, and your in-app preferences live only on your device.

The remainder of this document explains what that means in detail, and what limited interactions exist with Apple’s own systems (the App Store, StoreKit, iCloud Backup) — none of which Sheaf can read or control.

What Sheaf does not do

Sheaf does not contact a Sheaf-controlled server at any time, for any purpose.
Sheaf does not run any analytics, telemetry, crash-reporting, or remote logging service that sees your usage. No Firebase, no Mixpanel, no Sentry, no App Center, no internal logging endpoint.
Sheaf does not include any advertising SDK or third-party tracker.
Sheaf does not create a Sheaf account. There is no sign-up, no login, no password to recover.
Sheaf does not read your contacts, calendar, location, or device identifiers.
Sheaf does not transmit the contents of your documents, flags, voice memos, or photos anywhere. The only path for that data to leave the device is when you yourself tap the system Share button (AirDrop, Apple Mail, Files, etc.); after that point, the receiving app or service is responsible — Sheaf has no further role.

What Sheaf stores on your device

Sheaf stores the following on the iPhone or iPad it runs on. All of it is protected with iOS’s standard file-protection class (NSFileProtectionComplete), which encrypts the data at rest while the device is locked.

Imported documents: read-only copies of PDF and Word files you import. The original file is unchanged. Sheaf reads it for display; it does not modify the bytes on disk.
Flags: the issues, risks, questions, and notes you create against passages of a document, including titles, body text, optional voice memos, and optional photos. Each flag is anchored to a character range in the document’s extracted text.
App preferences: your reviewer name (for the Annotated Word export’s comment author), your auto-lock timeout, which first-time guide cards you’ve dismissed, and similar UI state. Stored in iOS UserDefaults.
Subscription state: a cached flag indicating whether your Sheaf Pro subscription is currently active. The flag is derived from Apple’s signed StoreKit receipt; we do not store payment information, your Apple ID, or your email address.

You can delete any of the above at any time by deleting the flag, document, or the entire app. Deleting Sheaf from your device removes all Sheaf-stored data on that device.

Apple’s role

Sheaf is distributed through the Apple App Store and uses Apple’s subscription system (StoreKit). This means Apple — not Sheaf — handles:

Account, identity, and payment: managed through your Apple ID. Sheaf never sees your name, email, address, or payment method.
Subscription state: Apple confirms to Sheaf, via a cryptographically signed receipt on your device, whether your Sheaf Pro subscription is active. The receipt does not include personal information beyond what Apple manages.
iCloud Backup: if you have iCloud Backup turned on in iOS Settings, the iOS system may include Sheaf’s local data (documents, flags, preferences) in the device-wide backup, encrypted with your iCloud key. Sheaf does not push to iCloud separately and does not have access to the backup.

Apple’s own privacy policies govern these interactions. They are independent of, and not modified by, this policy.

Third-party software included in Sheaf

Sheaf is built with a small number of open-source libraries, all linked into the app at build time. None of them makes network calls in Sheaf:

ZIPFoundation — used to open and re-package .docx files locally for the Annotated Word export feature. Source: github.com/weichsel/ZIPFoundation
DocReader — used to extract paragraph text from .docx files for the reader. Source: github.com/germanhl36/DocReader

Both run entirely on-device. Neither sends data anywhere.

What happens when you share

Sheaf has multiple export and share paths (Annotated Word, Annotated PDF, Share Issues List, Markdown, JSON, PDF report). Each of these creates a file or a piece of formatted text on your device and hands it to iOS’s standard Share Sheet for you to forward via AirDrop, Mail, Files, Messages, or any other app you choose.

Once the data has left Sheaf for another app, that other app’s privacy policy applies. Sheaf is not aware of the recipient, the destination, or what subsequently happens to the data.

Children

Sheaf is a professional tool for reviewing legal and business documents. It is not directed at children under 13, and we do not knowingly collect any information from children. As described above, Sheaf does not collect information from any user.

Your rights

Because Sheaf does not collect any personal data, most of the rights commonly described in privacy policies (access, rectification, erasure, portability, restriction) do not have a practical action on our side: there is nothing for us to look up, modify, or transmit.

If you nonetheless wish to confirm this in writing, or have any other privacy-related question, contact us at the address below.

Changes to this policy

If Sheaf’s data practices ever change — for example, if a future version adds a feature that contacts a server — we will update this page before that version ships, and surface a clear in-app notice the first time the new behavior runs. The “Last updated” date at the top of this page reflects the most recent revision.

Contact

Linclaw Consulting AB
Ljungdalen 301
845 99 Ljungdalen
Sweden

Email: info@linclaw.eu