Privacy Policy

Effective date: 8 November 2026

1. Who we are

This policy explains how Comcent Technologies Private Limited (“Comcent”, “we”, “us”) handles personal data on this website, comcent.io, and in Comcent Cloud, our hosted voice infrastructure service at app.comcent.io, and in the Comcent mobile apps for Android and iOS, which let members of an organisation take its calls and answer its conversations from their phone.

Comcent Technologies Private Limited
Aasare, 2-187/B16, Fourth Floor, (301) Prathvi Palace
Behind Maari Gudi, Brahmavara, Karnataka, India - 576213
Email: contact@comcent.io

The open-source edition of Comcent runs on your own servers. We do not receive any data from it, and this policy does not apply to it.

2. Our role: controller and processor

If you were on a call with an organisation that uses Comcent Cloud, please contact that organisation about your data. Its own privacy policy applies. If you contact us, we will pass your request on to it.

3. What we collect

Account data. When you or your organisation sign up: your name, email address, phone number, password (stored only as a secure hash), organisation name, and your role. If you sign in with Google or another identity provider, we receive your name and email address from it.

Billing data. The billing name and address, tax details if you give them, your top-ups, plan, charges and invoices. We do not collect or store card numbers or bank details: PayPal and Razorpay handle those. We receive payment metadata from them, such as the payment ID, amount, currency, status and the payer’s name and email.

Call data (processed for our customers). Call recordings, transcripts, AI summaries, sentiment and labels, call logs (numbers, times, durations, agents), voicemail, contact details, and voice bot conversations.

Mobile app data. When you sign in to a Comcent mobile app, we also collect:

The app uses the microphone only during a call, to carry your voice to the other person through our call servers. A call you take in the app is handled like any other call in Comcent Cloud: whether it is recorded or transcribed depends on your organisation’s settings (see “Call data” above). To connect a call, the app also asks Google’s public STUN server for the phone’s public IP address, so Google sees that address.

The app shows notifications for incoming and missed calls, new conversations and new messages. A notification can include the caller’s number or name, the queue, and the first line of a message. The app does not read your contacts, location, photos, or your phone’s own call log or text messages, and it contains no analytics, advertising or crash-reporting tools.

On the phone, the app keeps your sign-in and the counts shown in its home-screen widget in its private storage. Signing out removes them.

Usage data. How you use the app and website: pages and features used, device and browser, IP address, approximate location from the IP address, and logs we keep for security and troubleshooting.

Marketing and attribution data. The campaign that brought you to us, such as UTM tags and ad click IDs (for example gclid), and which ads or pages you saw before signing up. See section 6.

What you send us. Messages to support, feedback, and anything else you choose to share.

4. Why we use it and our lawful basis

PurposeLawful basis
Create and run your account, provide the service, process call data for your organisationPerforming our contract with you or your organisation
Take payments, issue invoices, keep accounting recordsContract, and legal obligation (tax and company law)
Security, fraud and abuse prevention (including coupon abuse and toll fraud)Legitimate uses under the DPDP Act; legitimate interests under GDPR
Service emails (sign-up, security, low balance, renewals, invoices)Contract
Ringing your phone for calls and sending mobile app notificationsContract
Support and responding to your requestsContract, or legitimate interests
Analytics cookies on the website and in the appYour consent
Advertising tags and measuring our adsYour consent
Marketing emailsYour consent, which you can withdraw at any time
Complying with the law and responding to lawful requestsLegal obligation

Under the DPDP Act, we process your data with your consent or for the “legitimate uses” the Act allows, such as when you give us your data voluntarily to use a service or to meet a legal obligation. Where we rely on consent, you can withdraw it at any time; this does not affect what we did before.

5. Who we share it with

We do not sell your personal data.

We use the following subprocessors to run Comcent Cloud. Each gets only the data it needs for its task:

SubprocessorWhat it doesWhere
DigitalOceanHosting of the app, database and call serversUnited States
Amazon Web Services (S3)Storage of call recordings and encrypted backupsUnited States
OpenAITranscript analysis, summaries, sentiment and the voice botUnited States
DeepgramSpeech-to-text and text-to-speechUnited States
ResendSending emailUnited States
PayPalPayments outside IndiaGlobal
RazorpayPayments in IndiaIndia
Zoho BooksInvoicing and accountingIndia
SentryError reports from our servers, which may include account identifiersUnited States
Google Firebase Cloud MessagingDelivering calls and notifications to the Android app: the push token and the notification’s contentUnited States
Apple Push Notification serviceDelivering calls and notifications to the iOS app: the push token and the notification’s contentUnited States
Your phone carrierCarrying your calls, such as Twilio or your SIP trunk provider, under your own agreement with the carrierDepends on the carrier
We also use the analytics and advertising providers in section 6.

We may also share data:

6. Analytics and advertising

