Introduction
Welcome to Muzza (muzza.ai), operated by the company. This policy explains what data we collect when you use the platform and how we protect it.
Data We Collect
We collect only the data the service needs:
- Account data: your email address, used to create your account and log in. When signing in via an external account, we only receive the identifier and username.
- Chat data: your conversation content, stored to provide the chat experience and protected by strict access controls. We do not sell your conversation content or use it for advertising.
- Generated images: metadata about images you create (such as date and associated character) and the generated media needed to provide your collection and image features.
- Payment data: transaction history, prepaid-access status, Token balance, provider invoice references, and payment status. The Stars payment itself is processed by Telegram under its own policy.
- Usage and analytics data: page views, product and funnel events, referral source, approximate region, and device/browser information. These signals may be associated with pseudonymous analytics or visitor identifiers.
- Visitor, security, and operational data: a pseudonymous visitor ID sent to our server with a hash derived from the trusted request IP for journey continuity, earned-Token attribution, fraud prevention, rate limiting, and aggregate measurement. We may also process IP addresses, request/error identifiers, timestamps, and reliability signals for security and operations.
Generated-content memory
The platform uses a generated-content memory system to improve conversation quality. It stores summaries derived from your interactions. These summaries are account-, conversation-, and persona-linked data; they are not anonymous. This memory:
- Is linked to your account only and isolated from other users.
- May contain details summarized from your conversations with a character.
- Is shared across the stories you play with the same character, so the character remembers your relationship from story to story.
- Can be forgotten on request: choosing Forget me clears everything that character has learned about you across all your stories, and deleting a story forgets what was learned in that story.
- Is scheduled for deletion with your account, subject to the retention limits below.
Chat Storage
Conversation content is protected by strict access controls and stored only as needed to provide the chat experience, abuse handling, and account features. We do not sell conversation content or use it for advertising.
Authorized Muzza dashboard administrators can read conversation content when needed for support, safety, abuse investigation, or product-quality review. Every transcript view is recorded automatically.
We do not use your chats for model training, fine-tuning, or evaluation unless you give a separate explicit opt-in.
Sex Chat
Sex Chat is an anonymous text chat area inside Muzza. Conversations run between real adult users: the other party in a Sex Chat conversation is a real adult user, never an automated character. Automated characters elsewhere on the platform remain fiction and never a real person. Sex Chat has its own data and checks, described in this section.
When you use Sex Chat, we additionally collect and store:
- Your profile: the name, gender, picture, and short bio of your one Muzza profile as shown in Sex Chat.
- Your likes and the matches they create.
- Your Sex Chat messages and chat requests.
- The applause you give or receive, and your friends list.
- Your presence status (online or offline).
- Your account status: Sex Chat actions require a registered, confirmed adult account; no birth year is collected.
- Violation and lockout records produced by the automated checks described below. Lockouts apply to Sex Chat only.
- Report metadata when you report a Sex Chat conversation.
Anonymity: other users never see your account identity, such as your email address. What other users can see is your profile card (name, gender, picture, and short bio), your applause badge, your presence status, and the chat itself. Contact details are blanked from the profile card. This separation is enforced by strict row-level security at the database level.
Automated checks on every Sex Chat text: every text connected to Sex Chat, including chat messages, chat requests, and the profile names and bios shown in Sex Chat, is checked automatically before it is stored or delivered. The checks look only for ways to break anonymity: contact routes, attempts to move the chat off the platform, meet-up arrangements, and identifying details. They do not judge themes, tone, or content. Text that fails a check is not delivered, and if the checks are unavailable, the text is not sent. Blocked or rephrased texts are stored as a record for review and enforcement, visible to operators only.
The checks run through an automated text-classification provider, with a backup routing provider used only when the first is unavailable. A check sends the text being checked, a normalized copy of it, and recent messages from the same conversation, from both users, as context. The provider returns a classification only.
Storage and archive: Sex Chat messages are encrypted at rest. Chats stay open until one user deletes the chat or blocks the other. Deleting a chat removes it for both users, and neither user can read a deleted or blocked chat again. There is no archive or export of Sex Chat chats. Deleted chats and stopped texts stay stored, encrypted, for operator review.
Operator access: Muzza operators can see Sex Chat conversations, both users' accounts, and stopped, undelivered texts, for safety, abuse reports, and legal compliance.
Retention: Sex Chat chats and related Sex Chat records are kept until your account is deleted, then erased; the backup rotation periods described in the Account Deletion section apply.
Push notifications: with your opt-in, Sex Chat replies are notified through Telegram and browser push. Notifications carry no message content.
Reports: Sex Chat reports are reviewed by moderators. A report stores metadata only; moderators read the conversation itself.
Analytics and Tracking
Google Analytics and its site-speed measurements run by default. Privacy settings is the off switch: turning them off unmounts the trackers and keeps them off on later visits, and you can turn them back on there at any time. Essential server-side payment, entitlement, security, abuse-prevention, and reliability records still operate so we can provide and protect the service.
- Product analytics are on by default and can be turned off in Privacy settings.
- An explicit opt-out in Privacy settings unmounts the trackers, and that choice is applied on later visits.
Push Notifications
You can optionally enable push notifications. When you do, we store an account-linked push endpoint, the cryptographic keys used to secure the notification channel, and related browser/device and operational identifiers needed to deliver and manage notifications. You can turn notifications off from your account settings or browser controls. Notification delivery also sends the notification title and body to the push service for your device.
Third-Party Service Providers
We use third-party service providers to operate the platform. Each provider receives only the data it needs to perform its function:
Live voice calls (where offered): a live voice call requires a versioned processing consent that you accept first. The consent covers the processing, the provider handling and retention of call data, live captions, and the optional transcript. During a call, your speech is converted to text automatically by our contracted live-voice provider, and the character reply is synthesized audio. Muzza does not store the raw audio recording. Captions are shown live and are not stored unless transcript saving is on. The transcript is optional and off by default; when enabled, the final transcript is stored encrypted with the chat. The provider may retain call data under its approved terms, and we ask for your consent again if the provider or the retention terms change. You can withdraw your consent at any time; withdrawal stops future calls and transcript saves and ends any active call.
- Database hosting and authentication: our own servers in Frankfurt, Germany (European Union), operated by us
- Website hosting and content delivery: the website runs on managed hosting behind a content delivery network (CDN) and firewall
- Automated text generation: a contracted automated text-generation provider powers character conversations
- Generated-content memory system: processing account-, conversation-, and persona-linked summaries to improve conversations
- Image generation: automated image-generation services used to create requested media
- Payment processing: Telegram processes Telegram Stars payments and the associated transaction data under its own policy
- Live voice calls (where offered): a contracted live-voice provider processes call speech under the versioned consent described in this policy
- Public media moderation: an automated moderation provider checks public gallery and roster media
- Optional browser analytics providers: Google Analytics and its site-speed measurements run by default and can be turned off in Privacy settings.
- Visitor and device signals: pseudonymous identifiers used to connect visitor journeys, attribute earned Tokens, prevent abuse, and produce aggregate statistics
- Email service: verification messages and password resets
- Sex Chat anonymity checks: an automated text-classification provider checks Sex Chat texts, with a backup routing provider used only when the first is unavailable; see the Sex Chat section
- Advertising attribution: if you arrive through one of our ads, we tell that ad network when your visit leads to a first paid chat message, using only the network's own click identifier. No other personal data is sent.
Account Deletion
Account settings opens a support-assisted request addressed to [email protected]. Send it from the account email. Support verifies identity and scope, then confirms receipt and the next steps; opening the draft alone does not disable access or start deletion. Once an accepted request is processed, encrypted backups expire on their rotation schedule (base backups are kept about 14 days and off-site copies about 16 days), and limited records may be retained where needed for payment reconciliation, fraud prevention, safety reporting, dispute handling, or applicable law. The request may cover these account-linked categories:
- Your email address and account data
- Conversation records associated with the account
- Generated images and your collection
- Payment history and token balance
- Prepaid-access data
- Generated-content memory linked to your account
- Push notification subscriptions
Your Rights
Under the General Data Protection Regulation (GDPR) and applicable laws, you have the following rights:
- Right of access: You can request a copy of your personal data stored with us.
- Right to rectification: You can request correction of any inaccurate data.
- Right to erasure: You can request account deletion or erasure, subject to applicable legal and retention limits.
- Right to data portability: You can request an export of your data in a machine-readable format.
- Right to object: You can object to the processing of your data for specific purposes.
- Right to withdraw consent: You can withdraw your consent to data processing at any time.
Account Settings also provides a limited self-service core JSON export containing your profile, readable conversation text, payment-intent history, and privacy-request history. It does not currently include binary images, generated-content memory, or every other account-linked category. For a complete access request, contact [email protected].
To exercise any of these rights, contact us at [email protected]. We will acknowledge and handle your request within the time required by applicable law. If you need confirmation or believe account-linked data remains after deletion, email us from the account address so support can follow up.
Child Protection
Muzza is intended for adults only (18 years or older). We do not knowingly collect data from minors. If we become aware that a user under 18 has created an account, we will disable the account immediately and handle associated data under applicable safety, reporting, and retention duties. If you believe a minor is using the platform, report it to [email protected].
Data Breach Notification
If a security breach affects your personal data, we will:
- Notify affected users without undue delay when applicable law requires it.
- Report to relevant authorities within the deadlines required by applicable law.
- Explain the nature of the breach, the data affected, and the measures taken to address it.
- Provide recommendations to protect your account.
Security
We implement strict security measures to protect your data:
- TLS encryption for all data in transit.
- Strict access controls for conversation content.
- Encrypted storage of data on servers in the European Union.
- Logging minimization and restricted access to operational logs, which may contain IP, request, error, or pseudonymous identifiers needed for security and reliability.
- Strict row-level security (RLS) policies at the database level.
Policy Updates
We may update this privacy policy from time to time. We will notify you of any material changes via email or a notification on the platform. We recommend reviewing this page periodically.
Contact
If you have questions about this policy or how we handle your data, contact us at: [email protected]