Abidence Privacy Policy

Effective date: 2026-06-17 · Last updated: 2026-11-15

Abidence stores your cases, incidents and optional filing dates on your iPhone. It has no developer-operated record server or analytics service. Apple handles purchases; Calendar accounts, selected PDF sharing destinations, device backups, support and legal-page hosting have their own handling as described below. The App does not file complaints or send your case to a housing provider or agency automatically.

1. Who publishes Abidence

Abidence is an independent iOS app published under a single Apple Developer account (Team ID ZM8LF8494F). Privacy questions can be sent to captainlongevity@gmail.com.

2. Where your records live

Every incident you record, every case, every party you name, every protected-class tag you choose, and the optional HUD and private civil-action filing dates you enter are stored in the app's local SwiftData store on your iPhone. Abidence has no backend and no cloud sync (it does not declare the iCloud entitlement and uses no CloudKit container), so there is no copy of your records anywhere the developer can read, restore, or move. Your records may be included in your standard iOS Backups — iCloud Backup or a Finder/iTunes backup — when you have those enabled, which is Apple's normal behavior for on-device data and not an Abidence 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.

3. What you record, and what Abidence never asks for

Abidence records structured facts about what a housing provider did: an exact, approximate, or unknown occurrence date, the party involved, a description of what happened, their verbatim words, a note about written materials, and witnesses. The App stores the time a new incident is first saved separately from when it happened. Older incident records may have no recording time. It does not collect or store a Social Security number, financial-account number, government ID, or any health record.

You may optionally tag which protected class you believe was involved — race, color, national origin, religion, sex, familial status, or disability. These tags are entirely optional and user-selected; you may leave them all blank, and the app never builds an identity profile from them. The disability category records only an "accommodation denied" event fact — never a diagnosis or any health detail.

4. No analytics or advertising; on-device processing

There is no analytics SDK, no crash reporter, and no advertising identifier in Abidence. The developer does not know how often you open it, which screens you use, how many incidents you log, or whether you subscribed, except through Apple's standard aggregate sales reports. The federal Fair Housing Act summary and state agency lookup guidance are bundled reading material. Opening a public resource link takes you to a site with its own privacy practices. Abidence does not include case information in those links. Countdown arithmetic uses only filing dates you enter; the App does not derive legal deadlines from the first or latest incident or decide which laws, extensions or exclusions apply. Countdown arithmetic and repeat-party grouping run on your device.

5. On-device features that use Apple frameworks

The updated App keeps an on-device count of new incidents successfully saved, the time of the first such save, and whether it has already requested Apple’s optional App Store rating prompt. These settings contain no case text and are not sent to a developer server to request a rating. Apple controls whether its rating prompt appears and handles any rating you choose to submit.

6. Subscriptions and StoreKit

Abidence offers an optional Pro tier (an annual subscription and a one-time Lifetime purchase) through Apple's StoreKit 2. When you purchase, restore, or when the app checks your entitlement, your device talks directly to Apple. Abidence uses Apple-provided product prices, offer eligibility and verified transaction details such as product identifier, expiration and revocation to display offers and control access. It does not receive your Apple ID, payment method or billing address. Apple's handling of that information is governed by Apple's own Privacy Policy.

7. Permissions

Abidence requests Face ID only if you enable App Lock, and Calendar when you choose to add an entered filing date, and Notifications when you enable local deadline reminders. You can revoke these permissions at any time in iOS Settings > Abidence. The app requests no camera, no photo library, no microphone, no location, no contacts, and no HealthKit access, and it does not track you across apps.

8. Deleting your data

Deleting a case removes its saved filing dates and linked text-based incident records after a successful local save. Removing just a filing date leaves the case and incident history intact. Separate adversary profiles remain; deleting a case is not a wipe of that directory. There is no Recently Deleted or database-archive restore; a PDF cannot rebuild the deleted records.

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.

If you delete Abidence without an iOS Backup available, the records are permanently gone — there is no complete App-archive export, import or backup feature, and no remote copy for the developer to recover. Readable PDF exports are separate reference copies, not restorable archives. If a case matters to you, generate an Evidence PDF and save it to Files, email it to yourself, or send it to your attorney while you are building it.

9. What Abidence is not

