Last updated 22 November 2026

Privacy policy

Inclamo is a voice assistant that answers a Shopify store's phone, and Inclamo Helpdesk, an inbox in which an online store answers its customers. This policy says what we collect, why, who processes it on our behalf, how long we keep it, and how to exercise your rights. It applies to merchants who install the Inclamo app, to their customers who call the store, to customers who write to a store through Messenger, Instagram or WhatsApp when the store uses Inclamo Helpdesk (section 10), and to visitors of this website (section 11). To have your data deleted, see Data deletion.

1. Who we are

Inclamo is a product of Aceverse LLC (ТОВ ЕЙСВЕРС), Ukraine, est. 2026, EDRPOU 46394755. Questions about data: hello@inclamo.com.

Registered details: ТОВ «ЕЙСВЕРС» (Aceverse LLC) · ЄДРПОУ 46394755 · 08176, Україна, Київська обл., Бучанський р-н, с. Софіївська Борщагівка, вул. Клубна, буд. 12, кв. 87 · тел. +380 63 020 44 91

2. What the app reads from Shopify

With the merchant's authorisation, the app reads from the Shopify Admin API only what a call needs:

  • Orders, by the order number a caller names: the order number, its date, fulfilment and payment status, the items ordered with their quantities (no prices), and each shipment's carrier, tracking numbers and items, and whether its delivery is recorded. Before the assistant tells anything about an order, it checks that the caller may hear it: it compares the ZIP code the caller says with the ZIP code of the order's shipping or billing address or, when the merchant has switched on caller recognition, the number the call comes from with the phone of the order's customer. The order's ZIP code and its customer's phone are only compared: Inclamo does not store them and never reads them back to the caller.
  • Customers, only when the merchant has switched on caller recognition or a caller asks for a one-time code (section 3). With caller recognition: the customer whose phone is the number the call comes from, with their first name and their latest orders, so the assistant can greet them and offer their orders without asking for an order number. For the code: the customer whose email or phone number the caller gives, with the phone on their record and, once the code matches, their first name and latest orders.
  • Draft orders: when a recognised caller asks on the call to order a part, the app creates a draft order in the shop for that customer, and the shop sends its own invoice to the customer's email after the assistant has read the address back masked and the caller has confirmed it. The email is not stored by Inclamo and is never read aloud in full. A caller whose email the shop does not have, including a caller the app does not recognise, may spell one for the invoice instead: the assistant spells it back letter by letter, creates the draft only after the caller confirms it, and uses the address only for that order's draft and invoice (section 3).
  • Products and inventory: titles, tags, variants, prices and stock, to find a part that fits a vehicle and to tell its price and availability.
  • The shop's published policies, such as shipping and refunds, which the assistant answers from.

In Shopify's terms, orders and customers are protected customer data (level 1). Four customer fields are protected at level 2, and Inclamo asks Shopify for them for these reasons only:

  • phone: to recognise a caller by the number they call from, and to tell a customer about their own order without asking for the ZIP code when the call comes from the phone on the order; and the phone on the record of a caller who asks for a one-time code, the only number the code goes to;
  • name: to greet a recognised caller, or a caller the code confirmed, by first name and to address a callback ticket to the right person;
  • address: the ZIP code of an order's shipping or billing address only, compared with the ZIP code the caller says;
  • email: to send the shop's invoice for a draft order the caller asks for to the recognised customer's own email, after the caller has confirmed it; and to find the record of a caller who gives their email for a one-time code.

3. What we collect during a call and from the merchant

During a call to the store's number: the caller's phone number as the network presents it, a transcript of the conversation with a short summary of it, and what the caller tells the assistant (a vehicle, a part, an order number, a ZIP code for the check, a name and a phone for a callback ticket, an email for the invoice of a draft order when the shop has none for the caller). An email the caller spells is kept on the draft order in the shop and, like the rest of the conversation, in the call's transcript for 30 days (section 6); the app's own database does not store it, and the app's log keeps it only masked. The audio of the call passes through our providers while the call lasts (section 5). We do not record or keep the audio of store calls in this version: a store call is kept as its transcript.

