VUST Privacy Policy

• Telegram identifiers, such as Telegram user ID, chat ID, language, username, first name, or referral payload when available.
• User messages, uploaded text, URLs, files, images, or prompts needed to provide the selected tool.
• AI-generated outputs, tool status, delivery status, feedback, and support messages.
• Payment status, entitlement data, pass key, spark balance, trial counters, purchase events, and refund status.
• Operational event and log metadata such as bot, surface, source, timing, provider, model, cost estimates, error codes, and safe request references.
• Website usage metadata collected by hosting, analytics, security, and performance tools.

• to deliver AI-generated results and Telegram bot responses;
• to count free trials, subscriptions, passes, and spark usage;
• to grant and verify paid entitlements;
• to handle support, refunds, abuse prevention, and debugging;
• to monitor quality, cost, latency, errors, and service health;
• to improve product flows and understand aggregate usage.

VUST relies on third-party processors and infrastructure providers, including:

• Telegram for bot delivery, Telegram user context, and Telegram Stars payment surfaces;
• Tribute for supported external checkout and payment flows;
• AI and model providers for text, image, search, analysis, or generation tasks;
• hosting, database, storage, analytics, logging, and security providers such as Vercel and Supabase;
• other tool-specific providers when a feature needs translation, extraction, search, or media processing.

VUST does not publicly sell user data. We do not share raw user inputs with advertisers or data brokers.

• VUST stores payment state and entitlement state needed to deliver access.
• Public analytics and admin events must not include raw payment IDs, raw Telegram IDs, raw secrets, payment card data, or full wallet identifiers.
• Payment processors may independently process payment details under their own terms and privacy policies.
• VUST does not collect or store full payment card numbers through its own website.

Retention depends on the data type and operational need.

• Tool history, trial counters, entitlement records, purchases, and refund records may be kept while needed for account, billing, support, and audit purposes.
• Operational logs may be retained for debugging, incident response, analytics, and service reliability.
• Support conversations may be kept while the issue is open and for a reasonable period after closure.
• Temporary caches and processing artifacts should be deleted or made ineligible for reuse after their operational purpose ends.

You may request access, correction, deletion, or review of your VUST data by contacting @vustbot.

Some records may need to be retained for security, billing, dispute, tax, fraud-prevention, or legal reasons. Support handling is manual.

VUST uses practical safeguards such as access controls, transport encryption, secret separation, and privacy-safe logging patterns. No system is perfectly secure, and you should avoid sending unnecessary secrets or highly sensitive data to general-purpose AI tools.

VUST is not intended for children. If you believe a child provided personal data to VUST, contact support so we can review and remove it where appropriate.

VUST may update this Privacy Policy as products, payment rails, infrastructure, or legal requirements change. Material changes may be announced on the website or in relevant bots.