PricingCustom builds
Log inStart free trial
One inboxEvery chat in one listLead sourcesThe ad or page behind each chatAuto-repliesAn answer at once, after hours tooReportsReply times and a Monday reportBookingsViewings and appointments from the chatPhone appThe same inbox on your team's phonesWebhooks and calendarChats and bookings to your systems
All channelsFour channels in one inboxWhatsAppYour number, through Meta's official platformInstagramDirect messages and story repliesMessengerYour Facebook Page's chatsWebsite chatA chat on your site, working today
Online shopsClinics and dentistsCar dealersReal estate and developersHotels and guesthousesBeauty and salonsRestaurants and deliveryFitness and studiosSchools and coursesRepair and services

All industries →

PrivacyTermsDelete your data

Privacy

mpulse holds chats between businesses and their customers. This page says what we keep, why we keep it, who else handles it, and how to have it removed.

Updated 15 November 2026

On this page

Who we areIf you run a business on mpulseIf you wrote to a business that uses mpulseFacebook, Instagram and WhatsApp dataRemoval and deletion through MetaAIIf you used the chat or the form on this websiteCookiesWho else handles dataWhere data is keptHow long we keep itHow we protect itYour rightsChanges to this page
  • The chats belong to the business that received them. We hold them on its behalf.
  • We never sell personal data and never use it for advertising.
  • Customers' messages are never sent to an AI model.
  • Closing an account removes its data from our database at once, together with the sign-in accounts of its people who are in no other team, with the two exceptions under “How long we keep it”. Our database provider's recovery copies are gone within 24 hours.
  • You can ask what we hold about you, and have it corrected or deleted.
  1. Who we are
  2. If you run a business on mpulse
  3. If you wrote to a business that uses mpulse
  4. Facebook, Instagram and WhatsApp data
  5. Removal and deletion through Meta
  6. AI
  7. If you used the chat or the form on this website
  8. Cookies
  9. Who else handles data
  10. Where data is kept
  11. How long we keep it
  12. How we protect it
  13. Your rights
  14. Changes to this page

Who we are

mpulse is run by LLC “ინთაიმი” (Georgia), trading as Vebses, identification code 405403317, registered at Irakli Abashidze Street N 21, apartment 18, Tbilisi, Georgia. Write to info@mpulse.ge about anything on this page.

mpulse puts a business's customer chats in one inbox and shows its owner how the team is doing. The chat on this website is ours. The chats inside mpulse belong to the businesses that use it.

If you run a business on mpulse

We keep what the account needs:

  • Your name, work email, role and profile photo, and your Google name, email and picture if you sign in with Google. A password is stored only as a one-way hash.
  • If you make your account yourself on our website: which version of our terms you accepted, when, and the internet (IP) address and browser you accepted them from.
  • If you add a mobile number to log in with: the number, and when a texted code last confirmed it.
  • While a company's free trial runs: a one-way code made from its owner's email address and login number, so the same inbox or phone cannot start a second trial beside it. It is deleted when the trial ends.
  • Your company's name, plan and seats, and the invoices we issue to it.
  • How your team uses mpulse: who replied, when, and how long it took. The scorecard and the weekly report count these.
  • Which chat each person on your team has open, and whether they are writing a reply in it, so two people do not answer the same customer at once. We keep only who, which chat and when, never what is being written. It stops showing within 20 seconds of them leaving the chat, and the record is deleted within a day.
  • Technical records that keep accounts safe: sign-in sessions with the device and IP address, and, if you turn notifications on, the address your browser gives us for them, or the push token of the mpulse phone app.
  • If you use the Agent page to train the AI assistant: the knowledge you give it, and the test messages you type there as a customer, with its answers. The day's test conversation is kept in your workspace and starts again the next day.
  • If your owners set up webhooks or calendar addresses: each webhook's address, the events it sends and its signing secret (encrypted), with a 30-day log of its deliveries (when, which event and how the address answered, never what was sent); and each calendar address (encrypted), with when a calendar app last read it.

We use this to run the service, bill you, help you when you ask, and keep it secure. Our legal grounds are the contract with you and our legitimate interest in running a safe service (Article 6(1)(b) and (f) of the GDPR, where it applies).

Each person you invite is told what is measured before they join.

If you wrote to a business that uses mpulse

