Effective date: 17 November 2026 · Version 1.12
This Privacy Policy explains how LTD Arilx (“Arilx”, “we”, “us”, “our”) collects, uses, and protects personal data across our websites at arilx.io, arilx.ai, studio.arilx.io, and app.arilx.io (together, the “Services”), and when you send a message to our Facebook Page (Arilx) or our Instagram account (@arilx.io), or to our Telegram bot (@ArilxBot).
Legal name: LTD Arilx (შპს არილიქს)
Company ID: 445839754
Registered address: 2 G. Volski St., Batumi 6000, Georgia
Contact for privacy matters: [email protected]
Arilx provides an AI-powered website builder and an AI chatbot builder, offered on a subscription basis. This policy is governed by the Law of Georgia on Personal Data Protection and, where applicable to users in the European Economic Area (EEA), the EU General Data Protection Regulation (GDPR).
Personal data is processed in two distinct situations, and our legal role differs in each.
(a) When you use our Services (arilx.io, arilx.ai, studio.arilx.io, or app.arilx.io) directly, or message our Facebook Page, Instagram account or Telegram bot, we are the data controller. This covers people who register an account, use the website or chatbot builder, chat with the Arilx assistant on our website, submit our contact or booking forms, or send a message to our Facebook Page (Arilx) or Instagram account (@arilx.io) or to our Telegram bot (@ArilxBot). For this data, Arilx decides why and how it is processed. Meta, which runs Messenger and Instagram and delivers those messages to us, is a separate controller for its own platforms (section 6). Telegram Messenger Inc., which runs Telegram and delivers messages between you and our bot, is a separate controller for its own platform, under its own terms and privacy policy (section 6).
(b) When a visitor interacts with a chatbot that our customer built and embedded on the customer’s own website or connected to the customer’s own Facebook Page, Instagram account or Telegram bot, or uses a website our customer published on arilx.app, we are a data processor. In that case our customer (the chatbot or website owner) is the controller, and Arilx only processes the visitor’s data (for example contact-form messages, bookings, chat messages on any of those channels, the contact details and booking requests a visitor leaves in the chat, and the visitor’s IP address when the page is served) on the customer’s behalf, under our Data Processing Agreement (https://arilx.io/dpa). The processing of chatbot conversations is described in our separate AI Assistant Privacy Policy, and our customers are responsible for providing their own privacy notice to their visitors. It also covers people who order, book or pay on our customer’s website or in its chat: their name, phone number, email address and delivery address, their orders and bookings, the codes we send by SMS or email to confirm a phone number or an email address, the addresses they save, their answer to whether the business may send them offers, and the emails they exchange with the business. Online payments are made on the page of the payment provider the business connected, into the business’s own account; we never see or store card details.
Email address, first and last name, phone number, country, and an encrypted (hashed) password. We use your phone number to send you sign-in and sign-up codes and account notices by SMS. If you sign in with Google, we receive your Google account identifier, email, and name from Google.
If you send a message to our Facebook Page (Arilx) or our Instagram account (@arilx.io), Meta delivers it to our systems through its Messenger Platform. Our systems receive the content of your message (text, and any photos, voice notes or files you send), the conversation identifier Meta assigns to you for our Page or account (a page-scoped or Instagram-scoped ID), and the time of each message. When Meta provides it, our systems also receive the name on your profile: your first and last name on Messenger, your name or username on Instagram. Our team sees it next to the conversation in our Arilx dashboard, so that the person who replies to you can address you by name. It may be sent to the AI provider with a message, so that the assistant can address you by your first name (section 5), and it is deleted together with the conversation (section 8). We do not store your profile picture, and our systems do not receive your gender or language from Meta. Members of our team who open the conversation in Meta’s own inbox (Meta Business Suite or the Instagram app) also see what Meta shows them there, including your public profile name and photo.
Our AI assistant answers these messages, and sometimes a member of our team replies too (section 5). We reply only inside conversations you start, and we do not send marketing messages on Messenger or Instagram.
If you send a message to our Telegram bot, Telegram delivers it to our systems. We keep the chat identifier Telegram assigns to your chat with our bot, the text of your message (including any caption), and the time of each message. We also ask Telegram for the name on your profile and keep it: your first and last name, or your username if your profile has no name. Our team sees it next to the conversation in our Arilx dashboard, so that the person who replies to you can address you by name. It may be sent to the AI provider with a message, so that the assistant can address you by your first name (section 5); your username is not sent. It is deleted together with the conversation (section 8). We do not store your Telegram profile photo, bio, language or phone number, even when Telegram includes them in what it delivers to us. Photos, voice notes, files and other attachments are not downloaded: we record only that one was sent. The chat identifier is never sent to our AI providers.
Our AI assistant answers these messages, and sometimes a member of our team replies too (section 5). We answer only in chats you start, and we do not send marketing messages or follow-up messages on Telegram.
Telegram Messenger Inc. runs Telegram and, for its own platform, acts as an independent controller under its own terms and privacy policy (https://telegram.org/privacy), which also explains how Telegram handles your data and where it stores it.
If you buy a domain through us or move one to us, we collect the registrant details the registrar requires: your name, your organisation’s name (for a company), address, phone number and email address. We send them to the registrar once, to register the domain in your name.
Subscription payments are processed by Bank of Georgia on its own secure payment page. You enter your card details directly with the bank.
We never receive, see, or store your full card number or CVV. To start a payment we send the bank only the order reference, the amount and currency, and the name and identifier of the plan; your name, email address and phone number are not part of that request. To let you see and reuse your saved payment method, and to renew your subscription, we store a limited set of payment details returned by the bank: the cardholder name, the card expiry date, the last four digits of the card, and a secure payment token issued by the bank. We do not store the full card number or security code.
The Services are intended for users aged 16 and over. We do not knowingly collect personal data from anyone under 16. If you believe a child under 16 has provided us data, contact [email protected] and we will delete it.
| Purpose | Legal basis |
|---|---|
| Creating and managing your account | Performance of a contract |
| Providing the website and chatbot builder, including AI generation | Performance of a contract |
| Processing your chatbot conversations and documents through AI models | Performance of a contract |
| Alerting you by email to the leads and booking requests your chatbot collects | Performance of a contract |
| Delivering your chatbot on the channels you connect (Facebook Messenger, Instagram, Telegram) and showing you those conversations | Performance of a contract |
| Processing subscription payments and renewals | Performance of a contract |
| Responding to your contact requests and managing bookings | Performance of a contract / legitimate interest |
| Answering messages you send to our Facebook Page, Instagram account or Telegram bot | Legitimate interest / steps at your request before entering a contract |
| Transactional emails (verification, password reset, booking confirmations) | Performance of a contract |
| Newsletters or marketing (only if you opt in) | Your consent |
| Analytics, measurement, heatmaps, and session replay on arilx.io | Your consent |
| Measuring our advertising and showing our ads to past visitors (Meta Pixel on arilx.io, arilx.ai and studio.arilx.io) | Your consent |
| Keeping the Services secure and preventing fraud and abuse | Legitimate interest |
| Complying with legal obligations | Legal obligation |
We may display the public content of published websites as examples of our work, as described in the Terms of Service. This uses only what you have made public; form submissions, bookings and visitor data are never used. To opt out, write to [email protected].
We do not sell your personal data, and we do not use it for automated decision-making that produces legal or similarly significant effects on you.
Our Services use three AI providers. Anthropic (Claude models) powers the AI website builder: the brief you write, the content of your site, and your edit requests are sent to it to generate and change your site. Google (Gemini API) powers chatbots and the assistant: message text, conversation history, your chatbot configuration, uploaded document text, and our instructions are sent to it. OpenAI (GPT models) writes a chatbot’s answers when its owner has chosen Advanced answer quality: it receives the same data for that chatbot (message text, conversation history, the chatbot’s configuration and knowledge, and our instructions), while Google still detects the language and translates where needed, and writes the answer whenever OpenAI cannot. The name, email and phone number that chat visitors enter in the chat’s contact fields, and their IP address, are not sent to any provider. A visitor may also type contact details into a message, for example to ask for a call back or to request a booking; they are then part of the message text, which is sent to the provider so that the assistant can take the request.
Messages you send to our Facebook Page or Instagram account may be answered by our AI assistant (Google Gemini API, or OpenAI if we set it to Advanced answer quality). The text of your messages and the conversation history are sent to that provider to write the reply. With some messages your profile name is sent too, so that the assistant can address you by your first name; the conversation identifier Meta assigns is never sent. The assistant’s first reply tells you that it is an automated assistant. If you want to talk to a person, the assistant gives you a link to contact us or to book a meeting.
Messages you send to our Telegram bot may be answered by the same assistant. The text of your messages and the conversation history are sent to the AI provider that writes the reply (section 6). With some messages your profile name is sent too, so that the assistant can address you by your first name; your username is never sent, and neither is the chat identifier Telegram assigns. The assistant’s first reply tells you that it is an automated assistant.
The replies of our assistant on arilx.io are written by OpenAI (GPT models). The text of your messages, the conversation history, the parts of our knowledge that relate to your question, and our instructions are sent to OpenAI to write the reply. If you gave us your name, your first name may be sent too, so that the assistant can address you by it. If OpenAI cannot answer, Google writes the reply. Google also always turns your question into a search of our knowledge.
All three providers are used under their commercial (paid) terms, under which they do not use your data to train their AI models. OpenAI may keep the text it receives for up to 30 days to check for abuse, then deletes it.
AI output can be wrong; see the Terms of Service.
We use the following service providers, who process data only on our instructions. This table is the complete list; we update it before we start using a new provider.
| Provider | Purpose and data sent | Location |
|---|---|---|
| Anthropic PBC | AI website builder: your brief, site content, and edit requests | USA |
| Google LLC | Gemini API (chatbot and assistant: messages, conversation history, configuration, document text); Google Sign-In (account identifier, email, name); Google Calendar / Meet (booking details); Google Analytics 4 on arilx.io (only with your consent) | EU / USA |
| OpenAI OpCo, LLC | OpenAI API (chatbot answers at Advanced answer quality, and our assistant on arilx.io): message text, conversation history, the chatbot’s configuration and knowledge | USA |
| Microsoft Corporation | Microsoft Clarity analytics, heatmaps, and session replay on arilx.io (only with your consent) | EU / USA |
| Meta Platforms Ireland Ltd. | Advertising measurement and ad audiences (Meta Pixel) on arilx.io, arilx.ai and studio.arilx.io, only with your marketing consent; Messenger Platform: delivering the messages you send to our Facebook Page and Instagram account, and our replies; when you connect your own Facebook Page or Instagram account to your chatbot, the messages your visitors send there and your chatbot’s replies | EU / USA |
| Amazon Web Services (AWS) | Cloud hosting, database and file storage (account data, sites, uploads, submissions, chat conversations on every channel, including messages to our Facebook Page and Instagram account, channel access tokens in encrypted form, and catalog images); region: EU (Stockholm) | EU (Sweden) |
| Amazon SES (AWS) | Sending transactional and notification emails; sending emails on a business’s behalf to its buyers and receiving the replies and other incoming email of the business: sender and recipient email addresses and message content, including attachments | EU |
| Cloudflare, Inc. | CDN, DNS, and DDoS protection for arilx.io and arilx.app: every request to our sites, including the visitor’s IP address | Global |
| uBill | Sending SMS messages (sign-in and sign-up codes, account notices; and, for our customers’ businesses, order and booking updates and verification codes to their buyers): the phone number and the text of the message | Georgia |
| INWX | Domain registration, transfer and renewal: the registrant’s name, organisation, address, phone number and email address, which the registrar passes to the domain registry; for some domain endings these details are public in WHOIS | Germany (EU) |
| Bank of Georgia | Card payment processing on the bank’s own payment page: we send the bank the order reference, the amount and currency, and the name and identifier of the plan; you enter your card details on the bank’s page, and we receive the cardholder name, expiry, last four digits, and a payment token | Georgia |
| Unsplash (Unsplash Inc.) | Stock photos: search keywords from our servers; photos on published sites are loaded directly by the visitor’s browser from images.unsplash.com, so the visitor’s IP address and browser details reach Unsplash | USA / global |
| MaxMind (GeoLite2) | Country lookup from IP address, done against a database stored on our own servers; no visitor data is sent to MaxMind | - |
Meta is the exception to “only on our instructions”: for data collected through the Meta Pixel, and for messages sent through Messenger and Instagram, Meta also acts on its own behalf under its own privacy policy.
Telegram Messenger Inc. is not one of these service providers. It delivers messages between people and the Telegram bots connected to Arilx and, for its own platform, acts as an independent controller under its own terms and privacy policy (https://telegram.org/privacy).
Flitt, the payment provider a business can connect to take online payments from its own buyers, is not one of these service providers: it is the business’s own provider, and the money goes to the business’s own account. On the business’s instruction we send Flitt the order reference, the amount and currency and, when the buyer gave one, the buyer’s email address; the buyer enters card details on Flitt’s page, and we never receive them.
We may also disclose data where required by law, to protect our legal rights, or in connection with a business transfer (e.g. a merger or acquisition), in which case you will be notified.
Some of our providers (in particular Anthropic, Google, OpenAI, Meta, Cloudflare, and Unsplash) may process your data outside Georgia and the EEA, including in the United States. Transfers from Georgia follow Article 37 of the Law of Georgia on Personal Data Protection. The United States is not among the countries recognised as giving an adequate level of data protection, so transfers there rest on appropriate safeguards agreed with each provider (Article 37(2)(b)), namely its data processing terms, which include standard contractual clauses, and, where Article 37(3) of that Law requires one, on a permit of the State Audit Office of Georgia. Transfers to providers in the EEA (Amazon Web Services and Amazon SES, Sweden) rely on the adequate level of protection there. Where the GDPR applies, transfers outside the EEA rest on the standard contractual clauses in those providers’ terms.
Telegram is not one of our providers. When you write to a Telegram bot, your messages and the replies pass through Telegram’s own servers, as its privacy policy describes (https://telegram.org/privacy); you chose that channel, and our replies reach you only through it. Telegram processes that data as an independent controller under its own policy.
| Data | Retention period |
|---|---|
| Account and profile data | While your account is active; deleted within 90 days of account closure |
| Chat conversations and chat-visitor data | 6 months, then deleted |
| Conversations of your chatbot on a connected Facebook Page or Instagram account (our copy) | 6 months, then deleted. The conversation also stays in Messenger or Instagram, for the visitor and for you, under Meta’s own policy |
| Conversations of your chatbot on a connected Telegram bot (our copy) | 6 months, then deleted. The conversation also stays in the visitor’s own Telegram app, under Telegram’s own policy |
| Leads your chatbot collected (the contact details, requests and booking requests visitors leave in the chat) | Kept for you while the chatbot exists; deleted when you delete the lead, the chatbot or your account |
| Channel access tokens and Telegram bot tokens | Until you disconnect the channel, delete the chatbot or close your account; then deleted |
| Messages to our Facebook Page and Instagram account (our copy, with your profile name when Meta provides it) | 6 months, then deleted. The conversation also stays in Messenger or Instagram under Meta’s own policy |
| Messages to our Telegram bot (our copy, with your profile name) | 6 months, then deleted. The conversation also stays in your own Telegram app, under Telegram’s own policy |
| Uploaded documents, chatbot knowledge (the original text and its English copy), your chatbot’s business card, actions and catalog (items and images), and generated websites | While your chatbot or subscription is active |
| Contact and booking form submissions | Up to 12 months, then deleted |
| Analytics and session-replay data on arilx.io (only with your consent) | Microsoft Clarity: up to 30 days. Google Analytics 4: the retention period configured in our GA4 property (at most 14 months) |
| Meta Pixel data on arilx.io, arilx.ai and studio.arilx.io (only with your marketing consent) | The `_fbp` cookie lasts up to 90 days; Meta keeps the data it receives under its own retention policy |
| Server logs (including IP address) | A limited period, for security purposes |
| Customer-website visitor data (form messages, bookings) | Kept for the website owner while their site exists; deleted without undue delay when the owner deletes the site or the account |
| Orders, bookings, buyers’ contact details, saved delivery addresses and business email of a customer’s business | Kept for the business while it exists in Arilx; deleted when the owner deletes the business or the account |
| Verification codes sent to a business’s buyers | A code works for a short time only; we keep a one-way hash of the code and of the number or address it was sent to, not the code itself |
| Domain registrant details | Kept with the domain order, for as long as the law requires us to keep billing records |
| Backups | Up to 30 days |
Under Georgian law and the GDPR (where applicable), you have the right to access, rectify, erase, restrict, or object to the processing of your personal data; to data portability; and to withdraw consent at any time where processing is based on consent.
To exercise any of these rights, contact us at [email protected]. We will respond within 30 days. If you are a visitor to a customer’s website and your request is about data that website collected, contact the website owner first: they are the controller. We help them respond. You may also lodge a complaint with the State Audit Office of Georgia, which supervises personal data protection, or, if you are in the EEA, with your local data protection authority.
To have our copy of a Messenger or Instagram conversation deleted, email [email protected] or say so in the conversation itself. We delete our stored copy within 30 days and, where Meta’s tools allow, remove the conversation from our Page inbox. We cannot delete the copy in your own Messenger or Instagram app; that copy, and what Meta keeps, are governed by Meta’s privacy policy.
To have our copy of a Telegram conversation deleted, email [email protected] or say so in the conversation itself. We delete our stored copy within 30 days. This does not delete the conversation in your own Telegram app; that copy, and what Telegram keeps, are governed by Telegram’s privacy policy.
We apply appropriate technical and organisational measures, including encryption of data in transit, hashed passwords, access controls, and secure http-only cookies for authentication, to protect your data against unauthorised access, loss, or misuse. Access tokens for the channels you connect are stored encrypted. Your visitors’ conversations are visible only to you (and the people you allow to use your Account) and to the members of our team who need access to run and support the Services.
We may update this Privacy Policy from time to time. We will post the updated version on arilx.io and update the effective date above. Significant changes will be communicated to you.
LTD Arilx · [email protected] · registered address: 2 G. Volski St., Batumi 6000, Georgia.
© 2026 Arilx. All rights reserved.