Useful context without building a dossier on you.

Effective: September 28, 2026

The short version

• An account is optional. The account feature may not be enabled in every build.
• We do not sell personal data or use third-party advertising trackers.
• The app does not request GPS, contacts, microphone, camera, or photo-library access.
• If you do not sign in, your topic preferences, saved Before setups, onboarding state, and optional home area remain stored on your device.
• If optional account sync is enabled and you sign in, only your broad topic levels are synchronized to our service. Home area, Before profiles, reminders, onboarding state, and catch-up history remain device-local.
• Some information is sent to our backend when needed to provide a catch-up, answer a “What?” request, or synchronize the optional account feature.

Information stored on your device

Informedish stores app preferences locally, including topic levels, optional home area, saved Before profiles, whether onboarding is complete, and the time of your most recent catch-up.

If optional account sync is enabled and you choose to sign in, broad topic levels may also be synchronized to our backend. Home area, saved Before profiles, reminder state, onboarding state, and catch-up history are not included in account sync.

Information sent to our service

When you load a catch-up or use Before, the app may send your optional home area and topic preferences to our backend so it can rank current material appropriately.

When you use “What?”, the text you type is sent to our backend so we can identify the likely current story and return a source-backed briefing. Informedish does not intentionally maintain a personal search-history profile tied to an account or identity.

For the anonymous web version of “What?”, we also derive a short-lived pseudonymous abuse-control fingerprint from the request's network address using a server-held HMAC secret. The raw network address is not stored in that rate-limit record. The fingerprint and request counters are retained only long enough to enforce short burst and daily usage limits, then expire automatically.

If optional account sync is enabled and you sign in, your Clerk session token is sent with private account requests for verification. Informedish does not store that token. We store an opaque internal account ID, a provider-scoped cryptographic fingerprint of Clerk's verified user identifier, and your broad topic levels. We do not copy your Clerk email address, phone number, display name, or profile information into the Informedish sync record.

Service providers and data sources

We use service providers and public/third-party data sources to operate Informedish. These currently include:

• Vercel for hosting and server infrastructure.
• MongoDB for storing operational story, source, and briefing data, short-lived anonymous web abuse-control windows, and, when optional account sync is enabled, privacy-minimal account preference records.
• Clerk for optional sign-in and account authentication. Depending on the sign-in methods enabled for Informedish, Clerk may process identifiers such as an email address, phone number, or third-party sign-in identity. Informedish does not copy those profile identifiers into its topic-sync record.
• OpenAI for generating some source-backed briefing text from selected source material. The current briefing-generation path does not intentionally include the raw text of your “What?” query in the model prompt.
• GDELT and source publishers for discovery and source material. When a “What?” request requires targeted discovery, a cleaned version of the search text may be sent to a discovery provider to find relevant current material.

These providers may process technical request information, such as IP address, timestamps, and service logs, as part of operating and securing their infrastructure.

Analytics, advertising, and tracking

Informedish does not currently include a third-party advertising SDK or cross-app advertising tracker.

For website operations, we keep coarse daily aggregate counters for server/origin work such as Ish, Before, topic pages, public event pages, and web “What?” requests. These counters contain only the route/product area, coarse outcome, bounded timing totals, and limited built-in dimensions such as Before room/time or broad topic. They do not contain a cookie identifier, account ID, session ID, raw network address, home area, or the text of a “What?” query.

These aggregate operational counters are used to detect errors, understand server workload, and verify that generation-heavy paths stay bounded. CDN edge-cache hits intentionally do not create MongoDB analytics writes.

If our analytics or advertising practices materially change, this policy and the applicable App Store / Google Play disclosures will be updated before the change is released.

Retention and deletion

Local app preferences remain on your device until you change them, clear the app’s data, or remove the app.

If optional account sync is enabled and you sign in, synchronized broad topic levels and the pseudonymous account mapping remain until you change them or delete the account. The app provides a Delete account action when the account feature is enabled. A successful deletion removes the synchronized Informedish preference record, the provider identity mapping, short-lived account rate-limit records, and the corresponding Clerk user. Device-local home area, Before profiles, reminders, onboarding state, and catch-up history are not server account data and therefore remain on the device unless you clear the app's local data or remove the app.

Operational source, event, and briefing records are shared product data rather than account data and are retained as needed to run, audit, and improve the source-backed briefing system.

Aggregate public-web operations counters are retained for up to 120 days, then expire automatically.

Children

Informedish is a general-audience current-events product and is not designed specifically for children. Live news and current-events material may include discussion of violence, conflict, crime, or other mature subjects.

Changes to this policy

We may update this policy as the product changes. The effective date above will be updated when we make a material change.

Contact

For privacy questions, correction requests, or support, email josh@noraknows.ai.