1. What Quasr.AI Processes
Quasr.AI is a Discord-based AI assistant. Depending on the feature being used, Quasr may receive information needed to identify the interaction, determine where the request came from, apply permissions or service limits, and generate a response.
- Discord identifiers: information such as Discord user IDs, server/guild IDs, channel IDs, message IDs, and related identifiers may be processed when necessary to operate Discord features.
- Message and prompt content: text that you send to Quasr, including a message that mentions Quasr or a prompt entered through a supported command, may be processed to generate an AI response.
- Context: when a feature needs conversational context, relevant recent Discord messages may be read for processing. The exact context available depends on how the feature is implemented and what Discord permissions allow.
- Usage and service data: Quasr may process information needed to enforce feature access, daily or rolling limits, membership status, anti-abuse controls, and operational reliability.
2. Mention-Only AI
For the normal Discord experience where Quasr responds when it is mentioned, the bot processes the message that triggered the interaction and, where needed, relevant recent context to understand what the user is asking.
The purpose of this processing is to turn the user's request into an AI response. Quasr does not need to continuously read every channel merely because the bot is installed. A message becomes relevant to Quasr when the bot is invoked by the applicable feature and Discord permissions allow the required context to be read.
Where the request is forwarded to an external AI infrastructure provider, the message content and necessary context may leave Quasr's own process temporarily so the provider can generate the requested response.
3. AurInfer-Powered AI Processing
Some Quasr AI capabilities are powered through AurInfer. In those flows, Quasr sends the information required to AurInfer so its service can process the request and return an AI result.
For example, a user's prompt may be transformed into a request containing the prompt, relevant conversation context, and technical information needed to identify the request. AurInfer then routes that request through its AI infrastructure and returns the generated result to Quasr, which delivers the response back through Discord.
According to AurInfer's current Privacy Policy, AurInfer states that raw message content and other real-time interaction data are discarded after a response is generated and delivered by default, outside specified exceptions such as usage logs, security identifiers, moderation metadata, integration credentials, and its optional Core Memory system. AurInfer also states that it uses Zero Data Retention (ZDR)-compliant vendors for AI model calls and that conversations and generated content are not used to train AI models. These are AurInfer's stated policies, not a guarantee that Quasr can control or alter AurInfer's systems.
For the most current details about AurInfer's handling of data, users should review the AurInfer Privacy Policy.
4. Ask-Pro
Ask-Pro is an advanced Quasr feature that may route a user's request through a more capable AI path. When a user uses Ask-Pro, the prompt and the context required to answer it may be processed by Quasr and by the AI infrastructure/provider used for that Ask-Pro request.
Ask-Pro access can also require service-side checks such as Discord membership or usage-limit enforcement. Those checks may use Discord identifiers and usage information so Quasr can determine whether the user is eligible to use the feature and whether an applicable limit has been reached.
Ask-Pro does not mean that Quasr automatically owns or permanently stores the entire conversation. The actual handling of the prompt depends on the infrastructure path used for the request. Where AurInfer is the processing layer, AurInfer's current Privacy Policy describes real-time interaction data as zero-retention by default, subject to the exceptions stated in that policy.
Quasr may retain limited operational information needed to provide the feature, such as access or usage records, if such records are implemented for quotas, abuse prevention, debugging, or service integrity. Quasr should not be understood as promising that every technical log is automatically deleted immediately unless this Policy specifically says so.
5. What Happens to a Typical AI Request?
- You invoke Quasr by mentioning the bot or using a supported command/feature.
- Discord delivers the event and the information Quasr needs to identify the user, server, channel, and request.
- Quasr prepares the request by applying the relevant feature rules, permissions, limits, and available context.
- The AI request is processed by the configured AI infrastructure. For AurInfer-powered features, AurInfer receives the information necessary to process the request.
- The AI result returns to Quasr and Quasr sends the response back to Discord.
- Retention depends on the layer: real-time prompt content may be transient, while operational records, usage records, security information, or provider-side records may follow the applicable retention policy of the system that handles them.
6. Data We Do Not Need to Collect
Quasr is not designed to require sensitive information such as passwords, payment-card numbers, government identification documents, or a user's Discord account password in order to use the normal bot features. Users should not intentionally provide sensitive personal information to an AI prompt unless it is genuinely necessary and they understand the risks of sending it to an AI service.
7. Third-Party Services and AurInfer
Quasr operates on and may depend on third-party services, including Discord and AurInfer. Depending on the feature, additional infrastructure or AI providers may be involved through the service provider used by Quasr.
For requests processed through AurInfer, the applicable AurInfer Privacy Policy, Terms of Service, and Guidelines also apply to AurInfer's handling of the request. Quasr.AI is an independent project and does not own or control AurInfer's infrastructure or third-party model providers. Quasr's Privacy Policy describes Quasr's intended handling and the AurInfer practices that AurInfer publicly states; it does not replace AurInfer's own policies.
Third parties may process information according to their own policies. Quasr cannot guarantee or override a third party's independent systems, retention practices, security controls, or legal obligations.
Discord remains responsible for its own handling of Discord account and platform data under Discord's policies and terms.
8. Storage and Security
Quasr aims to minimize stored user information and only retain information that is necessary for operation, access control, service limits, security, troubleshooting, or other legitimate service purposes.
Where data is stored by Quasr-controlled systems, reasonable technical and organizational measures should be used to protect it against unauthorized access, alteration, disclosure, or loss. However, no online system can be guaranteed to be completely secure.
Information processed by AurInfer or another provider is protected and retained according to that provider's own systems and policies. AurInfer currently states that stored data such as usage logs, security identifiers, and other specified records are protected using encryption in transit and at rest.
9. Retention and Deletion
Quasr does not promise a single universal retention period for every category of data because different information has different operational purposes.
- AI prompt/output content: may be processed transiently to generate a response and, when handled through AurInfer, is subject to AurInfer's stated zero-retention default and its listed exceptions.
- Usage/access records: may be retained when needed for quotas, membership checks, abuse prevention, diagnostics, or service reliability.
- Discord identifiers: may remain in operational records for as long as needed for the associated service function or security purpose.
- Provider-side data: follows the applicable provider's privacy policy and retention practices.
If you want a specific piece of Quasr-controlled data reviewed or deleted, contact the Quasr.AI team through the official support/community channel. Requests may be subject to legitimate security, legal, or operational retention requirements.
10. AI Training
Quasr does not represent that every third-party AI provider has identical data practices. For AurInfer-powered processing, AurInfer's current Privacy Policy states that conversations, messages, tool usage, and other generated content are not used to train or fine-tune AI models and that its model providers are selected on a Zero Data Retention basis. This statement applies to AurInfer's stated practices and may change if its policy changes.
Quasr does not independently claim that data sent to every possible AI provider is covered by the same policy. Where a different provider is used, its applicable privacy terms may differ.
11. Children's and Teen Users
Quasr is used through Discord and therefore must be used consistently with Discord's age requirements and applicable law. Quasr does not ask users to submit government ID, passwords, or other sensitive identity information as part of normal AI use. Users under the age of majority should use the service in accordance with the requirements that apply to them, including any parent or guardian requirements imposed by the relevant platform or law.
12. Your Choices and Requests
You can choose not to send personal or sensitive information in prompts. You can also stop using Quasr or remove the bot from a server. For requests concerning information controlled by Quasr, contact the Quasr.AI team through the official community/support channel and describe the request clearly.
For information handled directly by AurInfer, requests may also be directed to AurInfer under its own Privacy Policy. AurInfer currently lists support@aurinfer.com for privacy and data-protection requests.
13. Changes to This Privacy Policy
This Privacy Policy may be updated when Quasr's features, infrastructure, data practices, or legal requirements change. The latest version will be published on this page with an updated date. Material changes should be reviewed before continuing to use the affected features.
14. Contact
For questions about how Quasr.AI handles information, contact the Quasr.AI team through the official community/support channel linked from the website.
This policy describes Quasr.AI's intended data handling and the third-party practices explicitly referenced above. It is not a substitute for the privacy policies of Discord, AurInfer, or other third-party services.