Privacy policy

This policy explains what personal data Fake Dvipam (“we”) collects when you use Fake Dvipam, why we collect it, who else handles it, and what choices you have. We keep it short on purpose.

1. What we collect

• Account details: your name and email address, and a sign-in identifier. You sign in only with Google, through Firebase Authentication, so we receive these from your Google account. We never see or store a password.
• Plan and minutes: your current plan and how many minutes you have left.
• Payment records: the order id, payment id, plan, amount, status and time of each payment. Razorpay handles your card, UPI or bank details. We never see or store them.
• Usage records: when each session started and ended, and minutes used.
• Messages you send us: for example through the contact form.
• Technical data: standard server logs such as IP address, browser and time of request, kept for security and debugging.

2. Call audio and transcripts

The desktop app listens to audio you hear from other participants so it can transcribe it and find questions. Speech is processed on your device where possible. When a question needs the AI model, we send the text of the question and the minimum context needed to answer it to our AI service providers. We don’t keep transcripts after a session ends. We don’t send your screen or video.

Other people on your call. Their speech is personal data too. You are responsible for telling them, or getting their consent, where the law requires it. See recording, consent and platform rules.

3. Why we use it

• To run the service: sign you in, add and count minutes, show your dashboard.
• To take payments and prevent fraud or double-crediting.
• To answer your messages and give support.
• To keep the service secure and fix problems.
• To meet legal and tax obligations.

We don’t sell your personal data. We don’t use it for advertising.

4. Who else handles it

• Google (Sign-in with Google, Firebase Authentication and Cloud Firestore): sign-in, accounts and records.
• Razorpay: payment processing, under its own privacy policy.
• AI service providers: generate suggested answers from question text.
• Hosting and infrastructure providers: run this website.

Some of these providers process data outside India. We choose providers that protect data with encryption in transit and at rest, and we share only what each one needs.

5. Cookies

We use one strictly necessary cookie to keep you signed in (__session). It is not used for tracking or advertising. Firebase also stores a sign-in token in your browser’s local storage. We don’t use advertising or analytics cookies.

6. How long we keep it

• Account and usage records: while your account is open.
• Payment records: as long as tax and accounting law requires.
• Contact messages: until your question is resolved, then for a reasonable period.
• Server logs: a short, limited period.

7. Security

Data in transit is protected with TLS and data at rest is encrypted by our cloud provider. Database rules limit each account to its own records, and only our server can change minutes and payments. No system is perfectly secure. See Security for more.

8. Your rights

You can ask us to access, correct or delete your personal data, to restrict or object to how we use it, and to withdraw consent where we rely on it. Under Indian law you can also nominate someone to exercise these rights for you and make a grievance to us. Email support@example.com. We may need to keep some records, such as payments, when the law requires it.

9. Children

The service is for people aged 18 and over. We don’t knowingly collect data from children.

10. Changes

We’ll post changes here and update the date above. If a change is significant, we’ll tell you directly.

11. Contact

Fake Dvipam
Registered business address, City, State, PIN, India
support@example.com