Privacy Policy

Last updated: 3 September 2026

DreamSoft ("we", "us", "our") is operated by DreamLearn Quiz LLP and runs two products under one account: CallMitra, where businesses build AI agents that make and receive phone calls and follow up over RCS and SMS; and the WhatsApp Business API inbox, where a team answers one WhatsApp number together. This policy covers both, and explains what data we collect while running them, why, and how it's handled.

1. Who this applies to

This policy covers two kinds of people: customers — the businesses who sign up for a CallMitra account and configure agents, numbers, and messaging channels — and end users — the people those agents call, or who call/message a customer's connected number.

2. What we collect

• Account data: a customer's name, email, and organization details, used to sign in and operate the dashboard.
• Call data: phone numbers dialed or received, call duration, status, and a transcript of what was said — generated so the customer can review conversations and so the agent can hold a coherent conversation turn to turn.
• Message data: the content and delivery status of WhatsApp, RCS, and SMS messages sent through the platform, and any inbound replies to a customer's connected number.
• Knowledge base content: documents a customer uploads so their agent can answer questions from them.
• Usage and billing data: call minutes, messages sent, and the resulting wallet transactions.

We do not collect this data about someone who has never called, messaged, or been called/messaged through a customer's CallMitra-connected number.

3. How we use it

• To operate the call — speech is transcribed and sent to the language model powering that customer's agent so it can generate a reply, then synthesized back to audio.
• To send the message a customer configured (a saved template, or one the agent decides to send mid-call) over WhatsApp, RCS, or SMS.
• To show a customer their own call/message history, transcripts, and analytics inside the dashboard.
• To bill for minutes and messages actually used, against a customer's prepaid balance.
• To operate the platform reliably — diagnosing errors, preventing abuse, and keeping the service running.

We do not sell call or message content, or use it to build advertising profiles.

4. Third parties we send data to

Running a call or sending a message necessarily routes data through the specific providers a customer's agent is configured to use:

• Telephony: Plivo, Exotel, or Vobiz — carries the call itself.
• Speech-to-text / text-to-speech: Sarvam AI, Cartesia, ElevenLabs, or OpenAI, depending on what the agent is configured with.
• Language model: Anthropic (Claude), OpenAI, or Google (Gemini) — whichever the customer selected for that agent.
• Messaging: Meta (WhatsApp Business Cloud API), Telinfy (RCS), or an SMS gateway — only for the channels a customer has actually connected.

Each of these providers processes only what a given call or message actually needs to function, under their own privacy terms.

5. WhatsApp Business API

Where a customer connects a WhatsApp number to us, some things are worth stating plainly, because the arrangement differs from the rest of the platform:

• The account stays theirs. The WhatsApp Business Account (WABA) and phone number are created under the customer's own Meta Business account. We are granted access to operate the inbox on top of it; we never own the number, and the customer can revoke our access at any time without losing it.
• We handle messages on their behalf. For a connected number we process the messages sent and received — content, the end user's phone number, the profile name WhatsApp supplies, media, and delivery/read receipts — so that the customer's agents can read and answer them in the shared inbox, and so templates and broadcasts can be sent and reported on.
• Meta processes it too. Every WhatsApp message necessarily passes through Meta's WhatsApp Business Cloud API and is subject to Meta's own terms and privacy practices, over which we have no control.
• The business is the one contacting people. For an end user messaging a business through WhatsApp, that business decides what is sent and holds the relationship. We provide the software it runs on.
• Opt-in is the customer's responsibility. WhatsApp requires that a person has agreed to be contacted before a business messages them. We provide the tools to collect and record that consent; the customer is responsible for having obtained it.
• Disconnecting. When a customer disconnects their WABA or closes their account, we stop processing new messages for that number. Message history already in the inbox is deleted on request, as described below.

We do not use a customer's WhatsApp message content to train models, to market to their end users, or for any purpose other than operating the service they asked us to run.

6. Data retention

Call transcripts, message history, and account data are retained for as long as a customer's account is active, so they remain available for review and billing records. A customer can request deletion of their account and associated data by contacting us.

7. Your choices

An end user who does not wish to receive further calls or messages from a business using CallMitra should contact that business directly — CallMitra is the platform their agent runs on, not the business itself. WhatsApp messages include a standard opt-out path; SMS sends honor STOP requests.

8. Security

Access to the dashboard requires authentication, and platform-admin functions are separately restricted. Data in transit to and from telephony, AI, and messaging providers is encrypted (HTTPS/TLS).

9. Changes to this policy

If this policy changes materially, the "Last updated" date above will change accordingly.