DutyReady is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy question, write to captainlongevity@gmail.com.
Is there a DutyReady server holding my license and CE records?
No. There is no DutyReady server. Your credentials, continuing-education entries, and firearms-qualification dates live in this app's local SwiftData store on your iPhone. We cannot read them, restore them, or move them.
Does the app store images or PDFs of my certificates?
No. DutyReady records structured data only — course names, hours, dates, providers, categories, and credential details. It has no camera and stores no certificate images. The certificate files your CE provider gives you stay in your own Files or Photos app, outside DutyReady. CE compliance summary PDFs are built on demand and handed to the iOS Share Sheet. They include each credential’s details, cycle progress and logged courses with dates, hours, providers and categories; they do not embed certificate files, CE notes or firearms-qualification history. A PDF is a summary, not an importable database backup.
Do you collect analytics, crash logs, or an advertising identifier?
No. There is no analytics SDK, no crash reporter, and no advertising identifier in the app. We do not know how often you open it, which screens you visit, how many credentials you track, or whether you subscribed — except through Apple's standard, aggregate developer sales reports.
How does DutyReady compute my CE gap and reference state requirements?
Entirely on your iPhone, with deterministic rule-based logic. In version 1.1, for a fixed-hour reference whose training period matches your saved credential renewal cycle, the app subtracts your logged hours dated within that cycle through the current day to show an estimate. Future course dates and entries outside the cycle do not count toward that estimate. Conditional, course-based, local, discontinued, unconfirmed or mismatched-period references do not produce a completion percentage or automatic hour gap. Logged hours are not verified course credits or a determination of compliance. The bundled PI and security reference covers all 50 states and DC, with selected polygraph references, official source links and review dates; some rules remain explicitly unconfirmed. Updates arrive through ordinary App Store releases, not live regulatory monitoring. Nothing about these calculations is transmitted.
Do you talk to any state licensing board, Department of Public Safety, or government system?
No. DutyReady makes no API calls to any state licensing board, Department of Public Safety, regulatory agency, ASIS International, the National Council of Investigation and Security Services (NCISS), or any government system. The reference text is bundled lookup content. If you choose an official source link, your browser contacts that site under its own privacy practices; your credential or CE records are not included in the link. The app cannot and does not submit a renewal, report CE, or check a license on your behalf.
Does DutyReady sync records with iCloud?
No. DutyReady does not declare the iCloud entitlement; there is no CloudKit container and no remote sync. Your records may be included in your standard iOS Backups (iCloud Backup or Finder/iTunes backup) when those are enabled — that is Apple's normal backup behavior for all on-device data, not a DutyReady feature.
Device-backup contents and recovery depend on your system settings, a successfully completed usable backup and Apple’s restoration process; enabling backup alone does not guarantee recovery of every record or original file. We cannot retrieve or restore your device backups.
Preferences (including onboarding completion, App Lock and reminders), cached purchase access, and local rating-request history are stored in UserDefaults. Unsaved record-editing fields and the onboarding acknowledgement checkbox are held in memory; Save commits record fields and Cancel discards unsaved edits. Completing onboarding persists its completion flag. App Lock is not a separate password-encryption layer for these settings. Records and settings may be included in standard iOS Backups, depending on system settings and a usable completed backup. We do not have access to your iOS Backups. If you delete the app without an iOS Backup, your data is permanently lost. There is no in-app data export, import, or backup feature beyond CE summary PDF generation.
aps-environment entitlement.DutyReady offers an optional Pro tier (an annual subscription and a one-time Lifetime purchase) via Apple's StoreKit 2. When you subscribe, restore a purchase, or when the app verifies your entitlement, your device communicates directly with Apple's servers. StoreKit provides verified transaction information, including product and transaction identifiers, purchase and expiry dates, and revocation status, so the App can determine access on your device. The developer does not receive those transaction records through a DutyReady server. We do not receive your Apple Account credentials, payment method or billing address. Apple's handling of subscription information is governed by Apple's Privacy Policy.
You can manage these permissions at any time in iOS Settings > DutyReady. DutyReady requests no camera, no microphone, no photo library, no location, no HealthKit, and no contacts permission.
DutyReady is a personal recordkeeping and reminder tool for licensed security professionals. It is not affiliated with, endorsed by, or connected to any state Department of Public Safety, licensing board, or regulatory agency. It uses no government logo or mark, implies no official certification or endorsement, and submits records to no government system. It does not provide continuing-education courses, does not issue or renew licenses, and does not provide legal advice or any guarantee that a record will satisfy a board, an auditor, or a court. References to state CE requirements are based on publicly available regulatory content and are reference-only.
DutyReady is a professional tool intended for U.S. adults who hold or are applying for an occupational license. We do not knowingly collect any information from anyone, including children.
Deleting a credential also deletes its linked continuing-education entries and firearms qualifications after a successful save. Calendar events created earlier are separate and are not removed by that record cascade. There is no Recently Deleted or full-database import; a generated PDF cannot recreate that history.
After successful edits or deletion, the App attempts to reconcile pending reminders and refresh widget snapshots, and repeats reconciliation on launch or foreground activation. Delivered notification history, failed snapshot writes or iOS-managed widget refresh timing can leave earlier content visible. App Lock does not protect notification previews, widgets, Calendar copies or shared files; manage their visibility in system settings. Removing the App normally removes its local container, not independently kept original media, exported files, recipient copies or older backups. Manage those copies separately. Device-backup recovery requires a usable completed backup; the developer has no record archive to retrieve.
DutyReady is published in English and marketed in the United States. The reference data (state continuing-education requirements by credential type) is U.S.-specific. The App does not route records through a developer-operated record server. Apple services, legal-page hosting, support correspondence and any sharing destination you choose may process information outside your country under their own policies. Those services are separate from the App’s local record storage.
If a future release ever changes how the app handles data — for example, if a later version ever introduces any sync, analytics, or third-party integration — we will update this policy and surface the change in the app before that feature becomes available. The "Last updated" date above reflects the most recent revision.
Privacy questions: captainlongevity@gmail.com
The app requests full Calendar access. Event titles, dates, notes and alarms created by the app are saved to your system calendar, which may sync to a calendar-account provider or be visible to people sharing that calendar. These Calendar copies are outside the app’s local database and App Lock; deleting an app record or uninstalling the app does not guarantee removal of every calendar or synced copy. Manage those copies in Calendar and the relevant account. Removing an event created by the integration looks it up using its saved event identifier.
These legal pages are hosted on Vercel. Opening a page sends ordinary request information, such as the IP address, browser information and requested URL, to the host for delivery and security; see Vercel’s Privacy Notice. This website request is separate from App record storage. If you email support, we receive the address and information you choose to send so we can respond. Send only the details needed for that request.
The updated App pauses the normal record interface if its persistent database cannot be opened and only a temporary in-memory store is available. New recording and editing through that interface are blocked. The App keeps the existing database files rather than treating the temporary empty store as your archive. Database-dependent startup work in that interface is paused; previously scheduled reminders, widget snapshots or independent copies may remain.
Older versions may have written records to a separate fallback database. The updated App leaves those files in place and does not automatically merge, replace or delete them. Check available device storage, close and reopen the App, and contact support before deleting or reinstalling it. This recovery screen is not a backup, a repair guarantee or an automatic restoration of missing records. Older installed versions may behave differently until updated.
The updated App checks credential, continuing-education and firearms-qualification saves and deletions before closing their forms or reporting completion. Relevant failures preserve the affected record or current form entries for retry. Calendar changes and saving their local link are separate operations. If a Calendar event was created or removed but its local status cannot be saved, the detail page offers Retry saving Calendar status for that same operation; it does not create another event on that retry. The current status is retained in memory and may autosave, but an interruption before persistence can leave a Calendar copy without a usable saved link or a stale link. If Calendar removal cannot be confirmed, the stored link is kept and the App asks you to check Calendar. Credential deletion still does not remove external Calendar copies.