Account Add to Discord (opens in a new tab)
Add to Discord (opens in a new tab)
Theme

Back to the home page

Privacy Policy: Ava (SetoChan)

Effective date: 26 June 2026
Last updated: 26 June 2026

This Privacy Policy explains what information the Ava Discord bot (“Ava”, “Ava Agent”, “the bot”, “the agent”, “we”, “us”, “our”) and its companion website/dashboard collect, how we use it, who we share it with, and the choices and rights you have.

Ava is operated by Simo (reachable through email: jumpursimo12@gmail.com), an independent developer. Ava is not a registered company. By adding Ava to a server, using its commands, chatting with it, or using the website, you acknowledge the practices described here.

If you do not agree with this policy, please stop using the bot and remove it from your server.

1. Quick Summary

  • We collect Discord identifiers (user, server, channel, and role IDs), limited profile data (username, avatar, account/join dates), and the content you send to the bot (commands, prompts, attachments, and facts you ask it to remember).
  • Your AI prompts and conversations are sent to a third-party AI provider (OpenRouter) and the underlying model providers to generate responses.
  • Server admins can enable features that store moderation records, ticket transcripts, and welcome/leave settings.
  • We use a payment provider (Gumroad) for paid tiers; we never see or store your full card details.
  • We do not sell your data and do not use it for advertising.
  • You can request deletion of your data at any time (see Section 10 and Section 11).

2. Who This Policy Covers

This policy applies to:

  1. The Ava Discord bot: its slash commands, the AI agent (/prompt), and all its features.
  2. The Ava website / dashboard at https://ava.simoapps.com/, including Discord login and subscription management.

Ava operates within Discord and is also subject to Discord’s Privacy Policy and Terms of Service. We do not control Discord.

3. Information We Collect

3.1 Discord identifiers and profile data

Collected automatically when you interact with the bot or it processes server events:

  • User IDs, server (guild) IDs, channel IDs, role IDs, and message IDs.
  • Username, display name / nickname, and avatar URL.
  • Account creation date and server join date (e.g. shown by /userinfo).
  • Member count and similar public server metadata.

3.2 Information you provide to the AI

When you use /prompt or chat with the agent:

  • The text of your prompts and messages.
  • Attachments you upload (up to 5 per message): images are passed to the AI as links; text files are downloaded and their contents are read and included in the request.
  • Conversation history within a session (short-term memory), kept to maintain context.
  • Long-term memories: facts the agent saves at your request or when you share something it determines is worth remembering (stored in the memories table until deleted).

3.3 Command inputs and moderation data

When you or your server’s moderators use commands:

  • Reasons, durations, nicknames, and message counts you supply to moderation commands.
  • Warnings (warnings) and a moderation case history (mod_cases): including the moderator ID, target user ID, action type, reason, duration, and timestamp.
  • Moderation log settings (mod_log_configs) and the log embeds posted to your chosen channel.
  • For /purge and similar actions, message content is processed transiently to perform the deletion; we do not store purged message contents.

3.4 Ticket data and transcripts

If a server enables the ticket system:

  • Ticket records (tickets): creator, channel, status, claimant, timestamps.
  • Ticket configuration (ticket_configs).
  • HTML transcripts of the messages in a ticket channel are generated when a ticket is deleted and sent to the server’s configured transcript channel. These transcripts contain the message content, authors, and timestamps of everyone who participated in the ticket.

3.5 Welcome / leave (greetings) data

  • Greeting configurations (greeting_messages): channel, message content, and embed settings created by server admins.

3.6 Usage, tier, and billing data

  • Preferred AI model, tier, ban status, and credit balance (users).
  • API usage records (usage_log): the model used, token counts, credits consumed, and timestamps.
  • Subscription and billing data (subscriptions, billing_events): your tier, billing interval, subscription status and dates, and payment event data received from our payment provider (Gumroad), which may include the email address and product/order information associated with your purchase. Raw provider webhook payloads may be stored (webhook_events) for reliability and fraud prevention.
  • We never receive or store your full payment card numbers. Payment processing is handled entirely by Gumroad.

3.7 Trusted-user lists

  • Server owners can grant bot access to specific users; these trusted user IDs are stored per server (trusted_users).

3.8 Website / dashboard data

If you use the website at https://ava.simoapps.com/:

  • Discord login (OAuth2): we request only the identify scope. From Discord we receive your user ID, username, and avatar. We do not request your email or your server list through Discord OAuth. The OAuth access token is used once to read your basic profile and is not stored.
  • Session cookie: after login we set a signed session cookie containing your Discord ID, username, and avatar to keep you logged in. This is a strictly functional cookie.
  • CSRF state (oauth_states): a temporary token created during login to protect the sign-in flow; it is automatically deleted within about 10 minutes.

3.9 What we do not collect

  • We do not collect your Discord email via OAuth (identify scope only).
  • We do not read or store the general contents of your server’s channels, only the specific content described above (your prompts/attachments, ticket transcripts on deletion, and data you submit to commands).
  • We do not store full payment card details.
  • We do not use tracking/advertising cookies or third-party analytics trackers.

4. How We Use Your Information

We use the information above to:

  • Provide the bot’s features: answer prompts, run tools, manage channels/roles, moderate, run tickets, and send welcome/leave messages.
  • Maintain context: short- and long-term memory so the assistant is useful across a conversation.
  • Operate moderation and logging that server admins enable.
  • Enforce limits and billing: track credits/usage, apply tier limits, and manage subscriptions.
  • Provide and secure the website/dashboard: keep you logged in and let you manage your subscription.
  • Respond to support requests sent via the contact form or support server.
  • Maintain security and integrity: prevent abuse, fraud, and violations of our terms; honor bans.
  • Comply with legal obligations where applicable.

