.png)
1. Scope
This Privacy Policy applies to Chirp-operated services, including the Chirp account and dashboard, Browse, Games or Work, Chirp Chat, Chirp AI, Chirp Remote Desktop, Chirp Bios, calls, profiles, servers, virtual items, integrations and related features.
Third-party websites, games, integrations, identity providers, payment processors and services linked from Chirp have their own privacy practices.
2. Information Chirp can process
Account and identity information
This can include your email address, username, display name, profile information, avatar, banner, account settings, age or eligibility information where required, authentication methods, linked identities and account status.
Security and device information
This can include IP address, user agent, device or browser information, session identifiers, login history, security events, two-factor authentication state, passkeys, recovery information, rate-limit data and abuse-prevention signals.
Content you provide
This can include messages, server posts, direct messages, threads, reactions, profile and Bio text, uploaded files, images, audio, stickers, emojis, server assets, reports, support requests, AI prompts and files submitted to AI features.
Usage and settings
This can include features you use, server memberships and roles, friends, blocks, notifications, virtual-item ownership, server support activity, feature settings, recent activity, and browsing or game history when those history features are enabled.
3. How Chirp uses information
Chirp uses information to operate the Services, authenticate accounts, deliver messages and media, provide AI results, connect Remote Desktop sessions, remember settings, maintain virtual balances and entitlements, process purchases, prevent abuse, secure accounts, investigate reports, troubleshoot bugs, measure reliability, and improve product functionality.
Chirp may also use aggregated or de-identified information to understand feature usage and system performance when that information no longer reasonably identifies an individual user.
4. Chirp Chat, profiles and community data
Your profile information can be visible to other users according to the product’s visibility rules. This can include your display name, username, avatar, banner, bio, badges, cosmetics, server tag, status and other profile customizations.
Messages and media are processed and stored as necessary to deliver Chat. Server content is visible to users with access to the relevant server, channel, forum or thread. Direct-message content is visible to participants and can be processed for delivery, safety, abuse prevention and support.
Server owners and moderators can access moderation features and information made available to them by Chirp. Reports can include relevant content and context needed to review the report.
Voice, video and screen sharing are processed in real time as necessary to connect participants. Participants can see or hear what you choose to transmit.
4A. Chirp Bios
A Chirp Bio is a public profile page tied to your Chirp username. Information you choose to place there, such as a display name, description, images, background media, audio and links, is intended to be publicly viewable and can be accessed without signing in.
When someone opens a Bio, Chirp can record the page view, an approximate visitor identifier derived from network and browser information, and a broad device category. This information is used to show the Bio owner basic analytics such as views, approximate unique visitors and device mix.
Bio appearance choices are separate from your private Chirp dashboard theme. Your dashboard theme is not published as part of your Bio.
5. Chirp AI, memory and generated content
When you use Chirp AI, Chirp processes your prompts, conversation context, attached files, available memory and any connected-service information needed for the request.
Chirp may send the information necessary for an AI request to third-party AI model providers. Those providers process the information to return model output and are subject to their own contractual and privacy obligations.
If a memory feature is enabled, Chirp can store selected context so future AI conversations are more useful. Memory can include preferences, project context and other information produced from prior use. Controls for memory may be offered in account or AI settings.
Do not put highly sensitive information into AI prompts unless it is necessary for the task and you are comfortable with it being processed to provide the feature.
6. Connected apps and integrations
If you connect an external account, Chirp can receive authorization tokens, account identifiers and data permitted by the scopes you approve. Depending on the integration, this can include email, calendar events, files, tasks or other connected information.
Chirp uses connected information to perform the action you request and support features you enable. Disconnecting an integration stops future access through that connection, subject to data already stored for legitimate account, security or history purposes.
The connected provider separately controls its own service and privacy practices.
7. Browse, Games and activity history
Browse can process requested URLs, search terms and technical information needed to retrieve or display web content. External websites can receive network and browser information when their content is accessed.
Chirp can save browsing history or game activity if the corresponding history setting is enabled. History controls in Chirp may allow you to view or clear saved activity.
Third-party websites and games can collect information directly from you under their own privacy policies.
8. Chirp Remote Desktop
Chirp Remote Desktop processes device registration information, device-specific authentication credentials, connection state and session metadata needed to connect your registered computers.
During a remote session, Chirp may relay desktop frames, audio, keyboard input, pointer input and control events between the registered computer and authenticated viewer. This content is processed to provide the session. Chirp may retain limited diagnostic or security metadata about the session, such as timestamps, device identifiers and connection events.
Only register or access computers you own or are authorized to control.
9. Chirps, purchases and payment information
Chirp stores information needed to maintain Chirps balances, virtual-item ownership, shop purchases, server support, subscription entitlements and transaction history.
If paid features are offered, payment information may be collected by an external processor such as Stripe. Chirp can receive transaction identifiers, purchase amount, currency, payment status and limited billing details needed to fulfill or support the purchase. The processor handles full card details according to its own privacy policy.
12. Data retention
Retention depends on the type of information and why it is needed. Account information can be kept while your account is active. Messages, uploads, histories, security records, transaction records and connected-service data can have different retention periods.
When information is deleted, copies can remain temporarily in backups or logs. Chirp can also retain information when reasonably necessary for legal compliance, security, fraud prevention, disputes, payment records or enforcement.
Where a product setting offers a clear or delete action, using it removes the information covered by that control from active product use subject to the limitations above.
13. Security
Chirp uses account authentication, access controls, session management and other technical measures intended to protect information. No online service can guarantee perfect security.
Use a unique password, enable two-factor authentication where available, protect recovery codes, review account sessions and keep registered Remote Desktop devices secure.
14. Your choices and controls
Depending on the feature, Chirp can provide controls to edit profile data, change privacy settings, clear history, disconnect integrations, manage sessions, block users, leave servers, delete content, remove devices, change AI memory settings or request account data.
If a requested privacy action is not available directly in settings, use the support or contact method provided inside Chirp. Applicable law may give you additional rights to access, correct, delete or receive a copy of personal information, or object to certain processing.
15. Age requirements
Chirp is not intended for anyone below the minimum age permitted by applicable law.
If Chirp learns that personal information was collected from a user who was not legally permitted to use the Service, we may restrict the account and delete information as required by law.
16. International use
Chirp and its service providers may process information in countries other than the one where you live. Privacy laws can differ between countries. When required, appropriate legal mechanisms should be used for cross-border processing.
17. Changes to this Policy
Chirp may update this Privacy Policy as features, service providers or legal requirements change. Material changes will be communicated through Chirp or another reasonable method when required. The “Last updated” date identifies the current version.
Questions
For privacy questions or requests, use the support or contact method made available inside Chirp. The Terms of Service contain the rules for using Chirp.