VCVoiceCraft TTS

Privacy Policy

VoiceCraft TTS accounts चलाने, payments verify करने, plans activate करने, device limits manage करने और support देने के लिए only necessary information collect करता है। हमारा goal unnecessary personal data collect करना नहीं है।

Information we collect

  • Name, email और phone number submitted during checkout or support.
  • Firebase user ID, account email, selected plan और activation status.
  • Device identifier, activation history और app version for Pro/Business device-limit checks.
  • Payment order ID, gateway status, plan amount और activation timestamp from Cashfree or approved payment gateway.
  • Support information such as screenshots, error messages और Windows version when you choose to send them.

Payment data

VoiceCraft TTS card numbers, UPI PIN, bank passwords या full payment credentials store नहीं करता। Payment gateway sensitive payment details handle करता है। हम only order status, plan metadata और activation proof रखते हैं ताकि paid access reliably verify हो सके।

Scripts and generated audio

Your scripts and generated audio are treated as your content. अगर आप support issue solve करने के लिए voluntarily script sample भेजते हैं, तो उसे only troubleshooting purpose के लिए review किया जाएगा। हम आपकी script को public marketing example के रूप में use नहीं करेंगे without consent.

How we use data

Data का use sign in, plan verification, app unlock, fraud prevention, device-limit enforcement, refund review, support diagnosis और product reliability improve करने के लिए होता है। Account and payment data third-party advertisers को sell नहीं किया जाता।

Retention and deletion

Payment and activation records tax, legal, fraud-prevention and dispute-handling requirements के अनुसार retain हो सकते हैं। Privacy request के लिए Contact page से same account email use करें।

How this privacy policy applies

Hindi users should keep the same email for checkout and app sign in. VoiceCraft TTS uses that account identity to verify paid access, support requests, device usage and plan status.

Use the same email for purchase and app sign in so the backend can verify the plan correctly and avoid manual license-key confusion.