Privacy

Accounts

You can use Verso without an account. Sign in is optional and only needed if you want saves, follows, preferred topics, and your city to follow you across devices.

On iPhone you can sign in with Apple or Google. On Android you can sign in with Google. We verify the identity token from Apple or Google, then create a Verso session on our servers. We do not receive or store your Apple or Google password.

If Apple or Google gives us a verified email, we store it so we can show it in Settings and so we can attach a second sign-in method to the same account when both tokens share that same verified email. Apple Hide My Email addresses (privaterelay.appleid.com) will not match a Gmail address, so those stay separate accounts. We do not merge two existing accounts later if emails happen to match.

Sign in with Apple may also share a name the first time you allow it. We store that display name when it is provided.

What syncs

When you are signed in we store your saved stories, followed people and places, preferred categories, chosen city, recently consumed cards, and hidden stories on our servers so they can appear on your other devices. Appearance, haptics, which feed tab you are on, and onboarding flags stay on that device only. Notification choices (major/local alerts, muted categories, follow alerts) sync with the device push record on our servers.

Guests send those same preferences as query parameters when they ask for a For you feed. Signed-in For you ranking uses the follows and city saved on your account instead.

Location

If you enable local news, Verso may request approximate (coarse) location so it can resolve a city on your device and fetch headlines for that place. Precise coordinates are not sent to our servers. You can deny permission and pick a city manually instead. If you sign in, that city name is stored with your account.

What we receive

The app loads story briefs, feeds, and search from our API. Publisher images may load from their hosts to show story art. Signed-in requests include your session token so we can load your saves and follows.

Notifications

If you turn on alerts, we store a device push token plus your notification choices — major events, local majors, and the city you picked for local news — so we can send those alerts. If you are signed in, that device record can be linked to your account. We don’t use this for ads. Turn notifications off in Settings to stop new alerts; uninstalling the app also drops the token over time.

On your device

Saves, follows, feed settings, a short offline cache, and (if you sign in) a session token stay on your phone. The session is stored in the iOS Keychain or Android encrypted preferences. Clearing app data or uninstalling removes local copies.

Deleting your account

Settings → Delete account removes your Verso user, identities, sessions, saves, and follows on our servers, and wipes that synced data plus the session on the phone you used. You can also email us at the address below.

Product analytics

The iOS and Android apps send product events toPostHogso we can see how the feed is used — for example that a story was opened, hidden, or saved, or that you changed a feed or notification setting. Those events include a story id, category, and similar metadata. They do not include the headline, the brief, or your email.

If you sign in we attach those events to your Verso user id so we can tell a guest session from a signed-in one. Sign out or delete account resets that link. We drop IP addresses on ingest. We do not use this for ads or sell it.

Session recordings

A sample of sessions (about one in ten) may record the screen as screenshots so we can debug blank feeds and broken navigation. Text fields are masked. Story images are masked. Headlines and briefs visible on screen can still appear in a recording.

Recordings are kept for 30 days. We do not send them to an AI model to watch. Sentry does not record sessions.

Crash diagnostics

Production builds may send crash and performance diagnostics toSentryso we can fix bugs. That can include crash logs, stack traces, device and app version, and API paths the app called — not screenshots or session replays. iOS may also send crashes to PostHog.

Contact

Questions, or a request to delete operational logs, analytics events, recordings, or crash events that may relate to you: emailhi@kjhq.dev. App Store and Google Play listings also declare this account data. Website:https://verso.kjhq.dev.