Privacy Policy

1 Scope

This Privacy Policy applies to Iris, a Telegram bot and the services operated through it. In this policy, “Iris”, “we”, “us” and “our” refer to the bot and its operator.

Telegram separately processes information under its own terms and privacy policy. This policy describes Iris's handling of information after Telegram makes it available to the bot.

2 Information IRIS receives

Iris receives information through Telegram when you interact with the bot, use features in a chat or group, or send content or actions that Telegram delivers to it. Depending on how you use Iris, the bot may receive or store:

• Account and profile information such as your Telegram user ID, username, display name, profile details made available to bots, and whether the account is a bot.
• Chat and group information such as chat IDs, group names, usernames, membership or administrator status, and settings related to a group.
• Messages and media you send to Iris, commands, replies, captions, images, voice messages, documents or other content when needed to understand or perform a requested feature.
• Feature data such as preferences, saved content, game state and results, scores, leaderboards, Aura balances and ledger entries, social connections, bonds, referrals, streaks, boosts and other feature-specific records.
• Moderation and safety information such as moderation actions, abuse signals, security events, rate-limit information, strikes, and limited context needed to investigate misuse.
• Support and transaction information such as amounts, status, transaction or provider references, wallet addresses where applicable, and reconciliation records.
• Technical information such as delivery state, request timing, errors, reliability events and other operational metadata needed to run the service.

Iris does not need every category above for every user. The information involved depends on the features you actually use and the events Telegram delivers to the bot.

3 How information is used

Iris uses information to:

• respond to commands, messages and requested actions;
• run games, Aura, leaderboards, bonds, streaks, boosts, referrals and other persistent features;
• remember settings and maintain continuity across sessions where a feature requires it;
• provide AI, translation, search, media, quote and utility features;
• manage groups, moderation tools and permissions;
• process support transactions and reconcile their status;
• prevent spam, abuse, fraud and attempts to disrupt or misuse the service; and
• monitor reliability, diagnose failures and keep Iris working correctly.

4 AI, translation & media processing

When you use a feature that depends on artificial intelligence, translation, media search, quote generation, speech, vision or another external processing capability, Iris may send the information needed to perform that request to an appropriate service provider.

For AI features, this can include your prompt, relevant recent conversation context, reply context, selected persona or feature instructions, and media such as an image or voice message when that media is part of the request. For translation, the text to be translated and the relevant language information may be sent for processing.

Media or search features may send a search query and, where a provider requires it to operate the service or enforce its terms, a platform-provided or service-specific user identifier. Quote or media creation features may process selected message text, displayed author information or a profile image when those elements are part of the requested result.

Iris sends only the information reasonably needed for the selected feature. These external services process information under their own applicable terms and privacy practices.

5 Persistent features

Some Iris features are intentionally persistent. Examples include Aura balances and history, game statistics and results, leaderboards, bonds, referrals, streaks, boosts, group settings, user preferences, saved content and similar feature state.

This data may remain after an individual conversation ends because the feature would not work correctly without continuity. Where a record represents an economy, score, shared game, transaction or relationship between multiple users, Iris may also need to preserve or anonymize part of that record rather than simply removing the entire shared history.

6 Groups & shared spaces

In groups, Iris may receive messages and events that Telegram makes available to the bot. Iris may inspect a message to determine whether it is a command, mention, reply or otherwise intended for a feature, even when no visible response is ultimately sent.

Group features can create records that are shared by or visible to multiple participants, such as scores, game results, leaderboards, funding progress, moderation actions or group settings. Deleting one person's account data does not necessarily remove information that is required to preserve the integrity of a shared group record.

7 Payments & support

If you use a support or payment feature, Iris may store transaction metadata needed to create, verify, credit, reconcile, refund or investigate that transaction. This can include amount, currency or asset, payment status, provider references, timestamps, transaction identifiers and wallet addresses where applicable.

Payment processing may be performed by an external payment service. Iris itself does not store raw payment-card credentials in its support records.

8 Service providers

Iris relies on third-party services to provide some functionality and keep the service available. Depending on the feature, these may include:

• AI and language-processing services;
• translation, search, media and content-processing services;
• payment and transaction-processing services;
• hosting, storage, networking, security and reliability services; and
• other processors necessary to complete a feature you request.

Information is shared with these providers only when reasonably necessary for the relevant feature, transaction, security purpose or operation of Iris.

9 Data retention

Iris does not apply one retention period to every kind of information. Retention depends on why the information exists.

Short-lived conversation or operational data may be removed relatively quickly, while settings, game history, economy records, social state, moderation history and other persistent feature data may remain for longer. Security, anti-abuse, transaction, reconciliation and audit records may be retained when reasonably necessary to protect the service, prevent fraud, resolve disputes or preserve system integrity.

When data is deleted from the live service, copies may remain temporarily in protected backups until those backups are replaced through normal rotation.

10 Deletion & controls

You may use the data or privacy controls made available through Iris, or contact the operator, to request deletion of applicable personal data.

A deletion request may remove data, anonymize identifiers, or detach your identity from records where full removal would break a shared record or transaction history. Limited information may continue to be retained where reasonably necessary for security, fraud prevention, abuse handling, financial reconciliation, legal obligations, audit integrity or backup rotation.

Deleting data from Iris does not delete information held independently by Telegram or another service you chose to use through Iris.

11 Security & abuse prevention

Iris uses technical and operational measures intended to protect the service and the information it handles. The bot may retain limited security records, identifiers, event details or message excerpts when needed to detect abuse, investigate suspicious activity, enforce limits, prevent fraud or recover from failures.

No online service can promise absolute security. Iris is designed to limit unnecessary exposure while retaining the information needed to operate safely and reliably.

12 Your rights

Depending on where you live, privacy law may give you rights concerning your personal information, such as the right to request access, correction or deletion, or to object to certain processing.

Requests will be handled in light of the nature of the data, applicable law, and the legitimate need to preserve security, transaction and shared-record integrity.

13 Changes to this policy

Iris evolves over time. This policy may be updated when features, processing practices or legal requirements change. The current version will always be published at this address with its effective date. Material changes may also be announced through Iris when appropriate.

14 Contact

For privacy questions, data requests or concerns about Iris, contact the bot owner or admin through the contact or support method made available by Iris. This helps the operator associate the request with the correct Telegram account without requiring additional personal information.