CatchMeUp — Privacy Policy

Last updated: May 2, 2026

Operator: Stego Apps ("we," "us")
Contact: through the official support channel or the contact method listed in the Discord App Directory (same paths as in our Terms of Service).

1. Overview

CatchMeUp ("the Bot") is a Discord application that helps users summarize recent activity in a Discord text channel. This policy describes what information is involved when you or your server uses the Bot, and how we use processors such as Discord and AI providers.

2. Where the Bot runs

The Bot operates within Discord. Use of Discord is also governed by Discord's Terms of Service and Discord's Privacy Policy.

3. Information the Bot accesses

When someone runs a Bot command in a channel where the Bot is present and has permission to read messages, the Bot may:

• Read recent channel messages that Discord returns via the channel history API (up to the limits configured for your server tier—for example, up to a capped number of recent messages and/or a time window you select).
• Read message content (including text and, where applicable, attachment metadata) needed to build a transcript for summarization. The Bot does not continuously copy your entire server history to a separate product database for training purposes as part of the features implemented in our application code; processing is driven by user-initiated commands.

For each included message, the Bot typically processes:

• Timestamps (as shown in the summary input),
• Author display names (as shown in Discord),
• Message text (after Discord's "clean" transformation where applicable),
• Optional images: small image attachments may be downloaded temporarily and sent to the AI service when your deployment uses a multimodal-capable provider configuration (for example, Google Gemini in our supported setup). Other provider configurations in code may send text only. Very large images may be skipped; some expired attachments cannot be retrieved.

Bot and system messages are generally excluded from the transcript where the implementation filters them.

4. Information you provide directly

Slash command options, such as an optional time filter (minutes_ago) and, for eligible servers, an optional question for context-aware Q&A. Questions may be length-limited by the Bot.

5. How we use this information

We use this information only to:

• Generate channel summaries or answers to your optional question based on the retrieved messages;
• Enforce fair use, cooldowns, and per-server daily limits so the service remains reliable;
• Reply to you in Discord (typically as ephemeral replies visible only to the user who ran the command, per Discord's behavior).

We do not use your data for unrelated marketing purposes through these features.

6. AI providers (subprocessors)

To produce summaries, the Bot sends a transcript (and, when applicable, image content) to an AI provider configured for our deployment. Depending on configuration, that may include OpenAI, Anthropic, Google (Gemini), and/or OpenRouter (which may route requests to other underlying models).

Those providers process content according to their terms and privacy policies. Examples:

• OpenAI: openai.com/policies/privacy-policy
• Anthropic: anthropic.com/legal/privacy
• Google AI / Gemini: ai.google.dev/gemini-api/terms (and related Google privacy notices as applicable)
• OpenRouter: openrouter.ai/privacy

Retention on our servers:Our application code is designed around transient processing for message content used in a request. We do not describe storing full channel logs in a long-term "chat archive" table for summaries in the current codebase; operational logs on servers may still contain error or diagnostic information—see section 9.

7. CatchMeUp Pro and payments

CatchMeUp Pro is offered through Discord's monetization (for example, subscriptions/entitlements in the Discord App Directory). We rely on Discord to determine whether your server has an active entitlement. We do not receive your full payment card details from Discord as part of that flow; billing is handled by Discord and its payment partners under Discord's policies.

8. Data we store on our systems

What we persist may include:

• Per-server, per-day usage counters (for example, counts of successful summary generations used to enforce daily limits), stored in a local database file on the infrastructure that hosts the Bot.
• Ephemeral operational state in memory (for example, short-term caching of a generated summary to avoid duplicate work, and cooldown timestamps). This is not intended as a durable archive of your messages.

Optional / future features:Our codebase may include database helpers for "last read" timestamps that are not wired into the running Bot in the current main flow. If you enable such features later, update this section to describe exactly what is stored.

9. Logs and security

We may process technical and security logs (for example, application errors, rate-limit messages, or hosting provider logs). Those logs might occasionally include fragments of content if an error payload includes request details. Retention depends on our hosting environment and operational needs; we aim to keep logs no longer than reasonably necessary for debugging, security, and reliability. Access is limited to those who operate the service.

We use reasonable safeguards appropriate to the nature of the service and hosting environment. No online service can guarantee perfect security.

10. Data location and transfers

Depending on how and where the Bot is hosted, data may be processed in the regions where our hosting provider runs the service (which may include the United States and other regions). AI providers may process data in the United States or other regions according to their infrastructure. For GDPR or similar regimes, consult your counsel regarding appropriate transfer mechanisms.

11. Your choices and controls

Server permissions: Administrators control which channels the Bot can access and whether it can read message history.

Discord settings: Users can adjust privacy settings within Discord; removing the Bot from a server stops new processing there.

Requests: For access or deletion requests, contact us through the paths listed at the top of this policy. What we can delete depends on what we hold—for example, aggregate per-server usage counters are generally not attributable to a single user in isolation.

12. Children's privacy

The Bot is not directed at children under the minimum age required by Discord or applicable law. If we learn we have collected personal information from a child inappropriately, we will take appropriate steps consistent with applicable law and our counsel's advice.

13. Changes to this policy

We may update this policy when functionality or legal requirements change. We will revise the "Last updated" date and, where appropriate, provide notice through Discord or this site.

14. Contact

For privacy questions or requests: through the official support channel or the contact method listed in the Discord App Directory, consistent with our Terms of Service.