The app stores thesis work locally, uses Apple’s private iCloud services for same-account sync, and sends data off-device only for Apple sync, AI requests, exports, or store and distribution flows.
Thesis notes, source cards, draft blocks, literature maps, revision queues, imported PDF text, handwritten note layers, and writing workspace content are stored locally on-device first. On devices signed into the same Apple Account, the app can also mirror thesis data through its private iCloud database so the same project appears across the student’s own devices.
Thesis data uses the app’s private CloudKit database for devices signed into the same Apple Account. That Apple service is what moves project data between a student’s own iPad, Mac, and iPhone rather than a separate app account system.
Links, copied text, and notes shared into the app are intended to stay in the app’s local capture flow until they are imported into a thesis project and turned into source cards.
If a student enables AI Supervisor Mode with their own OpenAI key, the key is stored in Apple Keychain rather than inside plain-text project data. It can also sync through iCloud Keychain when that Apple feature is enabled for the same Apple Account.
If a student uses AI features with their own OpenAI key, the relevant prompt content is sent to OpenAI to generate the requested response. The key itself is stored in Apple Keychain rather than in plain-text project data.
Thesis data can move off a single device through Apple’s private CloudKit sync for the same Apple Account. AI prompt content leaves the device only when the student runs an AI feature with their own OpenAI key, and exports leave the app only when the student chooses to save or share them elsewhere.
If you install through the App Store or TestFlight, Apple handles those distribution flows through its own systems and policies.
Download a product built around student ownership and calm, explicit data choices.