Quantium Service Privacy Policy

Effective Date: March 25, 2026

1. General Provisions

  1. This Privacy Policy outlines what data the Quantium service, available via the Telegram bot @quantium_aibot, collects, how it's used, stored, transferred, and protected.
  2. In this Policy, the Quantium service is referred to as the "Service."
  3. This Policy applies to all users of the Quantium Telegram bot, related service web pages, public legal pages, and administrative and technical components, unless explicitly stated otherwise.
  4. By using the Service, you confirm you've read this Policy and agree to its data processing rules.

2. What Data We Process

We may process the following data categories:

  1. Telegram Account Data: Telegram ID; username; profile first and last name; interface language; technical account attributes available via the Telegram API.
  2. Bot Interaction Data: User messages and bot responses; commands, button presses, selected settings, language, time zone, and current preferences; dialogue history, session info, support requests, and in-interface actions.
  3. User Content: Text, documents, links; images, audio, voice messages, video, and other files if you send them to the bot.
  4. Payment and Product Data: Info on selected plans, credit packs, subscriptions, and their validity periods; history of credit accrual, reservation, debiting, refunding, and expiration; payment statuses, transaction IDs, payment method, currency, technical payment tags; info on partner accruals and payout requests if you're in the partner program.
  5. Technical Data: Error and event logs; internal request IDs; data needed for service protection, abuse prevention, and diagnostics.

3. Data Sources

We get data:

  1. directly from you when you use the bot;
  2. from the Telegram platform within the limits allowed by its API and your user settings;
  3. from payment providers as needed to confirm and record payments;
  4. from AI providers and technical contractors as processing results, statuses, errors, and service responses;
  5. from internal service analytics and logs.

4. Purposes of Data Processing

We process data for these purposes:

  1. user registration and granting service access;
  2. processing user requests and generating AI responses;
  3. generating text, images, audio, video, and other results based on your request;
  4. storing dialogue history, actions, and support requests;
  5. calculating, accruing, debiting, refunding, and auditing internal credits;
  6. processing, renewing, changing, and terminating subscriptions;
  7. processing and confirming payments, preventing fraud, and performing financial accounting;
  8. handling support requests and service notifications;
  9. improving service quality, error diagnostics, ensuring security, investigating abuse, and product development;
  10. complying with legal, accounting, and tax requirements, and protecting the Service's rights and legitimate interests.

5. Legal Basis for Processing

Depending on the situation, data processing relies on one or more of these grounds:

  1. performing the user agreement and providing access to Service features;
  2. the Service's legitimate interest in ensuring operations, security, analytics, support, and product development;
  3. your consent, where required by applicable law;
  4. fulfilling legal obligations.

6. Use of AI Providers and Third-Party Services

  1. For service functions to work, user requests and related content may be sent to external AI providers and technical contractors.
  2. The service's current architecture may use providers from these categories:
    • Telegram, as a platform for message delivery and Telegram Stars payments;
    • OpenAI for specific text, multimodal, audio, and video features;
    • xAI for specific text, graphic, audio, and video features;
    • other payment and infrastructure providers connected to the service as the product evolves.
  3. These providers may process data sent to them according to their own rules and policies.
  4. The service can send these providers the necessary data to fulfill user requests, process payments, ensure delivery, prevent abuse, and keep the service running.

7. Payments

  1. The service generally doesn't store full user bank card details unless a connected payment provider or applicable law explicitly requires it.
  2. Payment data gets processed by relevant payment providers and platforms, including Telegram Stars and other connected external payment solutions.
  3. We may store technical payment details like amount, currency, date, status, transaction ID, payment type, and service data needed for payment confirmation, support, and audit.

8. Data Storage and Retention

  1. We store data for as long as reasonably needed to run the service, support users, for internal accounting, dispute resolution, abuse prevention, and legal compliance.
  2. In its current product model, the service might keep a full history of user messages and bot responses; AI request history; payment, subscription, and credit transaction history; support requests and related messages; technical logs, and internal security events.
  3. To optimize model performance, the service might separately store brief summaries of past conversations, persistent user preferences, and other memory elements needed to improve context.
  4. Older data can be stored long-term, moved to colder storage, aggregated, anonymized, or deleted at the Service's discretion, unless law requires otherwise.

9. Data Transfer to Third Parties

We may transfer data to:

  1. technology contractors and AI providers required for service functions;
  2. payment providers, banks, payment platforms, and anti-fraud services;
  3. hosting and infrastructure providers;
  4. professional consultants, auditors, and those providing legal and technical support for the Service;
  5. government authorities and others if such transfer is legally mandated or necessary to protect the Service's rights.

We don't sell user personal data to third parties as a standalone product, but we can use contractors and external services to run our product.

10. Cross-Border Transfer

  1. Since Telegram, AI providers, hosting, and payment infrastructure might be in different countries, user data could be transferred and processed outside their country of residence.
  2. By using the service, you understand and accept this potential cross-border transfer, to the extent needed for the service to function.
  3. Where applicable law requires, the Service takes reasonable steps to legally organize such transfers but doesn't guarantee the same level of regulation in all jurisdictions.

11. Security

  1. We take reasonable organizational and technical steps to protect data from loss, unauthorized access, alteration, disclosure, or destruction.
  2. These steps might include access control, administrative interface authorization, internal tokens, event logs, backups, request rate limiting, and other standard security practices.
  3. No storage or transmission method over the internet is 100% secure. You use the Service at your own risk.

12. User Rights

Subject to applicable law, you can:

  1. request information about your data processing;
  2. ask us to correct inaccurate data;
  3. withdraw consent if processing relies solely on it;
  4. request data deletion or processing restrictions if there's a legal basis;
  5. object to certain processing methods based on legitimate interest;
  6. file a complaint with the relevant data protection authority if legally allowed.

To exercise these rights, contact us only through the built-in ticket system within the Quantium Telegram bot: @quantium_aibot. Before fulfilling a request, we may ask for information needed to verify your identity and protect your account from unauthorized access.

13. Children's Data

This Service isn't for use by individuals under the age permitted by applicable law and Telegram's rules for independent use of such digital services without necessary parental consent.

14. Cookies and Web Pages

If you interact with our web pages, not just the bot, those pages might use technical cookies, browser local storage, access logs, and other standard web mechanisms for proper operation, security, and diagnostics. For more details, see our Cookie Policy.

15. Policy Changes

  1. We may update this Policy as our product, tech stack, legal requirements, and business processes evolve.
  2. The new version takes effect upon publication, unless we specify a different date.
  3. Continuing to use the service after an updated version is published means you agree to the changes.

16. Contact