Policy

Privacy Policy

How Asymmetrica and Ananta handle conversations, files, payment events, and operator diagnostics.


Overview

Asymmetrica provides AI-powered productivity and document workflows through Telegram, the Ananta mini-app, and connected web services. This Privacy Policy explains what information we process, why we process it, and how we use it to deliver and improve the service.

Scope

This policy applies to the Asymmetrica website, the Ananta Telegram experience, the web mini-app, payment flows, and connected service infrastructure used to fulfill your requests.

Information we process

Depending on how you use Ananta, we may process:

  • Conversation data such as messages, commands, and workflow context.
  • Files you send such as PDFs, images, office documents, and voice notes.
  • Account and identity signals needed to maintain continuity across Telegram and the mini-app.
  • Payment events and payment references required to provision credits and prevent duplicate processing.
  • Operational diagnostics required for debugging, fraud prevention, reliability checks, and founder/operator support.

Why we process this information

  • To answer questions and carry out requested workflows.
  • To generate, transform, or analyze documents you explicitly ask us to process.
  • To maintain session continuity and make the product usable over time.
  • To provision purchased credits and detect duplicate payment callbacks or delivery failures.
  • To improve reliability, observability, and security of the service.

Third-party processors

To provide requested functionality, Asymmetrica may rely on third-party services such as payment processors, OCR providers, document conversion services, search providers, storage systems, and messaging infrastructure. These providers only receive the information needed for the requested operation.

Files and generated outputs

Files you upload may be stored in the system workspace while Ananta processes them and while your conversation context remains active. Generated outputs such as PDFs, OCR artifacts, or structured drafts may also be stored so they can be delivered back to you or reopened in the mini-app.

Payments

Payments are processed through external providers such as Razorpay and, where applicable, Telegram Stars. We do not store full card details. We do store payment references, event identifiers, and related metadata needed to confirm successful purchases, prevent duplicate provisioning, and support debugging.

Diagnostics and safe-display operator tools

Asymmetrica includes founder/operator diagnostics for reliability and support. These tools are protected and designed to use safe-display redaction so that chat identifiers, paths, and hashes are masked where practical.

Data sharing

We may use third-party services required to deliver requested functionality, such as OCR, document conversion, storage, web search, or payment processing. We do not sell your personal information.

Retention and auto-deletion windows

We retain information only as long as needed to provide the service. Specific auto-deletion windows currently in place:

  • Conversations are kept for 30 days and then removed from active storage.
  • Payment receipts are kept for 180 days — required for tax and financial audit purposes.
  • Runtime continuity state — the active file pointer, active document context, attachment session, and session projection that we use to keep a workflow flowing across messages — has short TTL-based expiry, typically minutes to a few hours per artifact, so half-finished workflows don't linger on our servers once you've moved on.
  • Workspace files remain until you delete them individually (a bulk workspace purge is on our roadmap).
  • Learned preferences (language, name, recurring instructions) are kept across sessions so the product remembers you, and cleared when you run /deletedata.

Data is stored on our own servers in Singapore — not on a third-party public cloud. We can tell you exactly where your data lives at any moment.

Security

We take reasonable technical and operational steps to protect service data, but no online system can guarantee absolute security. You should avoid sending information you would not want processed through online software systems unless it is necessary for the task you are asking us to perform.

Your controls — commands you can run anytime

Ananta ships with self-service privacy commands you can send to @asymm_bot from your Telegram chat:

  • /privacy — Shows a full summary of what Ananta has stored about you: name, language preference, number of conversation turns, uploaded files, learned preferences, and retention windows. No need to ask us.
  • /exportdata — Downloads everything we hold about you as a single JSON file you can keep, audit, or hand to a data auditor. Includes messages, preferences, file metadata, business records, and the full runtime lifecycle.
  • /deletedata — Permanently erases all your data: conversations, files, preferences, session state. We ask you to confirm once (because it cannot be undone), then it is gone from our systems.

These commands are wired into the bot today — try /privacy now if you want to see your own report.

What we will never do

  • Sell your data. Ever.
  • Share your data with advertisers or data brokers.
  • Use your conversations or files to train AI models.

If any of these ever change, this policy will say so first, and you will be notified inside the product before the change takes effect.

DPDP Act and GDPR

Ananta is built to comply with India's Digital Personal Data Protection Act (DPDP) 2023 and Europe's General Data Protection Regulation (GDPR). You have the right to:

  • Access your data — use /exportdata in Telegram or email support.
  • Correct your data — just tell Ananta what changed.
  • Delete your data — use /deletedata in Telegram or email support.
  • Ask us anything — email sarat@asymmetrica.ai and one of us will actually read it.

For data-related support requests beyond what the commands above cover, email us directly at sarat@asymmetrica.ai.

Policy changes

We may update this policy as the product evolves. When we do, we will update the date on this page.

Last updated: 2026-04-18