NeighborLog is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy-related question, write to captainlongevity@gmail.com.
We do not collect, transmit, store on a server, sell, share, or analyze:
All dispute data you enter is stored locally on your iOS device using Apple's SwiftData framework. This data may be included in your iCloud or iTunes device backup if you have device backup enabled. We do not have access to your device backups.
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.
The updated Pro noise meter processes microphone input briefly in memory using AVAudioEngine to calculate approximate levels. It does not record audio, retain or queue microphone buffers, encode sound, write audio files, play microphone input back or upload it. Each input callback is reduced immediately to numeric power statistics. The App does not copy or retain the microphone buffer after calculation; iOS manages the system audio buffers. A saved measurement contains numeric average and peak estimates, duration, dates, any notes and an optional incident link, rather than audio. Input stops when you leave the meter, background the App or the App receives an audio interruption; resuming requires a new Start Measuring action. Estimates are unweighted and device-dependent, not calibrated sound-pressure or dB(A) measurements, and are intended for relative comparison and personal documentation.
Earlier installed versions used a temporary local audio file while measuring and could leave a file after interruption or failed cleanup. The updated App attempts to remove only that meter’s old UUID-named scratch files at launch after the journal opens and when the meter opens, starts or stops. A cleanup failure can leave an older file; the meter shows a warning and retries at those later events. This is best-effort cleanup, not a guaranteed erasure deadline or removal of independent copies. Updating these web pages does not change an older installed App: the in-memory implementation and cleanup apply when the updated App version is installed. Use the microphone only where permitted; this description does not guarantee compliance with recording or consent laws.
The following free and Pro features process data locally on your device only:
The updated subscription screen asks StoreKit whether the current Apple Account is eligible for the annual product's introductory offer. A configured trial alone does not establish eligibility. The eligibility result is held only in memory for the screen, refreshed when it opens or returns to the foreground and after purchase or restore attempts, and is not written to the journal or uploaded to the developer. This check does not give the developer your Apple Account identity or payment details. The screen shows trial wording only after a positive result; otherwise it shows the localized regular price, with a checking or unavailable explanation when eligibility has not been confirmed. Apple's purchase confirmation determines the final offer and charges. This presentation change applies after installing the updated App.
NeighborLog offers optional Pro access through Apple's StoreKit 2 as an annual auto-renewable subscription or a one-time Lifetime non-consumable purchase. The App also continues to recognize valid legacy monthly subscriptions that are no longer marketed to new customers. When you load products, purchase Pro, restore a purchase, or when the App verifies your entitlement, your device communicates directly with Apple's servers. NeighborLog processes verified StoreKit purchase information needed to unlock features. A local cache can retain the latest transaction identifier, product identifier, purchase and signing dates, expiry or revocation date, upgrade status and StoreKit environment for each supported product and environment. Expired or revoked entries may remain locally to prevent an older callback from restoring access incorrectly. This cache contains no dispute records and is not uploaded to a developer-operated server. We do not see your Apple ID, payment method, billing address, or complete transaction history. Apple's handling of purchase information is governed by Apple's Privacy Policy.
Version 1.4 keeps this purchase-access cache in UserDefaults, separate from the SwiftData journal. Verified access can bridge a temporarily incomplete StoreKit read, but a subscription grant is bounded by its verified expiration. Access checks run at launch, on foreground return, at a known subscription expiration and when StoreKit delivers transaction updates. Restore Purchases asks Apple to synchronize purchase access; it does not restore or merge journal records, photos or reports. These checks do not upload your journal to Apple or the developer.
You can revoke any of these permissions at any time in iOS Settings > NeighborLog.
You may enter information about a neighbor — name, address, vehicle, behavior — into NeighborLog as part of documenting your dispute. This information is stored locally; the App does not automatically send it to the developer or a recipient. Reports you choose to share can include it. You alone are responsible for the lawful collection, storage, and use of any third-party information you record in the app. NeighborLog does not automatically contact or identify a neighbor or send dispute data to another party. A report or export you choose to share can contain the information you entered. The app is one-sided personal documentation.
NeighborLog is not directed to children under 13. We do not knowingly collect any information from anyone, including children. The app's age rating reflects this.
Deleting a neighbor checks deletion of its incidents, including attached photo copies and inline witness references, before completing. The updated App retains separate witness-directory entries, communications, complaints, costs and numeric noise measurements, explicitly detaching their deleted-neighbor or deleted-incident relationships. Witness-directory identifiers for the deleted incidents are removed; complaint records retain their historical related-incident identifiers. Deleting an individual incident likewise keeps numeric readings as detached records and removes its witness-directory links. Failed deletion preserves the original affected graph and links. This is not a complete dispute-data wipe. There is no Recently Deleted or database-archive restore, and a PDF cannot reconstruct the journal.
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.
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. The app is published in English and is primarily marketed in North America.
If we ever change how the app handles data, we will update this policy and surface the change in the app before you can use the affected feature. The "Last updated" date at the top of this page reflects the most recent revision.
NeighborLog's widget displays locally prepared summaries of app records. The app and its widget exchange the relevant summary and preferences through an on-device shared container; this is not a developer-operated record upload. Information displayed by a widget can be visible to people able to view the Home Screen or Lock Screen where it is placed. Use the widget and device display settings to control that visibility. Screenshots and independent copies remain separate from the records you later edit or delete.
Privacy questions: captainlongevity@gmail.com
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 checks record creation, form saves, onboarding and deletions without rolling back unrelated pending edits. New incident entry keeps its two-stage workflow: the first successful save creates a real incident, then independent photo, numeric-reading and witness actions can save their own records. Closing or failing the later form does not undo earlier successful independent saves. Existing neighbor-profile text and dates remain live and may autosave; Save profile changes checks persistence, rather than treating the profile as a separate temporary draft. Other open form values are retained for retry after checked-write failure. Incident photos remain independent immediate saves: failed additions keep original stored bytes and GPS values while new selections remain in the current view for Retry saving photos or Discard. A failed library preparation adds none of that selection and supports retry or clearing. Confirmed removal affects the attached copy after successful saving, not the original library image or exported copies. Unsaved form values and photo selections are temporary memory, not restart-proof drafts. When Stop & Save fails, the stopped measurement’s numeric values remain temporarily for Retry saving reading or Discard without restarting microphone capture; retries reuse the same measurement identifier. No microphone buffers or audio are retained by this retry. A later attachment-sheet edit remains a live edit; it can autosave, and reassigning a numeric measurement does not erase an earlier incident’s mirrored numeric summary. The microphone processing, unweighted estimate limits and old-audio cleanup described above remain unchanged.
If the journal database cannot be opened, the updated App shows Saved records unavailable instead of terminating or showing an empty working journal. Existing database and photo files are kept and normal record-dependent views and startup work are paused. Check available storage and close/reopen the App; contact support before deleting or reinstalling it. This is not a repair guarantee or a backup.