That business decides what happens to your conversation, and we process it only on its instructions, as our terms with it set out. To see or delete your messages, please ask the business first.

For that business we hold:

  • Your messages, and any photos, files, videos or voice notes you send.
  • The name and profile picture the channel shows us, your ID and username on that channel, and your phone number if you wrote on WhatsApp and WhatsApp shared it.
  • Whether replies were delivered and read, and your reactions.
  • Notes the business adds about you.
  • Where the chat came from: the ad, link or campaign that brought you, or a source the business's team noted. For an ad or a post, that is its ID, title, text and picture or video, the post, product or form it showed, the link it points to (the site and the page only) and its welcome message; for WhatsApp, also Meta's click ID; and, when the business lets mpulse read its ads, the names of the ad, its ad set and its campaign.

If you wrote to the business on more than one channel, its team can join those chats into one person, so they read them together, and can undo that at any time.

The business can also send details of your chat to its own tools. Through a webhook, mpulse sends them to an address the business gives (its own system, or a service it uses, such as Zapier or Make): your name, phone number and email with your first message when you first write, how the chat ended when it is closed, and a booking's time, place and note. Through a private calendar address, the calendar app its team uses (such as Google Calendar) shows its bookings with your name, the place and the note. The business chooses these tools and is responsible for them.

We keep our own copy because Facebook, Instagram, WhatsApp and other channels do not keep one for the business. If you unsend or delete a message on Messenger or Instagram, its words and files are removed from mpulse, and from the raw notices Meta sent us about it. WhatsApp does not tell businesses when a message is deleted, so a WhatsApp message stays until the business deletes it with the chat, its retention setting removes the chat, or the business closes its mpulse account.

Photos, voice notes, videos and files in the conversation, the ones you send and the ones the business's team sends you, are copied into mpulse when they arrive, because the channels' own links expire. They are stored with the conversation and follow its retention and deletion.

If you wrote in the chat on a business's own website and left your email to get the answer there, we keep that address and when you agreed, and the business sees it in its inbox. If you leave before reading a reply, the reply is emailed to you in the business's name with a link back to the chat, and every such email has a link to stop them. While you chat we also note when you are typing (never what you type) and when your chat last checked for news.

On a business's own website, its chat keeps in your browser, in that site's storage, where your visits came from: the campaign tags and ad click IDs in the link you followed, the site that sent you, and the page you landed on. It keeps them for 90 days and sends them when you write, together with the page you wrote from. No IP address is kept for this. If the site's consent tool tells the chat that you declined such storage, nothing is kept or sent.

Your messages are never sent to an AI model or used to train one, never sold, and never used for advertising.

If you cannot reach the business, write to us and we will pass your request on.

Facebook, Instagram and WhatsApp data

A business connects a channel by signing in with Facebook (Facebook Login for Business) or through WhatsApp's own sign-up, and chooses there what mpulse may reach. From then on, Meta gives us:

  • Messenger: the Page's name, ID and picture, a Page access token, and the Facebook user ID of the person who connected it. For each person who writes to the Page: the ID Meta gives them for that Page, the name and profile picture Meta shares, their messages and attachments, reactions, delivery and read receipts, the ad or link they came from, and notices when a message is unsent or the conversation passes to another app.
  • Instagram: the professional account's ID, username, name and picture, reached through its linked Page and that Page's token. For each person who writes: the ID Meta gives them for that account, their name, username and profile picture, their messages and attachments, replies to stories, reactions, read receipts, and the ad or link they came from.
  • WhatsApp: the WhatsApp Business account's ID, the phone number's ID, display number and verified name, and an access token. For each person who writes: their phone number (their WhatsApp ID) when WhatsApp shares it, their WhatsApp user ID and username when they have them, their profile name, messages and media, the ad or post they came from with Meta's click ID for it, and the delivery and read status of the business's replies.
  • Ads, when the business lets mpulse read them: the names of the ads people came from, of their ad sets and campaigns, and each ad's picture.

We use this to show those conversations in the business's inbox, to send the replies its team writes, and to tell the team about new messages. Where each person came from (the ad or link, and the ad's names when the business lets mpulse read its ads) also goes into the business's own reports, its contacts file and its data exports, and, through mpulse's data API, webhooks and calendar addresses, to the business's own systems and the tools it connects, together with that person's name, phone number and email. We do not sell it, use it for advertising, build profiles of people from it, send it to an AI model, or share it with anyone but the business and the services listed under Who else handles data.

