Privacy policy

How CX-CRM handles personal data for the teams who use it and for the people who contact those teams by email, social messages, WhatsApp and phone.

Last updated

Who we are

CX-CRM is a customer service workspace operated by cxicon (“we”, “us”). Organisations use it to answer their own customers: their staff sign in, connect the organisation's mailboxes, Facebook Pages, Instagram accounts, WhatsApp numbers and phone lines, and work every conversation as a ticket.

This policy covers two groups of people:

  • Workspace users: the agents, supervisors and administrators an organisation invites to CX-CRM.
  • Contacts: the people who email, message, call or submit a lead form to an organisation that uses CX-CRM.

For contacts, the organisation they got in touch with decides why and how their data is used, and is the controller of it. We process that data on the organisation's behalf and on its instructions. For workspace accounts and for running and securing the service, we are the controller.

Information we handle

Workspace users

  • Account details: name, work email address, profile photo, roles, department membership, time zone and display preferences.
  • Sign in data: a hashed password (we never store it in plain text), password reset and invitation records, and session cookies.
  • Activity: an audit log of administrative and ticket actions (who did what and when), and your availability on the browser phone.
  • Microphone audio while you are on a call through the browser phone. We ask your browser for microphone access only to place and answer calls.

Contacts

  • Identity and contact details: name, email addresses, phone numbers, and social or WhatsApp identifiers with the profile name or username the network provides.
  • Conversations: emails (with their headers), Facebook, Instagram and WhatsApp messages, and the files attached to them, such as images, documents, voice notes and videos.
  • Lead form answers submitted through a Facebook lead ad, with the ad and campaign the lead came from.
  • Calls: caller and called numbers, call times, duration and outcome, call recordings, voicemail, transcripts, and the summary and reason an automated agent records for a screened or lead call.
  • Notes, tags, categories and statuses the organisation's team adds while handling a ticket.

Connected accounts

When an administrator connects a channel we store what is needed to keep it working: OAuth access and refresh tokens, or a mail server host and password, plus the account, Page or number identifiers. These credentials are encrypted at rest.

Technical data

Our servers record IP addresses, browser and device type, request identifiers, timestamps and error details to run, secure and debug the service.

How we use it

We use the information above only to:

  • Provide the service: turn incoming messages, calls and leads into tickets, match them to existing customer records, route them to the right department, and send the team's replies back through the same channel.
  • Keep accounts secure: authenticate users, enforce roles and permissions, scan every file for viruses, block senders an organisation chooses to block, and limit abusive message volumes.
  • Answer and route calls, record them when the organisation has switched recording on, and produce transcripts and summaries.
  • Send service email such as invitations, password resets, email address confirmations and alerts about failing channels.
  • Operate, troubleshoot and improve the reliability of CX-CRM, and meet legal obligations.

We do not sell personal data, we do not use it for advertising, and we do not use contact data or connected account data to train AI models.

Where a law such as the EU or UK GDPR or Malaysia's Personal Data Protection Act 2010 applies, we rely on performing our contract with the organisation, our legitimate interest in running a secure service, and legal obligations. The organisation is responsible for its own lawful basis for the contact data it brings into CX-CRM.

Connected services

CX-CRM connects to the services below only when an organisation's administrator connects them. Each provider receives only what it needs to deliver the feature, and its own privacy policy also applies to what it processes.

  • Microsoft 365 (Outlook, Exchange Online)

    Used for
    Read incoming mail in a connected department mailbox, turn it into tickets, and send agent replies from that mailbox.
    Data involved
    Messages, headers and attachments in the connected mailbox; the mailbox account's basic profile.
    Permissions
    offline_accessUser.ReadMail.ReadWriteMail.ReadWrite.SharedMail.SendMail.Send.Shared
  • Google (Gmail)

    Used for
    Read incoming mail in a connected Gmail or Google Workspace mailbox, turn it into tickets, mark handled mail, and send agent replies.
    Data involved
    Messages, headers and attachments in the connected mailbox.
    Permissions
    https://www.googleapis.com/auth/gmail.modify
  • Your own mail server (SMTP and IMAP)

    Used for
    Read and send mail for a mailbox an administrator connects with a host, username and password.
    Data involved
    Messages, headers and attachments in that mailbox.
  • Meta: Facebook Pages and Messenger

    Used for
    Receive Messenger conversations sent to a connected Page as tickets and send agent replies.
    Data involved
    Messages and attachments, the sender's Page scoped ID and name.
    Permissions
    pages_show_listpages_manage_metadatapages_messagingpages_read_engagementbusiness_management
  • Meta: Instagram

    Used for
    Receive Instagram direct messages sent to a connected professional account as tickets and send agent replies.
    Data involved
    Messages and attachments, the sender's Instagram scoped ID, username and name.
    Permissions
    instagram_basicinstagram_manage_messages
  • Meta: WhatsApp Business Platform

    Used for
    Receive WhatsApp messages sent to a connected business number as tickets and send agent replies.
    Data involved
    Messages and media, the sender's WhatsApp phone number or user ID and profile name.
    Permissions
    whatsapp_business_messagingwhatsapp_business_management
  • Meta: Facebook lead ads

    Used for
    Collect leads from lead forms an administrator picks, so each lead becomes a ticket the team can follow up.
    Data involved
    The answers the person gave on the form (such as name, email and phone), when they submitted it, and the ad, ad set, campaign and form it came from.
    Permissions
    leads_retrievalpages_manage_ads
  • Twilio

    Used for
    Phone numbers, inbound and outbound calls, the in browser phone agents answer with, call recordings and voicemail.
    Data involved
    Caller and called numbers, call times and status, call audio while the call is live, and recordings until we have copied them.
  • ElevenLabs

    Used for
    Speech to text transcripts of recordings and voicemail, and the automated voice agent used for call screening and lead calls.
    Data involved
    Call audio and what is said on the call, the caller's number, and the names, departments and categories the agent needs to route the call.

