Privacy notice.
Last updated: May 9, 2026
1. What we collect
The minimum required to deliver a bot to your channel:
- Discord channel ID — the destination channel you designated for a Newsris bot.
- Discord server (guild) ID — the server the channel lives in.
- An optional server label — a free-text name you (or we) give the row so we can identify it in our routing dashboard.
We do not collect your Discord user ID, email, password, IP address, browser fingerprint, or any analytics signal from the bot interactions themselves.
2. What we do NOT collect
- Message content — we do not read messages your users post in any channel. Our bots post; they do not listen.
- DMs — we never receive DM content sent to or from any Newsris bot.
- Reactions / threads / member lists — out of scope.
- Your email or other contact info — unless you contact us at support@aiah.us or join a waitlist on a different AIAH page (e.g., aiah.us/snapjoin/waitlist), which is governed by that page’s notice.
- Tracking pixels, GTM, page-view analytics on the Newsris pages. The Newsris marketing pages (aiah.us/newsris, /newsris/terms, /newsris/privacy) carry no analytics.
3. What we store
On our infrastructure (Turso-backed databases, hosted in the US):
- Bot fire history. Timestamps and content of each post we made — what we said, when, where (channel/server ID).
- Source content cache. Headlines, URLs, and metadata from public sources we ingested. We do not cache content behind authentication walls.
- Routing config. The channel/server IDs and language preferences mapped to each bot stream.
- Operational logs. Standard server logs (HTTP requests, error traces) retained for short periods for debugging, with no user-identifying content.
4. Third parties
Delivering Newsris requires a handful of providers:
- Discord. Bot delivery transport. Discord’s privacy policy applies to all message transport between the bot and your channel.
- Turso (libsql). Database hosting for the routing, fire history, and source caches.
- DeepSeek and Google Gemini. Language-model providers used to generate the briefs the bots post. Source content we pass to them includes only public text we’ve already ingested.
- Public news sources we read (Reuters, TechCrunch, Smol AI, BAL, MPI, layoffs.fyi, etc.). We hit their public feeds like any reader does.
We do not sell, rent, or share routing or fire-history data with advertisers or analytics firms.
5. Cookies and trackers
The Newsris pages do not set cookies or run analytics. If you visit other AIAH pages (e.g., a waitlist), those pages may set their own cookies; we’ll disclose that at the point of collection.
6. Data retention and deletion
To stop a bot from posting in your server: remove the bot from the server, OR ask the operator to delete the channel from our routing. Once removed, we lose the channel ID and the bot can no longer post there.
To request deletion of your server’s record from our routing config: email support@aiah.us or DM @arisdy on Discord with the server name. We’ll remove it, typically within 7 days.
Bot fire history (what the bot said, when) is retained for ongoing operations and is not personally identifying. We do not currently delete past posts on request.
7. Children's data
Newsris is not directed at users under 13 and does not knowingly collect data about them. If you believe a minor has interacted with a Newsris bot, contact us at support@aiah.us.
8. Changes to this notice
We may update this notice over time. Material changes will be announced in the public Newsris Discord server.
9. Contact
Questions, concerns, deletion requests: support@aiah.us or DM @arisdy on Discord.