Official Freesona Instances Privacy Policy
How your information is collected and used for Freesona-based bot instances operated by Quincy So
This Privacy Policy applies only to Freesona-based bot instances operated by Quincy So.
Because Freesona is publicly available, anyone may host their own independent instance with different configurations, logging practices, storage choices, or privacy policies.
If you are interacting with a Freesona-based bot that is not operated by Quincy So, this Privacy Policy does not apply to that instance.
1. Information We Collect
When you use a Freesona-based bot instance operated by Quincy So, we may collect the following types of information:
- Messages and commands — content you send to the bot, including slash commands, prefix commands, and direct messages in configured conversation channels.
- Server and user identifiers — Discord guild (server) IDs and user IDs needed to provide per-server configuration, per-user memory isolation, and command routing.
- Long-term memory facts — the bot may automatically extract and store facts about you (e.g., name, interests, projects) from your messages. These facts are stored locally in a SQLite database, keyed by your Discord user ID and guild ID, and are used to personalize future interactions. You can view, delete, or clear your stored facts at any time using
/memorylist,/memorydelete, and/memoryclear. - File attachments — images, PDFs, audio, video, and code files you send to the bot are transmitted to the configured AI provider for multimodal processing. Audio files may also be processed by MVSEP for vocal/instrumental separation. Media URLs may be processed via YouTube data extraction.
- Knowledge base content — server administrators may add documents (text, PDFs, EPUBs) to an optional local ChromaDB knowledge base. This content is stored locally and queried semantically during AI generation.
- RSS feed data — if RSS feeds are configured, the bot fetches and stores feed metadata (feed name, URL, latest item data) for auto-posting to designated channels.
- Diagnostic and error information — logs and error data used to debug issues and improve reliability.
2. How We Use Information
Collected information is used for the following purposes:
- Operating the bot and responding to your requests
- Personalizing AI responses using your stored memory facts and the configured persona
- Providing semantic knowledge retrieval from the local ChromaDB knowledge base
- Enforcing server rules and these Terms of Service
- Debugging issues and improving performance
- Delivering RSS feed updates to configured channels
We do not sell personal data. We do not use your data to train AI models.
3. Data Sharing
We may share limited data with third-party services that are necessary to fulfill your requests:
- AI providers — messages, persona instructions, memory facts, knowledge base chunks, and file attachments are transmitted to the configured AI provider (Google Gemini, OpenAI, Ollama, NVIDIA NIM, Azure AI Foundry, Groq, or OpenRouter) to generate responses.
- Audio processing — audio files submitted for separation are transmitted to MVSEP.
- Web search — search queries are transmitted to a web search API for retrieval.
- Media extraction — YouTube and other media URLs may be processed via yt-dlp for metadata and content extraction.
- Hosting infrastructure — data passes through hosting providers (e.g., Railway, Render, or self-hosted infrastructure) necessary for bot operation.
Each third-party provider is subject to its own privacy policy and terms. We are not responsible for their data practices.
4. Data Retention
We retain data only as long as needed for operation, security, or legal obligations:
- Memory facts — stored in a local SQLite database (
memory.db) until you or a server administrator deletes them, or until the bot is removed from the server. Capped at 20 facts per user. - Knowledge base entries — stored in a local ChromaDB collection until a server administrator deletes them via
/kbdelete. - RSS feed data — retained while the feed is configured; removed when the feed is deleted via
/rss remove. - Interaction logs — retained as needed for debugging and may be pruned periodically.
You may request deletion of your memory facts at any time using /memoryclear. For other data deletion requests, contact the operator through the designated support channels.
5. Your Choices
- Manage your memory — use
/memorylistto view stored facts,/memorydeleteto remove specific facts, and/memoryclearto clear all your facts. - Avoid sharing sensitive information — do not send messages or files containing personal data you do not wish to be processed by AI providers or third-party services.
- Server administrators — may disable autonomous mode, clear channel history, manage knowledge base entries, and apply their own moderation policies.
- Do not use the bot — if you do not agree with these data practices, you may choose not to interact with the bot.
6. Changes to This Policy
This Privacy Policy may be updated at any time. Continued use of the bot means you accept any changes to this policy.
7. Contact
For questions or privacy-related requests, contact the operator through the designated support channels.