← Back to the good stuff

THE SMALL PRINT, IN PLAIN ENGLISH

Privacy policy

Duely closed alpha · App policy updated September 8, 2026

This policy covers the Duely Mac app during the closed alpha. It is written by the maker of the product to be accurate. If anything here turns out to be wrong, please report it so we can fix it.

About this website

This marketing website has no account sign-in, signup form, or analytics integration. Early-access links open your email app; they do not send a message automatically. If you email us, the information you choose to send reaches Duely's contact address through your email provider.

The sections below describe the Mac app. Website note added September 8, 2026.

The shape of the system

Duely keeps your working semester and artifacts on your Mac. The configured production app requires account sign-in. An account connects Duely's model service and course-file sync; it does not back up the entire workspace. Reading saved work does not require a new model request.

What stays on your Mac

Your class meeting times, class summaries, agent conversations, and the documents, PDFs, slides, spreadsheets, and code drafts you make in Duely live in Duely's folder on your Mac. Workspace files stay in the folder you approved, and workspace-file edits stay inside it.

Courses and assignments are stored locally, including when you are signed in. Your account-specific day plan, estimates, session-done marks, and optional Duely-local study blocks stay on this Mac and are included in work recovery. Those blocks do not create events in connected calendars. Study history and tool preferences also stay on this Mac. Saved work survives a normal relaunch; keep your Mac backed up to protect it. The development Canvas Data scheme uses an isolated disposable session instead.

The local draft library belongs to the Mac user account. Documents, workbooks, slides, PDFs, code drafts, and chats remain available when that Mac user changes Duely sign-in; signing out of Duely does not hide or erase them. Account-specific class and Study records keep their existing owner. Use separate macOS user accounts when different people share a Mac.

Recovery copies

Settings offers an optional saved-work recovery copy. It contains selected saved library files, including records for the Duely accounts used by this Mac user, in a folder you choose. Duely does not encrypt or upload the copy. A cloud-synced destination may upload it through that folder's own service.

The copy excludes Duely's account credentials, browser sessions, pending jobs, and submission approvals. External workspace and code-project folders need their own backup. Unsaved edits are not included.

Restoring requires inspecting and choosing a recovery copy, then restarting. Duely keeps the previous library in the local Duely Recovery folder and preserves existing account ownership. Restoring does not grant external project access or resume old jobs and approvals. Recovery copies and retained previous libraries stay until you remove them; account deletion does not remove those local copies.

What syncs when you sign in

When course-file sync is available, course files the agent reads—class summaries, explored course pages, and assignment notes—are stored in your own account space in Firestore, in the US region. Server-side security rules restrict synced records to your signed-in account. The current app keeps the course and assignment ledger local.

Guidance and planned app control

The existing Guide can capture a selected app window and recognize its visible text for your requested explanation. macOS manages Screen Recording consent. Raw captures are temporary; images you separately attach to a conversation are saved with that conversation.

The planned companion brings visual guidance and approved work into the same assignment conversation beside the browser or a desktop app. It may use screenshots, recognized text, Accessibility content, and app integrations to understand selected work, and click, type, scroll, or drag when needed. A dedicated integration is not required. Guidance draws temporary overlays and waits for you to act. Control stays within approved apps and windows, checks the target and result, and provides an immediate stop. Passwords and authentication stay with you.

The companion sidebar, general Mac input control, and connection to the shared assignment agent remain unfinished. These are planned capabilities. App permissions do not approve changes, and macOS Screen Recording, Accessibility, and per-app Automation permissions still apply. Observations do not create a separate activity archive or background keystroke collection.

What reaches the model

When you use model-backed features such as course reading and agent runs, the approved material needed for that task is sent through Duely's backend to OpenAI's GPT API. This can include an approved browser page, files inside the workspace folder you chose, course material you pasted or imported, your request, relevant course names and deadlines, the agent's working notes, or a requested Guide window capture and recognized text. Planned companion context follows the selected app/window scope described above.

The assignment-agent context list shows what was included and what was withheld, with the reason. Your contacts, Keychain, background keystrokes, and unrelated content outside your selected pages, apps, windows, and files are not included. Production requests use the backend, which holds the model API key and verifies your sign-in. The separate development key mode calls OpenAI directly using a key supplied on that Mac.

Duely's backend streams prompts and outputs through and stores neither. OpenAI processes that traffic under its commercial API terms, including its standard API data handling and short-term abuse monitoring. Duely has not opted into a training-data program. Your Mac retains saved work produced with the model. Contact us if you would like the full closed-alpha model disclosure.

Analytics

The new Mac app source includes optional usage measurement, off until you choose Share usage measurements in Settings and the service confirms it. The older signed build has no product analytics. Sending feedback does not enable collection, and local Canvas/test sessions do not collect it.

Approved events pass through Duely's authenticated backend to PostHog's US service. They include operation and feature names, outcomes, typed errors, timestamps, bounded durations and counts, app build, and random account, attempt, session and work references. PostHog receives no Duely email or raw account ID. Analytics exclude prompts, answers, coursework, grades, titles, filenames, URLs, search text, screenshots, clipboard contents and keystrokes. There is no session replay, heatmap, generic autocapture or new automatic crash collector. Client IP data is discarded and GeoIP is disabled.

Turning collection off stops capture on this Mac and requests removal of unsent events; the app shows storage failures and pending service confirmation. Already received events are separate. Delete measurement history requests their removal from Duely and PostHog and remains pending until the provider verifies erasure, which can take several days. Duely retains raw backend events for up to 90 days; PostHog's selected Free plan retains them for up to one year. Scheduled maintenance removes expired backend records; outages or failed cleanup can delay removal and require repair. These periods are the configured expiry targets.

Feedback you choose to send

Send feedback saves a local draft and previews the exact report before sending. You choose the category and text; the preview includes app version/build, coarse macOS version, feature and any typed error code. Coursework, logs and screenshots are not silently attached. Signed-out drafts can be copied or exported; sending requires the intended signed-in account. Drafts and queues stay separate by account and are excluded from coursework recovery copies.

Submitted report text stays in Duely's feedback service, visible to the maker through restricted operator access, for up to 180 days unless deleted sooner. It is not sent to PostHog or an AI. My reports shows receipts, status and deletion controls. Local copies remain until you remove them, separately from server retention.

What Duely's operator can see

Retention and deletion

Synced account records, usage ledgers, and model-run receipts are kept until account deletion. Backend logs use the logging provider's default retention, recorded as 30 days in the closed-alpha data retention details. OpenAI's own API retention applies separately to model traffic.

Delete account is available in the app's Settings. It requires a recent sign-in. It first prevents new product writes and requests PostHog measurement erasure. Pending erasure keeps the account available for an explicit retry; the app does not claim completion. Once verified, deletion ends signed-in sessions and removes account records, product reports/events, usage ledgers, receipts and the account itself. A content-free server fence prevents late requests from recreating records for 24 hours after confirmed account deletion; incomplete deletion keeps its fence until completion or operator repair.

Account deletion preserves your coursework, saved files and recovery copies on this Mac. While erasure is pending, the app stops collection and clears the affected account's unsent analytics and local analytics references; storage failures are shown. Local feedback drafts and report copies remain until you remove them. Account deletion does not erase provider-retained logs. Removing the app alone does not erase its saved library in Application Support; delete local records or that library separately when you want them gone. Contact us for the full data retention details.

A question, or something to fix?

Email crdurnin15@gmail.com.