Access tokens are encrypted and never reach the browser. Disconnecting a channel deletes its token at once. Closing an account also unsubscribes mpulse at Meta from its Pages and WhatsApp Business accounts, unless another business on mpulse still uses them.

Removal and deletion through Meta

When the person who connected a Page or Instagram account removes mpulse in their Facebook settings, Meta tells us at once. We delete the access tokens of every Page and Instagram account they connected, and those channels stop until someone connects them again.

When they ask for their data to be deleted, Meta sends the request to https://app.mpulse.ge/api/channels/meta/data-deletion. We delete the same tokens, their Facebook user ID and any connection they had started and not finished, at once, and give Meta a confirmation code with a page where anyone holding the code can check the request. The code and its status are kept for 30 days.

Conversations already in a business's inbox are that business's records and stay with it. Delete your data explains how to have those removed.

AI

mpulse does not send customers' messages to any AI model, and the AI assistant does not answer customers.

On the Agent page an owner can teach the assistant about the business and test it in Try it, playing the customer. Those test messages and the business's knowledge go to Google's Gemini to write the test answer, on Google's paid terms, under which Google does not use them to improve its products. Before the assistant ever answers customers, this page will change and businesses will hear about it first.

If you used the chat or the form on this website

The chat on this website answers visitors from a script, so nothing you type there goes to an AI model. What you type may be saved in our database in Frankfurt, so we can test our AI assistant against real questions before it answers visitors. Please do not type anything sensitive.

People we invite to test the assistant get its answers: what they type goes to Google's Gemini, on Google's paid terms, to write the reply. The chat always says when the AI is answering, and a person is one tap away.

If you book a call in this chat or send the form on this website, what you give us there (your name and phone number, and your company and the channels your customers write on, if you gave them) is kept in our own mpulse inbox and emailed to the person who will call you.

Cookies

We use only the cookies the site needs: one remembers your language, and others keep you signed in, remember which workspace you opened, carry an invitation while you accept it, carry the terms you accepted through a sign-up with Google, or let an invited tester into the chat. We use no advertising or analytics cookies.

The mpulse chat on businesses' own websites keeps where your visits came from in your browser's storage for that site, for 90 days, as described above.

Who else handles data

  • Meta carries messages to and from Messenger, Instagram and WhatsApp.
  • Neon hosts our database, in Frankfurt.
  • Vercel runs the website and the app, in Frankfurt (region fra1).
  • Cloudflare keeps files larger than 1 MB that are sent in chats in its R2 storage in the European Union: photos, videos, voice notes and documents, from customers and from teams.
  • Resend sends our emails: invitations, password resets, weekly reports, alerts, and replies to website chat visitors who asked for them by email. The weekly report to a business's owners quotes the names and last messages of the customers still waiting for a reply, so those pass through Resend too.
  • GoSMS sends the text messages with the codes that confirm a mobile number and log you in with it, in Georgia.
  • Google handles Google sign-in. Its Gemini service writes answers only in the Agent page's tests and for invited testers of this website's chat, never for customers' messages.
  • If you turn notifications on in your browser, its push service (from Google, Apple or Mozilla) carries them to your devices, encrypted end to end, so that service cannot read them.
  • In the mpulse phone app, notifications go through Expo (650 Industries, Inc., in the USA), then Apple Push Notification service on an iPhone or Google's Firebase Cloud Messaging on Android. These services see a notification's text, including the preview of a customer's message, so they can deliver it.

Each one gets only what its job needs, under its own data processing terms. We share data with authorities only when the law requires it.

Where data is kept

Our database and servers are in the European Union, in Frankfurt: the database with Neon, and the website and the app with Vercel (fra1). Files larger than 1 MB are kept in the EU too, with Cloudflare R2. Meta, Resend, Google, Expo (in the USA) and the push services may handle data outside Georgia and the EU. For those transfers we rely on the safeguards in each provider's data processing terms, such as the EU's standard contractual clauses, as the Law of Georgia on Personal Data Protection and the GDPR require.

How long we keep it

A business chooses how long closed chats are kept: 3, 6, 12 or 24 months, or until it deletes them, which is the default. Every night, closed chats whose last message is older than that are deleted with their messages and files. Files picked in the inbox and never sent are deleted after a day.

