Privacy Policy

Last updated 15 October 2026. For businesses using convertCall, and for the people who call them.

Who this is about

convertCall is used by businesses. The business — your employer, or whoever gave you this phone — is the operator of the account this app signs into, and decides what the app says on their behalf. There are two different people in this policy:

• The person holding the phone. An employee or contractor of the operator.
• The caller. A member of the public who rang that phone and is sent a reply. They never installed anything and never agreed to anything — which is why this policy is stricter than the app's size suggests.

What the app does

When a call arrives on this phone, the app reads the incoming caller's number, asks the operator's server whether that caller should be replied to, and — if the answer is yes — sends them one SMS written by the operator. It does this whether or not the call was answered. Nobody presses send.

What this app automates

convertCall is a device automation app: it runs a small set of automations on the phone it is installed on, each one the person holding the phone can see and switch off. This is the complete list — there is nothing else the app does in the background.

• Reply to calls by SMS (on by default) — after a call ends, the caller gets the operator's message: one written for every caller, or separate ones for missed calls, answered calls, calls outside business hours, and — if the operator chooses — a different one for a caller who has heard from the business before. The operator chooses whether to reply to all incoming calls, missed calls only, or answered calls only. We do not read your messages: composing this reply needs only the caller's number, never anything already on the phone.
• Business hours (off by default) — an operator-wide setting for when the business is open. Outside those hours, a call either gets a different, "we're closed" message or no reply at all — the operator's choice.
• Reply to calls by WhatsApp (only if the operator adds it to a template) — not an automatic message: a reply's template can include a link to a WhatsApp number the operator has set for that phone, so a caller who would rather text can continue there. Tapping it only opens WhatsApp with a drafted message; the caller decides whether to send it, and convertCall is not a party to anything said afterward.
• WhatsApp button on sent replies (on by default, this phone only) — on the phone's own History screen, a reply that was actually sent gets a button that reopens WhatsApp, addressed to that same caller, with the same words already typed in. We do not read your messages: nothing is sent until Send is tapped inside WhatsApp itself, and the app does not hold any permission to read WhatsApp, or anything back from it.
• Call-back reminder (off by default, this phone only) — if a missed call has not been called back within a delay the person holding the phone chooses, this phone shows a notification with a Call button. This one runs entirely on the phone — see "Recent calls, for the call-back reminder" below.
• Daily summary (off by default, this phone only) — one notification a day, at a time chosen on the phone, stating how many calls this phone took and how many were replied to.
• Rules (none by default, this phone only) — automations the person holding the phone builds for themselves: when a call is missed or answered, or at a set time each day, if conditions they choose hold (inside or outside business hours, a new or returning caller, which SIM), then save the caller as a contact, add a call-back appointment to the calendar, turn Do Not Disturb on or off, or show a call-back reminder. Each rule can be switched off on its own. See "Contacts, calendar and Do Not Disturb" below.

Business hours is set by the operator and shared by every phone on the account; the call-back reminder, the daily summary, the WhatsApp button and rules are each phone's own choice and affect only that phone.

What it does not automate. convertCall does not use Android's Accessibility service, has no bulk or broadcast messaging feature, no SMS scheduler for messages you write yourself, and no camera, image or video permission — the app cannot see or capture anything of the kind. We do not read your messages — not your SMS, not WhatsApp, not anything else on the phone — in either of the WhatsApp-related items above or anywhere. The only things convertCall itself ever sends are the single SMS reply described above, and — only if the person holding the phone taps Send inside WhatsApp — a message that person chose to send, in a screen convertCall does not see once it opens.

What is collected

The caller's phone number. Read from the incoming call as it arrives, and sent to the operator's server so it can decide whether a reply is due and record that one was sent. It is used for nothing else — not sold, not shared with advertisers, not used to build a profile. The only place it travels outside the operator's own server is the mobile network that carries the SMS, the same carrier that already handled the call.

The account username and password. Typed into the app once, when the phone is set up, and sent to the operator's server with each request so it knows which business the phone belongs to. Stored on the phone in Android's encrypted preference storage, and excluded from Android backup, so it is not copied off the device.

A random installation identifier. Generated the first time the app signs in, to tell one of the operator's phones from another. It is not an advertising ID and is not derived from any hardware identifier — it says nothing about the device or the person, and means nothing outside the operator's own system.

Recent calls, for the call-back reminder — only while it is switched on

This automation is off by default. If the person holding the phone switches it on — or creates a rule with a "remind me" action — then after a missed call the app checks the phone's own call log — for that one number, since that missed call — to see whether it has since been called back. That check runs entirely on the phone. The result is never sent anywhere: not to the operator's server, not to us, not to anyone. It exists only to decide whether to show a reminder notification on this phone, and switching the automation off, or removing the rule's reminder, stops the check happening at all. This is the only circumstance in which the app reads anything from the call log beyond the number of the call currently arriving.

The daily summary notification

Also off by default. When switched on, it reads this phone's own history of calls it has already handled and shows a count in a notification once a day. Nothing new is collected to produce it and nothing leaves the phone.

Contacts, calendar and Do Not Disturb — only for rules you create

The app has no access to any of these until the person holding the phone creates a rule that needs it, and Android then asks them to allow it. It is never asked for up front, and someone who only uses SMS replies is never asked at all. What each is used for:

• Contacts — for the "save caller as a contact" action. The app looks up one number, the caller's, to see whether it is already saved, and if it is not, adds a new contact named the way the rule says (for example "Lead · 14 Oct") with a note of when they called. It never reads the rest of the address book.
• Calendar — for the "add a call-back" action. The app finds the phone's own calendar and adds one 15-minute call-back appointment with a reminder. It does not read the appointments already there.
• Do Not Disturb — for the ringer action. The app switches Do Not Disturb on, or back off, at the time the rule says. Android grants this from its own "Do Not Disturb access" settings page, which the app opens for the person to decide.