By WhatsApp, the assistant may send a caller three messages, and no other:

  • a one-time code, when a caller the assistant cannot otherwise confirm asks for one: it goes only to the phone on the store's record of the email or number the caller gives, never to a number the caller says, and confirms them for that call only. The app keeps the customer's id and a keyed hash of the code, never the code, the phone or the email;
  • the link to their request, after a request that waits for photos in the store's chat and only when the caller says yes to it: it goes only to the number the call comes from and opens the store's chat with the order number and the request's reference;
  • the link to a product's page in the store, when the caller asks for one: it goes only to a number the caller confirms on the call, the number they call from or one they give and confirm.

All three go from Inclamo's WhatsApp sender, for a store where Inclamo has switched WhatsApp on. Text messages (SMS) are off by default for every store: they carry only the first two, to the same numbers, from Inclamo's own number, and are switched on for a store only after Telnyx has verified that number. No link to a cart is sent by WhatsApp or by text message.

From the merchant: the assistant's settings (for example the greeting, the hours, the number calls are transferred to and the address for notices), and the name and email of the staff member who opens the app, as Shopify gives them at login.

4. Why

To answer the merchant's phone: find parts that fit a vehicle, tell the status and tracking of an order, take a return or a callback request, create a draft order the caller asks for, confirm a caller by a one-time code and send them the link to their request or to a product they ask for (section 3), and hand the call to a person. Nothing else. We do not use the data of merchants or their customers to train or fine-tune models. The processors that work for Inclamo (section 5) are bound by their written terms not to train models on this data, except Meta, which delivers our WhatsApp messages, and ElevenLabs, for an assistant whose voice is set up on it: Meta's terms for WhatsApp have no written condition on training models, and ElevenLabs' terms bind it not to train on this data only once Inclamo's account has opted out of training. By WhatsApp, a caller gets from us only the one-time code, the link to their request and the link to a product (section 3). A merchant's own Gorgias account is not one of them: it works under the merchant's own terms with Gorgias (section 5). We make no automated decisions with legal effect about anyone.

5. Who processes it

