Privacy

Zinging Privacy Policy

Updated October 16, 2026

This policy explains how Zinging, a Discord bot operated by Lakshay Chawla, handles information when people use it.

Information Zinging processes

When Zinging is online in a server and can access a channel, Discord may deliver message text and related Discord identifiers to the bot. Zinging reads message text to recognize its z prefix commands and to provide features enabled by a user or server administrator, including translation, reaction-based translation, and short cat-banter replies. The bot requests the Message Content privileged intent; it does not request the Guild Members or Guild Presence privileged intents.

Zinging also processes Discord user, server, channel, and message identifiers needed to handle commands, apply settings, and associate saved preferences. If a user provides a prompt or text for a bot feature, that input is processed for the requested feature.

How information is used and shared

• Ask, code, and cat-banter prompts, including relevant recent message context, are sent to a third-party AI platform selected by the operator to generate a response.
• Text submitted for manual, reaction-based, or administrator-enabled translation is sent to a third-party translation service selected by the operator to produce a translation.
• Owner-initiated self-update requests are sent to a third-party AI platform selected by the operator for inference. The selected AI and translation providers may change over time.
• The operator does not use Discord message content to train AI models. AI features use text to generate requested outputs, and translation features use text to produce translations. Third-party providers handle submitted text under their own current terms and privacy practices.

These providers process information to provide the requested feature. Zinging is hosted on Railway, and its persistent database is PostgreSQL. Railway states that its databases are encrypted at rest and that data in transit uses secure communication protocols.

Storage and retention

• Ask and code conversation sessions are held in application memory and expire 24 hours after the last message in a session.
• When a user asks Zinging to remember information, memory bullets may be saved with that user's Discord ID in the database. A user may have up to 50 bullets; older bullets are pruned as new ones are added.
• Translation preferences and server/channel settings are stored so they continue to work after a restart, until changed or removed.
• Owner-initiated update requests and related operational run records are stored in the database. There is no fixed automatic expiry configured for all such records.

Zinging's database does not keep a general archive of ordinary server messages. The bot processes message text for the features described above and reads recent Discord messages as context when a server has enabled cat banter. Discord separately retains messages under its own policies.

Choices and controls

Individual users cannot turn off automatic channel features for themselves; server administrators can disable automatic translation or cat banter in their server. Users can choose whether to invoke text commands or request a manual translation. Removing Zinging from a server stops its access there, but may not remove records already stored by the bot; use the contact below to request deletion.

Access, correction, and deletion requests

To ask what information Zinging has associated with you, or to request correction or deletion, email lakshaychawla13@gmail.com. Include your Discord user ID and enough detail to locate the relevant information, such as the server or feature. Do not send your password, authentication code, or bot token. We will verify the request and act promptly, subject to applicable legal requirements.

Security and changes

Zinging uses service-provider security controls for its hosted application and database. No online service can guarantee absolute security. This policy may be updated when the bot's data practices change; the current version will be published at this URL with its effective date.

Questions about this policy can be sent to lakshaychawla13@gmail.com.