None of this ever leaves the phone. Contacts and appointments the rules create are ordinary entries in the phone's own Contacts and Calendar apps, owned by the person holding the phone like any they made themselves; the app sends nothing about them to the operator's server, to us, or to anyone. Whether a caller is "new" or "returning" is judged from the app's own history of calls it has handled, never from the address book or the call log. The rules themselves are kept on the phone too, separately for each account signed into it.

What is deliberately not collected

We do not read your messages. The app holds no permission to read your SMS, WhatsApp, or any other messages, and no permission for your camera, images, video, or location. Contacts and calendar access exist only for the rules described above, are asked for only when a rule needs them, and are used only on the phone. It does hold Android's call-log permission, and uses it for exactly two things, both described above: reading the number of the call arriving now, and — only while the call-back reminder or a rule's reminder is in use — checking whether one specific number has been called back since a missed call. Neither is ever uploaded.

• Your existing SMS messages — the app holds no permission to read or receive them.
• Anything inside WhatsApp — the app holds no permission that lets it read WhatsApp; it can only open a wa.me web link, the same as tapping one in any other app, which hands control to WhatsApp entirely.
• Your address book and your calendar — never read as a whole, never uploaded. A rule may look up whether one caller's number is already saved, and may add a contact or an appointment; that is all.
• Your call history, beyond the two uses above — never enumerated in full and never uploaded, under either use.
• Photos, videos or camera access — the app holds no camera, image or video permission.
• Location — no location permission is requested.
• Advertising identifiers — none are read. There is no advertising, analytics or payment library in the app.

Permissions, and why each is needed

• Read call log (READ_CALL_LOG) — Android delivers the incoming caller's number only to apps holding this permission. Without it the app knows a call arrived but not from whom. Also used, only while the call-back reminder or a rule's reminder is in use, to check locally whether one number has been called back since a missed call. Your call history is never uploaded, and never read for any other purpose.
• Send SMS (SEND_SMS) — to send the reply without anyone pressing send, which is the entire product: convertCall does not send any SMS without the operator having set up and activated a template first, and never sends anything the operator did not write. We do not read your messages — this permission sends text, it does not read any, and the app holds no READ_SMS or RECEIVE_SMS permission that would let it.
• Read phone state (READ_PHONE_STATE) — to know the phone is ringing, and on a dual-SIM phone which SIM the call came in on, so the reply is sent from the same number.
• Notifications (POST_NOTIFICATIONS) — for the "watching for calls" notice that keeps the app running between calls, for the call-back reminder, for the daily summary, and to say what a rule did when it ran.
• Contacts (READ_CONTACTS, WRITE_CONTACTS) — only for a rule's "save caller as a contact" action, and asked for only when such a rule is created: to check whether one caller's number is already saved, and to save it if not. Never used to read the address book as a whole, and nothing from it is uploaded.
• Calendar (READ_CALENDAR, WRITE_CALENDAR) — only for a rule's "add a call-back" action, and asked for only when such a rule is created: to find the phone's calendar and add an appointment to it. Existing appointments are not read, and nothing is uploaded.
• Do Not Disturb access (ACCESS_NOTIFICATION_POLICY) — only for a rule's ringer action, to turn Do Not Disturb on or off. Granted from Android's own settings page, never silently.
• Run at startup (RECEIVE_BOOT_COMPLETED) — to start answering again after the phone restarts.
• Internet (INTERNET) — to reach the operator's server.

Who the data is shared with

Nobody, beyond the operator's own server and the mobile carrier that delivers the SMS. No third-party service receives the caller's number, the account, or anything else.

One technical exception, which carries no personal data. If the mobile network cannot look up the address of the operator's server — which has happened on some mobile networks — the app asks Google's and then Cloudflare's public address lookup (DNS) service instead, the way many Wi-Fi routers already do. All they are told is the server's name, convertcall.in: never a caller's number, the account, or anything else about the phone or the person holding it.

How long it is kept

The operator's server keeps a record of replies sent — who was replied to and when — which is what proves a message was sent to a member of the public; the operator is responsible for how long it is retained and for deleting it on request. The phone itself keeps a short local history of calls it has handled — used for the History screen and, if switched on, the daily summary — which is erased when the phone signs out. A call-back reminder check leaves nothing behind once it has run.

Your rights, and how to exercise them

Because the operator decides what is sent and holds the records, requests go to them.

• If you are a caller who received a message and want your number blocked or your record erased, contact the business that messaged you. They can block your number so you are not messaged again, and can delete their record of it.
• If you are the person holding the phone, signing out erases the local history from the device.

If you cannot reach the operator, contact us below and we will put you in touch with them or, where we are able to, act on the request ourselves.

Security

Traffic between the app and the operator's server is encrypted with HTTPS; release builds refuse plain, unencrypted connections outright. Account credentials are held in Android's encrypted preference storage and excluded from device backup.

Payments

The app's Billing tab only shows the account's plan and invoices; nothing is paid from the app. Invoices are paid through a Razorpay payment link our team sends, or arranged with our team directly. Razorpay, a payment provider regulated in India, collects the payment details and processes the payment, and our server verifies with Razorpay that the invoice was paid before recording it. Neither the app nor our server stores your card, UPI or bank details; Razorpay's handling of what it collects is governed by its privacy policy.

Children

This app is a business tool, is not directed at children, and is not designed for or marketed to them.

Changes

If this policy changes materially, the date at the top changes and the current version is published at the same URL.

Contact