We process this data because it is necessary to provide the service you requested, with your consent (e.g. memories you ask us to save, the contact form), and for our legitimate interest in operating, securing, and improving the bot.

5. AI Processing and Third-Party AI Providers

Ava’s intelligence is powered by external AI models accessed through OpenRouter, which routes requests to the underlying model providers (such as Anthropic, OpenAI, Google, DeepSeek, and others, depending on the model selected).

  • When you use the AI, your prompt, attachments, and relevant conversation/memory context are transmitted to OpenRouter and the selected model provider to generate a response.
  • This data may be processed and temporarily retained by those providers for the free models in accordance with their own privacy policies, over which we have no control. Please review their policies, including OpenRouter’s Privacy Policy.
  • We do not sell this data or use it to build advertising profiles. Whether your inputs are used by a provider to train models depends on that provider’s settings and policies.

Image generation (e.g. server icons) sends your text prompt to an AI image model through the same provider.

6. How We Share Information

We share information only as needed to run the service:

Recipient Purpose Data shared
Discord The platform Ava runs on All bot interactions occur through Discord
OpenRouter & underlying model providers Generate AI responses & images Prompts, attachments, conversation/memory context
Gumroad Process payments & subscriptions Purchase/subscription data; payment details go directly to Gumroad
Hosting / database provider Run the bot, website, and database Stored data, processed under our instructions
Other server members Tickets, moderation logs, greetings, and bot replies are visible in the relevant Discord channels Content posted in those channels

We do not sell your personal information and do not share it for third-party advertising.

We may disclose information if required by law, to enforce our terms, or to protect the rights, safety, and security of our users, the public, or the service.

7. Server Administrators and Shared Responsibility

Many features are controlled by the administrators of the server where Ava is used. When admins enable moderation logging, tickets, or welcome/leave messages, they decide what is collected and where it is posted, and they are responsible for informing their members and using these features lawfully.

  • Moderation records, ticket transcripts, and logs created in a server are associated with that server and are accessible to that server’s authorized staff.
  • If you have a concern about how a specific server uses Ava, please contact that server’s administrators. You may also contact us (see Section 13).

8. Data Retention

  • We retain data for as long as it is needed to provide the service, generally while Ava is in your server and/or your account is active.
  • We delete data upon request (see Section 11).
  • Transient data is short-lived: OAuth CSRF state is deleted within ~10 minutes, and short-term conversation memory is trimmed automatically and not permanently retained.
  • Some records may be retained longer where necessary to comply with legal obligations, resolve disputes, prevent fraud/abuse, or enforce bans.
  • When you remove the bot from a server, you may request deletion of that server’s stored configuration and records.

9. Data Security

  • Data is stored in a PostgreSQL database with access restricted to the operator and the systems that run the service.
  • Connections to Discord, AI providers, and the payment provider use encrypted (HTTPS/TLS) channels.
  • Website sessions use signed cookies, and the sign-in flow is protected against CSRF.

No method of transmission or storage is 100% secure. While we take reasonable measures to protect your information, we cannot guarantee absolute security.

10. Your Rights and Choices

Regardless of where you live, you can ask us to:

  • Access the personal data we hold about you.
  • Correct inaccurate data.
  • Delete your data (“right to be forgotten”).
  • Export a copy of your data in a portable form.
  • Object to or restrict certain processing, and withdraw consent where processing is based on consent.

You also have in-product choices:

  • Memories: ask the agent to list, edit, or delete saved memories at any time.
  • Confirmation prompts: toggle confirmation before destructive AI actions (/confirm).
  • Stop processing: end a running agent session with /stop or /stopall.
  • Website: log out at any time to clear your session.

Depending on your country (for example, if you are in the European Economic Area, the United Kingdom, Morocco, or California), you may have additional statutory rights and the right to lodge a complaint with your local data protection authority. We honor these requests regardless of location.

To exercise any right, contact us using Section 13. We may need to verify your Discord ID to process the request.

11. How to Delete Your Data

You can have your data removed by any of these means:

  • Ask the agent to delete the memories it holds about you.
  • Contact us at jumpursimo12@gmail.com or via our support server and request deletion of your account/usage data. Include your Discord user ID.
  • Server admins can remove server-specific data by deleting the relevant configurations (greetings, tickets, moderation log settings) and removing the bot from the server, or by contacting us.

We will action verified deletion requests within a reasonable time, except where we must retain certain records for legal, security, or fraud-prevention reasons (e.g. billing records or active bans).

12. Other Important Information

12.1 Children’s Privacy

Ava is not directed to children. You must meet Discord’s minimum age requirement (at least 13, or older where your country requires it) to use Discord and Ava. We do not knowingly collect data from anyone below the required age. If you believe a child has provided us data, contact us and we will delete it.

12.2 International Data Transfers

Ava relies on services (Discord, AI providers, the payment provider, and hosting) that may process and store data in countries outside your own, including outside Morocco and the EEA. By using Ava you understand your information may be transferred to and processed in those countries, which may have different data-protection laws.

12.3 Cookies

The website uses a single functional session cookie to keep you logged in after Discord sign-in. We do not use advertising or third-party tracking cookies.

12.4 Changes to This Policy

We may update this policy from time to time. When we make material changes, we will update the “Last updated” date above and, where appropriate, announce it on the support server. Continued use after changes take effect constitutes acceptance.

13. Contact Us

For privacy questions, requests, or complaints:

We will do our best to respond to all legitimate requests in a timely manner.

Questions? Ask in the support server (opens in a new tab).