LifeCase Privacy Policy

Information LifeCase stores or handles locally

Users may choose to add information such as:

• Cases, case titles, and case types
• Records, titles, dates, notes, and descriptions
• Tags, people labels, places, source labels, and other context
• Attachment names and references
• Export selections and related state

LifeCase uses this information locally to display timelines, help users find records, and generate Case Package PDFs.

Information LifeCase does not currently send to North Beacon Labs

Build 7 does not include LifeCase accounts, cloud sync, LifeCase server storage or upload, OCR, AI processing, subscriptions, advertising, or advertising tracking.

The app does not currently transmit LifeCase cases, records, notes, attachment references, export selections, or source documents to North Beacon Labs servers.

Support communications

If a user voluntarily emails North Beacon Labs at support@northbeaconlabs.dev, North Beacon Labs receives the sender's email address, message body, and any information or attachments the user chooses to send.

North Beacon Labs uses that information to review and respond to the support request. Users should avoid sending sensitive records or source documents unless they are truly necessary.

Photos, screenshots, documents, and attachment references

LifeCase accesses only photos, screenshots, or documents a user chooses through the device picker. Build 7 stores attachment names and references for timeline and export context.

Original attachments remain separate from generated Case Package PDFs. LifeCase does not promise permanent preservation, backup, or recovery of original source files.

Case Package PDFs

Users can select records and generate a Case Package PDF locally. An export may contain user-entered notes, dates, tags, labels, places, attachment names, and other context chosen for inclusion.

A Case Package PDF can include a cover page, disclaimer and notes, a timeline, and a Record Index. Original attachments remain separate from the generated PDF.

Sharing and export boundary

When a user invokes the iOS share or save interface, the user chooses where the exported PDF goes. That choice may move the PDF outside LifeCase.

External apps, services, and storage destinations govern exported information under their own storage, security, and privacy practices.

Accounts, cloud, AI, and OCR status

• No user accounts or sign-in
• No LifeCase cloud sync or server upload
• No OCR
• No AI processing
• No subscriptions
• No advertising or advertising tracking

If a future version changes how information is processed, North Beacon Labs should update this policy and the relevant disclosures before releasing that behavior.

User choices

• Choose which cases and records to create
• Choose which photos, screenshots, and documents to select
• Edit record details and export selections
• Choose whether to generate a Case Package PDF
• Choose an external destination through the iOS share or save interface
• Choose what non-sensitive information to include in a support request

Device storage and deletion considerations

Data stored locally by Build 7 is device-specific. Users should not rely on LifeCase as backup storage for original files.

LifeCase does not provide its own cloud synchronization, backup service, or cross-device recovery in this build. Apple device or iCloud backup behavior may separately affect whether app data can be restored. LifeCase does not control or guarantee restoration from those backups.

Retention and deletion

• Case and record data remains in local app storage unless it is changed through available app controls or removed through device or operating-system actions.
• Build 7 allows users to delete individual records. It does not provide case deletion or an app-level delete-all/reset control.
• Users can clear an attachment reference from a record. Clearing a reference or deleting a record removes that reference from LifeCase data but does not delete the original photo or document.
• Documents selected through the picker and generated Case Package PDFs may use app cache storage. Build 7 does not provide a user-facing control for deleting those cached files.
• LifeCase stores no app content on North Beacon Labs servers in this build, so North Beacon Labs has no server copy of LifeCase cases or records to delete.
• Support emails and voluntarily supplied attachments are separate from LifeCase app content. North Beacon Labs does not promise an automatic deletion schedule for support communications.
• Copies held in Apple device or iCloud backups, or in destinations selected through the iOS share or save interface, are outside LifeCase's direct control.

Security

LifeCase limits current data handling by keeping the documented Build 7 workflow local to the device. Device settings, access controls, backups, and any destination selected for an export can affect the privacy of information.

No app, device, storage system, or sharing destination can be guaranteed to be completely secure or permanently recoverable.

Product boundaries

LifeCase is not a law firm and does not provide legal, medical, financial, or other professional advice. It does not prepare court filings, verify evidence, rank records, or predict outcomes.

Policy updates

North Beacon Labs may update this policy as LifeCase changes. Material changes should be reflected in the policy and effective date before or when the relevant app behavior is released.