Files are scanned for viruses by a scanner that runs on our own infrastructure; they are not sent to a third party for scanning. An administrator can disconnect any channel at any time, which stops us reading from it and removes its stored credentials.

Calls, recordings and AI

  • Recording. When an organisation turns recording on for a phone line, callers hear a recording notice before the call is recorded. We copy each recording from Twilio to our private storage and then delete Twilio's copy.
  • Transcripts. Recordings and voicemail are sent to ElevenLabs to be transcribed, and the transcript is stored with the ticket.
  • Call screening. On lines where the organisation turns it on, an automated voice agent answers first, says that it is automated, asks the reason for the call and routes it to the right team. The words of the conversation are processed by the language model configured for that agent through ElevenLabs. Once we have stored the transcript and audio, we delete the conversation at ElevenLabs.
  • Automated lead calls. An organisation may have the automated agent call people who asked to be contacted through a lead form. The agent says it is automated, calls only between 9:00 and 20:00 in the person's time zone, and calls a number at most twice in 24 hours. You can tell the agent, or the organisation, that you do not want further calls.

Google user data

CX-CRM's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

  • We access a Gmail mailbox only after an administrator signs in and grants access, and only to read its messages into tickets, mark them as handled, and send the team's replies.
  • We do not use Gmail data for advertising, do not sell it, and do not use it to train AI or machine learning models.
  • Our staff do not read Gmail data unless the organisation asks us to for support, it is needed for security or to comply with law, or it has been made anonymous.
  • The administrator can revoke access at any time by disconnecting the channel in CX-CRM or in their Google Account settings.

Sharing and disclosure

We share personal data only:

  • Within the organisation's workspace, with users whose role and department allow them to see it.
  • With the providers listed under Connected services and with our hosting and email delivery providers, who act on our instructions.
  • When the law requires it, or to protect the rights, safety and security of our users, the public or CX-CRM.
  • As part of a merger, acquisition or sale of assets, in which case this policy keeps applying to the data transferred.

How long we keep it

  • Tickets, customer records, messages, files, recordings and transcripts are kept for as long as the organisation keeps its workspace, unless the organisation deletes them sooner or asks us to.
  • Raw copies of incoming email and messages are deleted 45 days after they have been processed into tickets.
  • Files uploaded but never sent with a message are deleted after 24 hours.
  • Recordings are deleted from Twilio, and screening and lead call conversations from ElevenLabs, once we have stored our copy.
  • Social profile details are cached for up to 24 hours before they are refreshed.
  • When an organisation stops using CX-CRM, we delete or return its data as our agreement with it sets out, except where the law requires us to keep it longer.

Security

  • Traffic is encrypted in transit with TLS.
  • Channel credentials are encrypted at rest and passwords are hashed.
  • Access inside a workspace is limited by role, permission and department, and administrative actions are written to an audit log.
  • Every file is virus scanned before anyone can download or send it, files stay in private storage, and supervisors can redact a sensitive file so its contents are removed.
  • Requests from Meta, Twilio and ElevenLabs are checked against their signatures before we accept them.

No system is perfectly secure. If we become aware of a breach affecting personal data, we will notify the affected organisations and, where required, the authorities without undue delay.

Cookies and local storage

We use only the cookies needed to run CX-CRM: a session cookie that keeps you signed in and a security token that protects forms against cross site request forgery. Your browser also stores your light or dark theme choice locally. We do not use analytics, advertising or third party tracking cookies.

Your rights

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict how it is used, and to withdraw consent.

  • Contacts: please send your request to the organisation you were in touch with, as it controls your data. If you write to us instead, we will pass your request on and help the organisation respond.
  • Workspace users: you can update your own profile, email and password in account settings. For anything else, ask your administrator or contact us.

We respond within 30 days. You also have the right to complain to your local data protection authority.

Deleting your data

To remove the data CX-CRM holds about you, or to stop us receiving data from a connected account:

  1. If you messaged a business on Facebook, Instagram or WhatsApp, emailed it, called it, or submitted one of its lead forms, ask that business to delete your data, or email privacy@cxicon.com with the subject “Data deletion request”, the business's name, and the email, phone number or profile you used. We will confirm with the business and permanently erase your messages, recordings, transcripts and customer record.
  2. If you connected a Facebook Page, Instagram account or WhatsApp number, an administrator can disconnect it on the Channel connection page in CX-CRM, and you can remove the app under Settings, then Business integrations, in Facebook. Disconnecting deletes the stored access tokens. Email us to have the messages already received erased too.
  3. If you are a workspace user, ask your administrator to remove your account, or email us.

We confirm every request by email and complete it within 30 days. Copies in backups are overwritten on their normal cycle. Our data deletion instructions give the full steps, including removing CX-CRM in Facebook.

International transfers

We and the providers above may process data in countries other than the one you live in. Where data leaves a country whose law restricts transfers, we rely on the safeguards that law allows, such as standard contractual clauses.

Children

CX-CRM is a business tool and is not directed at children. We do not knowingly collect data from children under 16 for our own purposes. If you believe a child's data was sent to an organisation through CX-CRM, contact that organisation or us.

Changes to this policy

We will update this page when our practices or integrations change, and change the date at the top. If a change is significant, we will tell organisations and workspace users before it takes effect.

Contact us

Questions or requests about privacy: email privacy@cxicon.com. We aim to reply within 5 working days.