The raw notices Meta sends us about new messages are kept for 30 days, so we can recover from errors, and are then deleted. When a message is unsent, or an account is closed, its part of them is removed at once.

What a webhook sends is kept only until the business's address takes it or our tries end, within about nine hours; the log of deliveries, without what they carried, is kept for 30 days.

An owner can download all of the business's data at any time from Settings, as JSON files in a zip.

An owner can also close the account there (Your data, then Close the account), by typing the workspace's name. Everything in it is removed from our live database and file storage at once: every chat, message, file, contact, note, channel and token, and its team loses access. The sign-in accounts of its people who are in no other team are deleted with it (the two that stay are below): their name, email, password hash, Google link and sign-in sessions. mpulse is unsubscribed at Meta from its Pages and WhatsApp accounts that no other business on mpulse uses, and the owners get an email confirming it.

Our database provider keeps a recovery history of the last 24 hours, so deleted data is gone from it within a day. We keep no other backups of the database.

Sign-in sessions end after 30 days without use. Someone an owner removes from a team loses access to it at once. If they are in no other team, their sign-in account stays, so they can be invited again, until they delete it themselves in Settings or ask us at info@mpulse.ge. Closing that team later does not delete it either: closing deletes only the accounts of the people still in the team at that moment. Two kinds of sign-in account stay: that of someone removed earlier from another team that still holds a record of their work there (replies or notes they wrote, chats assigned to them, files they uploaded, tags or contact details they added, invitations they sent, or something they did in its chats, such as assigning, closing or reading one), so that team's records keep showing who did the work, until they delete it themselves in Settings or ask us at info@mpulse.ge; and those of mpulse staff. Our accounting records of invoices are kept for as long as Georgian tax law requires.

Anyone can delete their own sign-in account at any time, in Settings: on the web under Your profile (Delete your account), and in the mpulse Chat app under Delete account. Their sign-in (email address, password hash, Google link and login number), sessions, photo, their profile in each team and the devices that get their notifications are deleted at once, and they get an email confirming it. If a team still holds a record of their work, the account stays only as a nameless placeholder, with no email address and no way to sign in, so that team's history stays whole. Someone who is a team's only member closes it with their account; the only owner of a team that others use first makes someone else an owner, or closes the team for everyone.

Saved website chats are deleted when we no longer need them to test the assistant, or sooner if you ask.

How we protect it

Each company's data is separated in the database, and every request is limited to the signed-in person's own company. Access inside a company is limited by role. Connections are encrypted, channel tokens are encrypted, and passwords are stored only as hashes. Every export and every change to how long chats are kept is recorded, and owners see the record in Settings.

If a breach puts personal data at risk, we tell the businesses affected without delay, and the authority within 72 hours, as the law requires.

Your rights

Under the Law of Georgia on Personal Data Protection, and the GDPR where it applies to you (for example if you are in the European Union), you can ask to see your data, correct it, delete it, restrict or object to how it is used, or take a copy in a common format. You can withdraw consent at any time, which does not undo what was already done. We make no decisions about people by automated means alone.

Write to info@mpulse.ge. If your data sits in a business's inbox, that business decides, and we pass the request on to it. If you think we got something wrong, you can complain to the Personal Data Protection Service of Georgia or, where the GDPR applies, to the data protection authority where you live.

Changes to this page

When something important changes, we update this page, change the date at the top, and tell businesses by email before it takes effect.

A Georgian platform for customer conversations.

info@mpulse.ge
Tbilisi, Georgia

Product

  • One inbox
  • Where every lead came from
  • Auto-replies
  • Reports
  • Bookings
  • Phone app
  • Webhooks and calendar
  • Pricing
  • Custom builds

Channels

  • Channels
  • WhatsApp
  • Instagram
  • Messenger
  • Website chat

Industries

  • Industries
  • Real estate and developers
  • Clinics and dentists
  • Beauty and salons
  • Car dealers
  • Online shops
  • Restaurants and delivery
  • Hotels and guesthouses
  • Fitness and studios
  • Schools and courses
  • Repair and services

Compare

  • Compare
  • mpulse or the WhatsApp Business app
  • mpulse or a spreadsheet and three phones
  • mpulse or Bitrix24
  • mpulse or FollowUP

Company

  • Log in
© 2026 mpulse
PrivacyTermsDelete your data