Abidence is a personal recordkeeping tool. It is not affiliated with HUD, the Department of Justice, any government agency, any housing provider, landlord, real-estate brokerage, or lending institution, or any law firm or fair-housing organization. It does not provide legal advice, does not determine whether any conduct was unlawful discrimination, does not predict the outcome of a complaint or lawsuit, and does not recommend attorneys. Fair Housing Act and state references are general public-law information only.

10. Children

Abidence is intended for U.S. adults. The developer does not knowingly collect information from anyone, including children.

11. Regional scope

Abidence is published in English and marketed in the United States. The federal Fair Housing Act summary and state agency resources are U.S.-specific. The App does not automatically upload your records to a developer-operated server. Apple services, website hosting, support correspondence and destinations you choose for sharing can process information outside your region under their own practices.

12. Changes to this policy

If a future release ever changes how the app handles data — for example, if a later version ever introduces sync, analytics, or any third-party integration — this policy will be updated and the change surfaced in the app before that feature becomes available. The "Last updated" date above reflects the most recent revision.

13. Contact & Support

Privacy questions: captainlongevity@gmail.com

Calendar permission and copies outside the app

On iOS 17 and later, the Calendar action requests write-only access and does not import existing events. Event titles, dates and notes 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. Editing or removing an App filing date does not update or delete an existing Calendar copy. Previously generated or shared PDFs also keep the dates shown when generated; regenerate a report when needed.

Website requests and support correspondence

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.

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.

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.

Saving changes in the updated editor

Updated case and incident forms retain entered fields when saving fails and restore affected model values and relationships. A failed case deletion preserves its incident graph. Canceling a new form does not roll back other pending records. The optional Calendar action adds only filing dates the user has saved, supports either date independently and reports a failed event commit. Calendar copies remain separate from App records; check Calendar before retrying an interrupted action to avoid duplicates. Temporary form entries are not a backup and may be lost when the App closes.

Optional filing dates in the updated App

Existing case titles, first incident dates and incident histories are retained. The two new optional filing-date fields start empty for existing cases; earlier calculated dates are not treated as confirmed user input. The editor holds proposed dates in temporary screen state until saving succeeds. A failed save restores the prior stored values; Cancel leaves the saved dates unchanged.

After confirming applicable dates with HUD or a qualified attorney, you may enter a HUD date, a private civil-action date, both or neither. Abidence does not verify them. An empty date produces no countdown or reminder. Successful case saves and deletes refresh local reminders. The Pro screen has Restore Purchases, including progress and results for restored access, no active purchase, incomplete verification, cancellation or failure. Restoring checks Apple purchase access and does not restore cases or incidents. Cancellation or a failed Apple sync does not itself revoke access. Repeated requests share one operation. After a successful sync the App verifies current access again; a newer verified transaction takes precedence over an older read for that product. Reminders are available without Pro when you enable them and permit notifications. They use only dates you entered and are refreshed on startup, foreground return and successful changes to saved filing dates or cases. A refresh clears older filing-date notifications, including inferred notifications from earlier versions. If saved dates cannot be read, the old notifications are not replaced. If scheduling fails, the Deadlines tab reports the problem. Notification delivery depends on your device settings. The case title and entered date information may appear in notification previews according to those settings, separately from App Lock. Pro Calendar copies are a separate, user-initiated action. Older installed versions may still require Pro for reminders.

Previously exported PDFs and Calendar copies require separate review; the App cannot correct copies already saved or shared elsewhere.

App Lock and open screens in the updated App

App Lock remains optional, off by default and available without Pro. It uses Apple biometric authentication; the App does not provide its own passcode fallback. A temporary interruption such as a system permission or purchase prompt does not by itself lock the App. When the App truly enters the background, a branded privacy screen covers open App content, including editors and share panels, and the App locks. On a protected launch or return, the App tries to authenticate once when ready. If Apple has an active purchase or restore flow, the App keeps its records covered after backgrounding until it can ask for authentication. Canceling or failing authentication keeps content protected; tap Unlock to try again. A completed authentication from an earlier background cycle cannot unlock the current screen.

Locking keeps the open interface and its temporary edits in memory so you can continue after successful authentication. Locking does not save a draft, create a backup or guarantee recovery after the App closes. It does not change saved records, purchase access or notification schedules. App Lock does not recall a file already handed to another app or cancel an existing external transfer. App Lock controls access to the App interface; it does not add separate encryption to exported files or protect copies already shared, Calendar entries, notification previews or system backups.