Privacy

Effective September 5, 2026. Unignorable is operated by Paul Jump. This policy covers the NYC web app and native iPhone app.

Planning a walk

You can enter addresses without granting location permission. Web address searches go through our service to OpenStreetMap Nominatim. Native address suggestions use Apple MapKit, with our geocoder as a fallback. Routing requests send start, destination, optional stop and selected avoidance areas through our server to Valhalla. The application does not keep a server-side trip history unless you explicitly save a walk to an account. Short-lived service caches help return results.

The web map loads OpenStreetMap tiles; the iPhone map uses Apple MapKit. These providers receive network requests needed to display maps. Opening Apple Maps or Google Maps shares that route with the chosen provider. Their privacy policies apply to those services.

Optional accounts and saved walks

Accounts use passkeys. We store an account name, random account ID, passkey public keys and sign-in sessions. Your device or password manager keeps the private key; we do not receive biometric data. Browser sessions use a secure, HttpOnly cookie; native session tokens are stored in Keychain. Sessions expire after 30 days. There is no email or password reset; keep your passkey in your password manager or add an additional passkey.

Only when you choose Save walk do we store its name, start and destination coordinates and labels, optional stop and preferences under your private account. We do not automatically upload recent searches, live location or walking progress. Saved walks remain until you remove them or delete your account. Account management includes removal of individual walks, sign-out and account deletion. Deletion removes account credentials, sessions and synced walks from the live service. Separate anonymous feedback and public observations are not linked to this account.

Nearby checks and public records

When you choose to submit a nearby check, your coordinates are used to check proximity, then discarded. We retain the condition ID, observation, time, approximate distance bucket and a pseudonymous network-derived identifier used for deduplication and abuse prevention. Submissions wait for review and do not directly change forecasts. Approved checks, report text and optional photos can appear in public records. Do not include personal details or images of people.

Product feedback

We store the topic, usefulness answer, message, platform, submission time, review status and reply for up to 90 days. No route coordinates or email address are attached. Feedback is private to the operator. A random receipt link shows only status and reply; anyone you give that link to can read the reply. The latest receipt ID is saved on your device. To request early removal, send its receipt ID through Feedback.

Device storage and service operation

The web app can save planner preferences and addresses in your browser. Record pages use bounded device storage to recognize repeat visits and send aggregate daily event counts without location or a new server-side visitor identifier. The iPhone app stores your latest feedback receipt in app preferences. It also keeps downloaded map data for up to seven days, the active walk for up to two days, and up to twelve recent addresses in a list that expires after thirty days without updates in protected local storage excluded from device backups. Saved map data is labeled with its download time when a refresh is unavailable. Clear recent addresses from Saved walks; removing the app clears its local map and walk files. Sign out before removing the app to remove its Keychain session token. Clear browser site data or remove the app to remove device storage.

Our server and hosting providers process network addresses for delivery, security and rate limiting. Infrastructure logs may contain request metadata. Some legacy campaign pages use first-party usage analytics and offer optional email-based participation. Those older flows are separate from planning a walk and sending product feedback.

Your choices

There are no advertising SDKs or cross-app tracking in the iPhone app. Location is optional and requested for actions you choose. Manage permission in your device settings. Public source records come from NYC Open Data and OpenStreetMap and may remain available from those sources independently.

Use Feedback for privacy questions or removal requests. We may update this policy as features change; the effective date will change with it.