On comcent.io we use Google Analytics, Google Ads, Reddit and Microsoft advertising tags, and PostHog. In the web app at app.comcent.io, PostHog records the pages you view and the features you use, and may record your session (password fields are never recorded).

When you sign up or first top up, we may send that event and its value, with a hashed (scrambled) copy of your email address, to Google Ads and Reddit to measure how well our ads work. We store the campaign details (UTM tags and click IDs) that brought you to us on your account, so we know which ads and posts bring customers.

Your choice. Analytics and advertising cookies and tags stay off until you accept them, through the cookie banner. Google tags run in Google’s Consent Mode: until you accept, they do not set cookies for analytics or ads. You can accept or reject analytics and advertising separately, and change your choice at any time from the Cookie settings link at the bottom of every page. Cookies we use:

7. International transfers

We are based in India, and most of our subprocessors are in the United States. Your data may therefore be processed outside your country. We choose providers with strong security and contract terms that protect personal data.

For data from the EU, UK or Switzerland, we rely on the European Commission’s Standard Contractual Clauses (and the UK addendum) in our providers’ data processing agreements, or on another transfer mechanism the law recognises.

8. How long we keep it

9. Leaving an organisation, deleting your account, and deleting an organisation

What an organisation keeps about its members. Each organisation keeps the name and email address of the people who were its members, and the history they worked on: calls, recordings, messages and notes. It keeps them after a member leaves, and after they delete their Comcent account, for as long as its own retention settings keep that history. This lets the organisation know who spoke to whom, for example for audits. A member’s availability (presence) history is kept with the organisation’s reports. That history belongs to the organisation, and we process it on the organisation’s behalf (section 2).

Leaving an organisation. You leave one organisation at a time, and confirm each one: from My profile › Your organizations in the web app, from the mobile app’s Settings, or at app.comcent.io/delete-account. Leaving has the same effect as an Admin removing you: you lose access, and the organisation lists you as a former member. If you are an organisation’s only Admin, you cannot leave it: make someone else an Admin first, or delete the organisation (below).

Deleting your account. You can delete your Comcent login account once you belong to no organisation. Do it from the mobile app’s Settings, or on the web at app.comcent.io/delete-account without installing the app: sign in, leave any organisations still listed, then type your email address to confirm. Deleting your account removes:

Your email address is then no longer tied to a Comcent account, so you can sign up again with it later, as a new account. What your former organisations keep about you is described above. Deleted data may stay in our backups until they expire, as described in section 8.

Deleting an organisation. An Admin can delete an organisation from Settings › General in the web app, by typing its name to confirm. When an organisation is deleted:

Erasing a former member’s details. If you have left an organisation and want it to erase your personal details, ask that organisation. It decides, under the law that applies to it. An Admin can erase a former member’s personal details from Settings › Members › Former members. A pseudonym, such as “Former member 3”, then replaces their name, and their email address is removed. The calls and messages they handled stay with the organisation, and a recording still contains the voices of the people on the call. Their availability (presence) history is kept for 365 days after the erasure, and then deleted.

10. Security

We protect personal data with measures such as encryption in transit (TLS), encrypted backups, access controls that limit who can reach production systems, and logging. No system is perfectly secure, but we work to keep your data safe and fix problems quickly.

11. Data breaches

If a breach affects your personal data, we will tell you and the relevant authorities as the law requires, including the Data Protection Board of India under the DPDP Act and, where GDPR applies, the supervisory authority. For call data we process for an organisation, we will tell that organisation without undue delay so it can meet its own obligations.

12. Your rights

Under the DPDP Act (India) you can:

Under the GDPR (EU and UK) you can:

Deleting your account. Leave your organisations, then delete your account in the mobile app’s Settings or at app.comcent.io/delete-account. Section 9 explains each step, and what your organisations keep.

How to use your rights. Email contact@comcent.io from the address on your account, or tell us how we can confirm who you are. We will reply within 30 days. For call data, we will pass your request to the organisation that controls it and help it respond.

13. Grievance Officer

If you have a question or complaint about your personal data, contact:

Grievance Officer, Comcent Technologies Private Limited
Aasare, 2-187/B16, Fourth Floor, (301) Prathvi Palace
Behind Maari Gudi, Brahmavara, Karnataka, India - 576213
Email: contact@comcent.io

We will acknowledge your complaint and aim to resolve it within 30 days. If you are in India and not satisfied with our answer, you may complain to the Data Protection Board of India.

14. Children

Comcent Cloud is a business service and is not meant for anyone under 18. We do not knowingly collect personal data from children. If you think a child has given us personal data, contact us and we will delete it.

15. Organisations’ own obligations

Organisations that use Comcent Cloud are responsible for their Callers’ and Members’ personal data: telling them how it is used (for example, that calls are recorded), having a lawful basis, and answering their requests. Our Terms of Use set out these responsibilities.

16. Changes to this policy

We may update this policy. When we make a change that matters, we will tell you by email or in the app before it takes effect. The effective date at the top shows which version applies.