Agistly Privacy Policy

Effective date: 2026-10-03 · Last updated: 2026-10-22

Agistly keeps your personal app records on your device. We do not operate an account service or a cloud copy of those records. The app does not upload those records to us. Purchases use Apple’s StoreKit; sharing, support, and system services are described below.

Who is responsible

Agistly is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). Questions and privacy requests:

Contact: captainlongevity@gmail.com

The records stored on your device

These records and preferences are used to provide the app features you choose. Local calculations do not send the input records to a developer-operated service. There is no in-app account or developer-operated cross-device sync.

How Agistly handles its main features

Boarding records and photographs are stored locally. The app does not connect to banking, credit-reporting, veterinary, or government systems. Bundled references are informational; following an external legal-help link or search opens your browser.

Optional permissions and system services

Permissions are requested in connection with the feature that needs them. You can refuse or revoke them in iOS Settings; features that need a refused permission may be unavailable. Selected photos and files are separate from granting unrestricted access to an entire library.

Widgets, shortcuts, and session displays

Widgets and shortcuts use locally stored or cached app data in this app’s shared container. Information you choose to display can be visible on a Home Screen or Lock Screen; use the system’s display and notification settings for sensitive records. These displays do not create a developer-operated upload service.

Sharing, exports, and external links

A lien-evidence PDF is built locally and offered to the iOS Share Sheet. Agistly does not send notices, demand payment, contact a boarder, or submit a filing.

Generating a file locally does not send it to us. When you choose a sharing destination, that app or provider can receive the selected content and apply its own privacy and retention rules. Opening a web link sends an ordinary request to the linked site. Review a report, photo, or screenshot before sharing information about yourself or others.

Apple purchases and diagnostics

Apple handles in-app payment and subscription billing. The app processes StoreKit product and transaction information to purchase, restore, and verify paid access. We do not receive your payment-card details or billing address through the app. Apple may provide sales reports and, depending on your Apple settings, diagnostic information through its developer services.

Apple’s handling of purchases, device services, backups, and diagnostics is described in Apple’s privacy information.

Analytics, advertising, and tracking

We have not added advertising, behavioral analytics, or third-party crash-reporting SDKs to Agistly. We do not sell your app records or use them for cross-app advertising tracking. This does not mean that Apple, an external site you open, or an optional data provider receives no connection information. Their exchanges are described above.

Retention, deletion, and device security

Deleting a boarding account also deletes its linked charges, payments, lien notices and communication history after a successful save. This is permanent record deletion, not account archiving or a recoverable snapshot. The App has no full-database import or Recently Deleted recovery; a generated document cannot reconstruct that account tree.

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.

Use a device passcode and appropriate operating-system protections. Optional App Lock, where available, is an access control and is not a promise that every copy, export, notification, or widget is encrypted or hidden. Because we hold no remote journal copy, we cannot recover a lost local record or delete a copy you sent to another provider.

If you contact support

Emailing captainlongevity@gmail.com voluntarily gives us your email address, message, and any attachments you send. We use that information to answer your request, investigate the issue, and meet applicable recordkeeping obligations. It is processed through email providers and kept as needed for those purposes; you may ask us to delete support correspondence, subject to any legal retention requirement. Please omit unnecessary private records.

This policy website

These static legal pages are hosted by Vercel. Loading a page makes a web request that can disclose your IP address, page URL, time, and browser or connection metadata to the host for delivery and security. We have added no advertising or analytics scripts to these pages.

Hosting information: Vercel’s Privacy Notice.

Children and privacy requests

Agistly is not designed to solicit children’s personal information through accounts or a developer-operated journal service. If you believe a child has provided personal information to us through support, contact us. You can manage local records yourself and contact us about support correspondence or other data we actually hold. For information held by Apple or another provider, use that provider’s request process.

Policy changes and contact

We will update this page and its last-updated date if these practices change. Material changes to app data handling will be explained before or when the affected feature is introduced. Privacy questions: captainlongevity@gmail.com.

When saved records cannot be opened

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 and attachment 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.

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; publishing this document does not update an installed App.

Saving changes in the updated editor

Updated account, charge, payment and communication forms report saving failures and retain their entries for retry. Failed deletion restores affected stored values and relationships. A new lien notice must save before its timeline opens. The lien timeline keeps its existing live editing strategy: fields can apply immediately and may autosave. A failed explicit save leaves changed text, dates and added photos in memory with a retry control; failed photo removal restores the prior image. Back navigation attempts to save pending changes; widget/reminder updates follow successful saving. Unconfirmed in-memory edits may be lost if the App closes.