ProcessorWhat it does for InclamoWhere
Shopifythe shop's orders, products and customers, read through the Admin APICanada, US
Hetznerhosting of the app, its databases, the voice platform and our own media server; our encrypted database backupsEU (Germany, Finland)
OpenAIthe assistant's voice: the whole conversation, audio in and out, during the call; and its replies in a store's chat, from the chat's text (see the Gorgias row)US
Microsoft (Azure OpenAI)the same OpenAI models, run by Microsoft in Inclamo's own Azure resource: the assistant's voice during the call and its replies in a store's chatstored in the US; processed in any Azure region where the model is deployed
Anthropicthe part classifier and the summary of a callUS
Telnyxtelephony: the store's number and the call audio between the caller and our voice platformUS
Meta (WhatsApp)delivering the WhatsApp messages to a caller (section 3): the one-time code, the link to their request and the link to a product, from Inclamo's sender through TelnyxMeta data centres
Googleemail to the merchant about a callback ticket, from Inclamo's Google Workspace mailboxGoogle data centres
ElevenLabsonly for an assistant whose voice is set up on ElevenLabs: speech recognition, the caller's audio turned into text during the call, and speech synthesis, the assistant's replies turned into speechstored in the US; processed also in other countries where its providers work
Groqonly for an assistant set up on Groq: the text model that writes the assistant's replies from the conversation's text and does that assistant's other text work on the call (OpenAI's open-weight model gpt-oss-120b, run by Groq)US and other countries where Groq or its providers work; its logs are kept in the US
Gorgias (the merchant's own account)the merchant's own helpdesk, connected by the merchant, where the assistant answers the store's chat and leaves notes and tags for the store's team, under the merchant's own terms with GorgiasUS, EU, Australia

Each of them except Gorgias, Meta and ElevenLabs is bound by its written terms not to train models on this data; the app's "Data and privacy" page cites each condition. A merchant's Gorgias account is the merchant's own, under the merchant's own terms with Gorgias, which let Gorgias use the account's data to build and improve its own models as far as the law permits. OpenAI keeps API data for up to 30 days for abuse monitoring under its terms. Microsoft does not make the prompts and replies available to OpenAI; it may process them in any Azure region where the model is deployed, and keeps what it stores, its abuse monitoring included, in the Azure geography of Inclamo's resource, the United States. The WhatsApp messages (section 3) go through Telnyx and Meta from Inclamo's sender, and a text message, once switched on, through Telnyx from Inclamo's own number. Meta's terms make it Inclamo's processor for the WhatsApp messages, which it keeps for up to 30 days; they have no written condition on training models, so the app shows Meta's condition as pending. ElevenLabs and Groq work only for an assistant whose configuration names them; no other assistant sends them anything. ElevenLabs' terms make it Inclamo's processor and let it use what it processes to improve its services and models unless the customer's account opts out of training; until the opt-out of Inclamo's account is on file, the app shows ElevenLabs' condition as pending. ElevenLabs keeps what it processes as its privacy policy allows, with no fixed term, and stores it in the United States. Groq's terms forbid it to train models on what it processes; by default it keeps no request, and it logs one for up to 30 days only to troubleshoot its service or investigate abuse. The list in the app is updated before a new processor handles data.

6. How long we keep it

  • A caller's phone and name in a callback ticket: 30 days from the ticket, then erased by a daily job; the ticket stays without them.
  • Call reports (the caller's number, the transcript, the summary and what the assistant collected): 30 days from the call, then erased by a daily job in the voice platform and in our data store; a line with the call's outcome and times stays without them.
  • The audio of store calls: not recorded in this version.
  • The log of who read a customer field, and when: at least as long as the data it logs; it holds no customer field itself.
  • The name and email of the merchant's staff member: until the app is removed.
  • Encrypted database backups: 30 days. Data erased from the databases stays in the backups until they expire, at most 30 days more.

7. Your rights and Shopify's requests

Customers may ask, through the merchant or by writing to us, for a copy of their data or for its erasure. Shopify forwards such requests to us: a request for a copy is answered within 30 days; an erasure clears the app's own records at once, and the call reports with the customer's number are erased within 30 days. Merchants may remove the app at any time. Shopify then asks us, 48 hours after the removal, to erase the shop's data, and the app erases its own records at that moment; call reports are erased 30 days after each call, as in section 6.

8. Where the data is

The app, its databases, the voice platform and our media server run on our server at Hetzner in Germany; the encrypted backups are kept in Hetzner storage in the EU. During a call, OpenAI and Telnyx process the call in the United States; where OpenAI's model runs through Microsoft in Inclamo's Azure resource instead, Microsoft may process the call in any Azure region where the model is deployed and keeps what it stores in the United States. For an assistant set up on ElevenLabs and Groq, ElevenLabs turns the caller's speech into text and the replies into speech and stores what it keeps in the United States, and Groq writes the replies in the United States or another country where it or its providers work, keeping its logs in the United States. Anthropic receives the transcript for the summary in the United States. Email to merchants goes through Google. Shopify is the merchant's own platform.

9. Security

The app, its API and this website's voice gateway are served over TLS only, and the app reaches Shopify and our providers over HTTPS. Database backups are encrypted before they leave the server, and the key that reads them is not kept on the server. Credentials the app stores are sealed with AES-256-GCM. The app's databases are kept on an encrypted volume on our server.

Every read of a customer field by the assistant or by a screen of the app is logged, and the merchant sees the count on the app's "Data and privacy" page. Production data stays on the server, and tests run on separate test databases. Two-factor sign-in is required on the staff accounts that run Inclamo: code hosting, servers, Shopify and our providers.

A security incident affecting a merchant's data is reported to the merchant without undue delay, and within 24 hours of its detection under our incident response policy.

10. Inclamo Helpdesk: Messenger, Instagram and WhatsApp

Our role. Inclamo Helpdesk is an inbox in which an online store answers its customers. When a store connects its Facebook Page, Instagram account or WhatsApp Business number, we process the messages on behalf of that store and only on its instructions. The store is the controller of its customers' data; Aceverse LLC is its processor.

What we receive from Meta. When a customer writes to a connected store through Messenger, Instagram or WhatsApp, we receive:

  • the name and profile picture the customer shows in that channel;
  • the customer's identifier in that channel (a page-scoped ID in Messenger, an Instagram-scoped ID in Instagram);
  • in WhatsApp, the customer's phone number;
  • the text of the messages and the attachments the customer sends (images, files, voice notes);
  • the time of each message and its delivery status.

Why. Only to show the conversation to the store's team in the helpdesk and to send the store's replies back through the same channel. Inclamo's AI agent does not answer Messenger, Instagram or WhatsApp conversations; before it does, this policy will name its provider.

What we do not do. We do not sell this data, share it with advertisers or build advertising profiles. We do not use it to train or fine-tune AI models, and we do not use WhatsApp data for any purpose other than the store's conversation with that customer.

Separation. Each store's conversations are kept in its own account in the helpdesk, and a store's team sees only that store's conversations.

Who processes it.

ProcessorWhat it doesWhere
OVHhosting of Inclamo Helpdesk: its database, the conversations and the attachmentsEU (France)
Metadelivers the messages between the customer and the store through Messenger, Instagram and WhatsApp, under Meta's own termsMeta data centres

How long we keep it. As long as the store uses Inclamo Helpdesk. When the store deletes a channel's inbox, that channel's conversations and attachments are deleted with it. When the store stops using the helpdesk and asks us to close its account, we delete all of its conversations, attachments and contacts within 30 days of the request.

Deletion. A customer, the store or Meta may ask us to delete this data at any time; see Data deletion. We complete a request within 30 days and confirm it by email.

Security. The helpdesk is served over TLS only, and it reaches Meta over HTTPS. The access tokens of a store's Page, Instagram account and WhatsApp number are used only for that store. To report a vulnerability, write to hello@inclamo.com.

www.inclamo.com

11. This website

We measure how www.inclamo.com is used with Google Analytics 4 and Microsoft Clarity (pages viewed, clicks, scrolling, session replays with form fields masked) and RB2B, which may match a U.S. visitor to a public business profile so we can see which companies are interested. Visitors from the UK, the EEA and Switzerland are asked first, and nothing that identifies a browser is stored until they agree. When we email a business contact, the link to this site may carry a personal code; if you follow it, we note the visit and what you did on the page (for example, played the demo call or booked a call) in our customer records, so we can follow up. To stop this, decline cookies, use the unsubscribe link in our email, or write to us.

A conversation with the voice agent on this site is recorded, as the agent says when it begins: the audio and the transcript are kept on our server and deleted 30 days after the conversation. The agent's voice runs on OpenAI's model, through OpenAI or Microsoft's Azure. If you book a call with us, your name, email, store address and, if you give it, your phone number go to our booking calendar at Cal.com, and a link to the booked call is sent by WhatsApp, through Telnyx and Meta, when you ask for it. Our server keeps a record of each conversation (its time and the address your browser connected from) and of each booking and message (the details you gave); a deletion period for this record is not set yet, and we delete it when you ask.

When you send a form on this site, the details you give go to our customer records (a scenario request becomes a conversation in Inclamo Helpdesk), and a notification with them goes to our team in Slack, so we can answer you.

12. Changes

Changes to this policy are dated at the top of this page.

Inclamo