Privacy

Beta Privacy Policy

This policy describes the current beta operation of AIDeepDebate. Payment metadata, provider configuration, and retention details may be updated before paid checkout opens.

Information we collect

- Account data: Google account email, profile name, and Google account ID.

- Service data: topic text, debate stages, final outputs, DDT usage, timestamps, history, and download metadata.

- Wallet and billing data: paid DDT, free DDT, reserved DDT, package tier, payment/order metadata, refund metadata, and usage receipts after checkout opens.

- Operational data: quality checks, provider usage, cost metadata, error logs, support records, and security events.

- Technical data: IP address, user agent, cookies/session IDs, and request metadata.

Purposes

- Account authentication and session management.

- Debate generation, result display, downloads, and history.

- DDT reservation, debit, release, wallet display, and refund handling.

- Service recovery, quality validation, security, abuse prevention, and support.

- Accounting, dispute handling, and legal compliance.

AI providers and external processors

To generate debate outputs, your topic, prompts, intermediate outputs, and final output context may be sent to AI API providers such as OpenAI, Anthropic, and Google. AIDeepDebate may also use infrastructure and service providers such as AWS, Cloudflare, Google OAuth, Toss Payments or another payment provider, and email routing providers for service operation.

International processing

AI providers, cloud infrastructure, authentication services, security services, and payment providers may process data outside your country. We transmit data only as needed to provide and operate the service, and provider-specific handling is governed by each provider's terms and privacy documentation.

Retention

- Debate result content: retained for 7 days by default, then deleted.

- Account data: retained until account deletion or a valid deletion request.

- Payment, DDT ledger, refund, and usage receipt metadata: retained as needed for accounting, dispute handling, and legal compliance after checkout opens.

- Operational/security logs: retained as needed for incident response, abuse prevention, quality validation, and cost reconciliation.

Operator access

Operators may access limited metadata, status, error logs, usage records, and quality validation records for support, incident recovery, abuse prevention, and accounting. Access to result content is limited to legitimate operational purposes such as user support, incident handling, or safety operation.

Sensitive input warning

Do not enter sensitive personal information, third-party personal data, trade secrets, confidential information, or legally protected information. Free or test provider quota may be subject to provider review or quality-improvement policies.

Your rights and contact

You may request access, correction, deletion, or restriction of your personal data. Contact [email protected].