Files
iris_x_hermes/docs/playstore-listing.md
T
ARIA f90e40a3fc
CI / Gateway plugin tests (push) Failing after 1m4s
CI / Kotlin tests (android host + desktop) (push) Successful in 8m3s
Fix README limit claims to match reality (issue #13)
- 'No file limit' -> 100 MB default, configurable via max_upload_bytes
- 'No character limit' -> 'No 4,096-character limit like Telegram'
  (hard frame-body cap: 1 MiB)
- Note that limits are set on the gateway side (hermes), not in the app
- Sync docs/playstore-listing.md (same overclaim)
2026-08-24 21:05:13 +02:00

1.9 KiB

Play Store Listing

Copy-paste text for the Play Console (and the F-Droid / sideload pages). Keep this file in sync with the README whenever the privacy story changes.

Short description (≤ 80 chars)

Private chat for your personal AI agent — Android & desktop.

Full description

Iris is a native chat app for your personal AI agent (hermes-agent): streaming replies, visible reasoning, structured tool activity, channels, threads, media, search — Telegram-quality, on your own infrastructure.

Absolute Privacy! — everything stays on your own infrastructure:

  • Your gateway, your machine, your data. No cloud middleman for chat.
  • Push notifications: ntfy by default — push metadata stays on your own (self-hosted) ntfy server.
  • FCM is opt-in (IRIS_PUSH_BACKEND=fcm): standard and reliable, but FCM push metadata (notification title, device token) is routed through Google's servers. If you want truly private communication, use ntfy (self-hosted) instead — it is the default.

100 MB file uploads by default (configurable on your gateway). No 4,096-character message limit like Telegram. Full markdown + HTML artifact preview. All settings live in the app.

Runs on Android and desktop (Linux, macOS, Windows) from one shared codebase.

Privacy note (for the "Data safety" section / FAQ)

Iris talks directly to your own hermes gateway over a private, token-authenticated connection. By default, push notifications use ntfy, which you can self-host so that push metadata never leaves your infrastructure. If you explicitly enable FCM, push metadata (notification title, device token) is sent via Google's FCM servers; chat content itself is not sent to Google — FCM only carries a short preview, and full content is fetched from your gateway over the authenticated connection. For truly private communication, use the default ntfy backend (self-hosted).