Skip to main content

Legal documents

Privacy Policy

Version 2.8 Effective from November 13, 2026
On this page
  1. Summary
  2. Contents
  3. 1. Who we are and how to contact us
  4. 2. Who you are and which sections apply to you
  5. 3. Controller and processor: our role
  6. 4. If you use AnyDialog for your business
  7. 5. If you visit our website
  8. 6. If you talk to a customer's AI assistant
  9. 7. Voice and phone
  10. 8. Artificial intelligence
  11. 9. When the assistant acts on the customer's systems
  12. 10. If you ask us for support
  13. 11. If you are a business we contact
  14. 12. Who we share data with
  15. 13. How long we keep data
  16. 14. Transfers outside the European Union
  17. 15. How we protect data
  18. 16. Cookies
  19. 17. Your rights
  20. 18. Children
  21. 19. Changes to this policy

Version 2.8 · last updated November 13, 2026

This policy explains what personal data we process, why, who we share it with, how long we keep it and how you can exercise your rights. It covers our website, the AnyDialog platform and the AI assistants that our customers place on their channels. It is written under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR).

Summary

  • The controller is GENIARIS S.R.L. For any privacy question, write to privacy@geniaris.com.
  • We decide how to process the data of your account, of our website and of support requests: we are the controller.
  • We process conversations with a customer's AI assistant on behalf of that customer: the controller is the business you are talking to, and its privacy policy applies.
  • Messages go through an artificial intelligence provider to produce the answer. We do not use them to train models.
  • Today, conversations are not deleted automatically: they stay until the customer deletes them or asks us to. Section 13 explains this.

Contents

  1. Who we are and how to contact us
  2. Who you are and which sections apply to you
  3. Controller and processor: our role
  4. If you use AnyDialog for your business
  5. If you visit our website
  6. If you talk to a customer's AI assistant
  7. Voice and phone
  8. Artificial intelligence
  9. When the assistant acts on the customer's systems
  10. If you ask us for support
  11. If you are a business we contact
  12. Who we share data with
  13. How long we keep data
  14. Transfers outside the European Union
  15. How we protect data
  16. Cookies
  17. Your rights
  18. Children
  19. Changes to this policy

1. Who we are and how to contact us

The data controller is GENIARIS S.R.L., VAT number 06471840659, REA SA-525962, registered office at Piazza XXIV Maggio 26, 84122 Salerno (SA), Italy.

You can contact us:

Only our authorised employees and contractors process data, for the work they are responsible for (technical, support, administration, sales), together with the providers listed in section 12.

2. Who you are and which sections apply to you

Who you are Our role Sections
Administrator or member of an organisation that uses AnyDialog controller 4, 12–19
Partner agency or affiliate controller 4, 12–19
Visitor to our website, including if you talk to our assistant or try the voice demo controller 5, 6, 7, 8, 12–19
Person who writes to or calls a customer's AI assistant processor on behalf of the customer 6, 7, 8, 9, 12–18
Person who opens a support request controller 10, 12–19
Business (or its contact person) we reach out to about the service controller 11, 12–19

3. Controller and processor: our role

As controller, we decide why and how data is processed: accounts, payments, the website, support, partner programmes and sales contacts.

As processor (Article 28 GDPR), we process data on behalf of our customers and follow their instructions. This covers:

  • the conversations of their AI assistants and the data the assistants collect (for example name, email, phone number, request);
  • appointments booked and calls made on the customer's behalf;
  • the documents, websites and texts the customer uploads as a knowledge base, which may contain data about other people.

For this data the customer is the controller: the customer decides what it is used for, the legal basis, how long it is kept and how people are informed. The conditions under which we work on the customer's behalf are in the Terms of Service, in the data protection section.

4. If you use AnyDialog for your business

4.1 Account and use of the dashboard

Data Why Legal basis
Name, email, password (stored only in non-reversible form), language, role in the organisation creating and managing the account, providing the service performance of the contract
If you sign in with Google: Google ID, address of your profile picture, access tokens signing in with Google performance of the contract
At sign-up: IP address, browser, browser languages, time taken to fill in the form, Google Workspace domain if any protecting sign-up against automated registrations legitimate interest (security)
Which version of the Terms you accepted and which version of this policy you were shown, when, from which IP and browser being able to show what you accepted and what we showed you legitimate interest
Date and IP of your last sign-in; log of actions on your profile (action, IP, browser) account security legitimate interest
Organisation and billing details: company name, VAT number, address, e-invoicing recipient code invoicing performance of the contract; legal obligations
Subscription history: plan changes, who made them, IP and browser managing the subscription, handling disputes performance of the contract; legitimate interest
Invitations to new members: email of the person invited letting a colleague join performance of the contract (the person inviting); legitimate interest (the person invited)
If you upload a key for an AI provider: the last four characters, who uploaded it (name, email, IP) tracking who changed a credential legitimate interest
If you connect Google Calendar: the email of the connected Google account and the access tokens (encrypted) letting the assistant book appointments performance of the contract
Test conversations with your assistants and content you upload providing the service performance of the contract

Required data. Your name, email and password (or signing in with Google) are needed to create the account, and billing details are needed to buy a plan: without them we cannot provide the service. Technical data is collected automatically while you use the service; you provide the rest when you use the feature that needs it.

Payments. Payment takes place on Stripe, which collects your card details, email, billing address and VAT number. We only keep the Stripe customer ID, the card type and the last four digits.

Communications. We write to you about the service: confirmations, invitations, invoices, renewals, security notices, support replies. We do not send newsletters and we do not use your data for advertising.

Who sees what. The administrators of your organisation see its members and what happens in its assistants. If your organisation is managed by a partner agency, the agency sees and manages your organisation. Our support team can access your account to solve a problem: we log when this access starts and ends, with the name of the person who used it, and some of the main actions taken this way.

4.2 Partner agencies

For agencies we process company name, VAT number, address, contact email and phone number, website, acceptance of the programme terms (with date, IP and browser) and the approvals given for purchases made on behalf of clients (with IP, browser and amounts). The contact email is also sent to Stripe for invoicing. Legal basis: performance of the contract and legitimate interest in being able to show what was agreed.

4.3 Affiliates

For affiliates we process name, email, commissions and payouts. Identity verification and bank details are collected by Stripe (Stripe Connect): we only keep the Stripe account ID, the verification status and the country.

If you sign up with an affiliate's code, we record the link together with your IP and browser. The affiliate sees your shortened name (for example "Marco R."), your masked email and the commissions earned. Legal basis: performance of the contract with the affiliate and legitimate interest in calculating commissions correctly.

5. If you visit our website

Data Why Legal basis
IP address, browser, pages requested running the website, protecting it from abuse, limiting repeated requests legitimate interest
Technical session with IP and browser, even without signing in making forms and navigation work legitimate interest
Browser language showing the site in your language (we do not store it) legitimate interest
Technical and preference cookies and browser storage see the cookie policy legitimate interest
Google Analytics measuring how the website and the dashboard are used consent
Code of the affiliate you came from (referral_code cookie) crediting your sign-up to the affiliate who referred you consent

Google Analytics only starts if you accept it: before consent the script is not even downloaded. You can change your mind from "Cookie preferences" at the bottom of every page: if you refuse, measurement stops and we delete the cookies it had set.

The AI assistant on our website. On our website you can talk to an AI assistant that presents AnyDialog. For these conversations we are the controller. We process them as described in sections 6 and 8 (text, voice if used, and any data you choose to write) to answer you and, if you ask, to contact you. Legal basis: steps you request before entering into a contract, and our legitimate interest in presenting the service.

Voice demos. If you enter your phone number on a voice demo page to receive a call from the assistant, we keep the number, IP and browser. Legal basis: your request (steps before entering into a contract).

Waiting list. While registrations are closed, you can leave us your email to find out when they open. We collect your email, the language of the site, the door you come from (customer, agency or affiliate) and, if you choose to enter them, your name, company and website. We send you an email with a link to confirm that the address is yours: you are on the list only after confirming it. When you confirm, our sales team receives a notice. We use this data only to write to you when registrations of the type you chose open, and possibly to contact you about that opening; we do not send you anything else. Legal basis: your request (steps before entering into a contract).

Some demo pages (for example the voice demo) load libraries from external public services (jsDelivr, cdn.tailwindcss.com): your browser shares your IP address with them.

6. If you talk to a customer's AI assistant

If you write to or call the AI assistant of a business that uses AnyDialog, that business is the controller. We process your data on its behalf. To learn why it collects the data, on what legal basis and how long it keeps it, read its privacy policy: when the customer has provided it, the link appears below the chat in the website widget and on the public page.

In the website widget, on the public page, on the demo page, on the phone and on WhatsApp, Telegram, Messenger, Instagram and SMS, the assistant says that it is an artificial intelligence from the first message of the conversation (Article 50 of Regulation (EU) 2024/1689, the "AI Act"). When a customer connects the assistant to its own system through our API, we give the customer the text of this statement: showing it to people is the customer's responsibility.

What we process on the customer's behalf:

  • the messages you write and the assistant's replies;
  • the data you choose to give during the conversation (for example name, email, phone number, your request);
  • appointments you book, if the customer offers them;
  • a conversation identifier. On a website it is a code generated by your browser. On WhatsApp, SMS and Telegram it contains your phone number or Telegram ID, and we also record your profile name. On Messenger and Instagram it contains the identifier Meta assigns to your profile for that page, and we also record your profile name (on Instagram also your username), which we ask Meta for; not your photo;
  • on a website, your IP and browser in the technical session (section 5), and your IP for about one minute to limit repeated requests;
  • a record of the steps used to produce each answer (for example which information the assistant looked up), which the customer uses to understand and improve the assistant;
  • the questions the assistant could not answer, which the customer sees in order to add the missing information.

Where the data goes:

  • to the artificial intelligence provider that produces the answer (section 8);
  • to the channel you are using: Meta for WhatsApp, Messenger and Instagram, Telegram, Twilio for phone and SMS;
  • to the customer's systems, if the assistant is set up to take actions (section 9);
  • by email to the colleagues the customer has chosen, when the assistant collects a contact request.

If the business also uses the same WhatsApp number on its phone. If the business connects to the assistant the number it also uses in the WhatsApp Business app, the assistant receives all new messages in that number's one-to-one chats, including those the business writes from its phone. We do not receive groups or calls. When the number is connected, Meta may send us the chat history and the phone's contact list: we do not keep the history; from the contact list we keep only a non-reversible fingerprint of each number, used to stop the assistant from replying to saved contacts if the business asks for it, and we delete it when the number is disconnected or when you ask us to delete your conversation. If the business has asked the assistant not to reply to saved contacts, we do not keep their messages (or those the business writes to them from its phone). Other messages the business writes from its phone stay in the conversation, like the assistant's.

Your rights. Contact the business you talked to: it makes the decisions. From its dashboard, the customer can search by email or phone number for what one of its assistants keeps about a person, and permanently delete a conversation: the messages, the data collected and the contact details of the related appointments are deleted; only the date and the usage remain, for costs and statistics. Appointments already created in the customer's calendar and data already sent to the customer's systems stay there and are managed by the customer. If you write to us, we tell you who to contact and, when we can identify the business, we pass your request on to it.

7. Voice and phone

  • We do not record audio. We keep the transcript of what was said, as with chat.
  • On the phone, speech is transcribed and synthesised by one of these providers, depending on how the assistant is set up: Deepgram, ElevenLabs or OpenAI. The call goes through Twilio. We use the caller's number to check whether the call is allowed and we do not store it in our records; Twilio also processes it to route the call.
  • In the website widget, dictation and read-aloud go through OpenAI. In live voice conversations, audio goes directly from your browser to OpenAI, which therefore also receives your IP address.
  • Outbound calls. A customer can have the assistant call a person. In that case we process, on the customer's behalf, the person's name and number, the reason for the call, the transcript and the data collected, and we send the outcome to the customer's system.
  • On the phone too, the assistant says that it is an artificial intelligence at the start of the conversation.

8. Artificial intelligence

8.1 What the AI provider receives

To answer, the assistant sends the AI provider:

  • the customer's instructions;
  • the parts of the knowledge base that are relevant to the question;
  • the recent conversation, including the data the person wrote (name, email, phone number, if given);
  • the outcome of any actions taken during the conversation.

The conversation also goes to the provider for supporting checks: working out which action, flow or suggested link is needed, reading a piece of data, checking a confirmation, checking that the answer is relevant. The question is also turned into a numeric vector to search the knowledge base: today OpenAI does this.

Without the conversation, the provider also receives texts written by the customer that need translating into the language of the person writing, and the sources used to suggest test questions. If the customer turns on the welcome message based on the page, the provider receives the address, the title and the visible text of the page of the customer's website that the visitor is on (never the content of forms).

Knowledge base. Documents uploaded by the customer are read by a text extraction service, split into passages and indexed in a search engine (Qdrant). To build the assistant's "memory", documents are also sent in full to the AI provider, which writes a summary of them. We advise customers not to upload personal data that the answers do not need.

8.2 Which provider

  • If the customer does not connect its own key, AnyDialog chooses the provider and the model. Today the platform's main provider is OpenAI, which we also use for knowledge base search and for voice.
  • If the customer connects its own key or its own endpoint ("bring your own endpoint"), the customer chooses the provider and the model. The providers that can be connected include Anthropic, Google (Gemini), Groq, Mistral, DeepSeek and OpenRouter, as well as any compatible service the customer specifies. For the answers, the relationship with the chosen provider is the customer's; the data still passes through our servers. Supporting checks, knowledge base search and building the memory use the platform's provider instead (today OpenAI): if the customer has chosen a different provider, these steps go to OpenAI with our key, including the documents sent in full to build the memory.

8.3 Training

We do not use conversations, collected data or knowledge bases to train artificial intelligence models. We send data to providers only to get the answer. How long a provider keeps the data and what else it may use it for (for example abuse monitoring) depends on its terms for API services: on request, we tell you the terms of each provider.

8.4 Automated decisions

Assistants answer automatically, but they do not take decisions that have legal or similarly significant effects on you (Article 22 GDPR).

At sign-up, some automatic checks against automated registrations (for example a form filled in too quickly, or too many attempts from the same IP) may reject a submission. You can try again or write to us.

9. When the assistant acts on the customer's systems

The customer can set up the assistant to send data to the customer's own systems during the conversation: a CRM (for example HubSpot, SuiteCRM, Mailchimp), an automation service (for example Zapier, Make, n8n), a Google Sheet, its own web address, or an email to its colleagues. We send this data on the customer's instructions. Once it arrives, it is in the customer's systems, and the customer is the controller.

Google Calendar. If the customer connects its Google Calendar, the assistant only reads which times are busy (not the titles or attendees of events) and creates, moves or cancels the appointments booked in the conversation. The event contains the person's name, email and phone number, and Google sends the invitation to the email address given.

Data received from Google. If the customer connects its Google Calendar, AnyDialog receives from Google APIs only what is needed to book appointments: the busy times of the chosen calendar (not the titles, descriptions or attendees of events) and the events created by the assistant, so it can move or cancel them. To offer free times in the conversation, this availability is processed by the AI provider that generates the reply, only for that reply. We do not use this data for advertising, we do not sell it, and we do not let people read it, except with the customer's consent, for security reasons or where the law requires it. Raw or derived user data received from Google Workspace APIs is not used to develop, improve or train generalized or non-personalized AI and/or ML models. AnyDialog's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Online shops. If the customer connects Shopify, WooCommerce or PrestaShop, the assistant reads the product catalogue. If the customer also turns on order lookup, the assistant can give the status of an order to a person who writes the order number and the email used for the purchase. It asks the shop for that order and answers only if the email matches, with status, dates, items, total, shipping and tracking. The buyer's name, address and phone number are not shown. The order number and the email, and what the shop returns, stay in the conversation and its technical logs, with the same retention as the conversation. Other orders and the shop's customers are not read.

10. If you ask us for support

When you open a support request from the dashboard, we process the subject, the text, attachments (up to five files, including screenshots), the severity you choose and any final rating.

Together with the request we automatically collect technical context that helps us reproduce the problem:

  • from the server: IP, browser, operating system, device type, browser languages, account language, plan and subscription status, role;
  • from the browser: screen and window size, time zone, languages, the dashboard page you are writing from.

Legal basis: performance of the contract for the reply, legitimate interest for the technical context. Emails about the request go to the person who opened it and to our support team. Your organisation's administrators see the request in the dashboard and can reply to it.

11. If you are a business we contact

To present AnyDialog, we may contact businesses. In that case we collect:

  • company data from public sources: Google Maps listings, search results, the company website (name, website, address, phone number, ratings, website content);
  • data about contact persons: name, role, work email and phone number, LinkedIn profile, from public sources or from lists we import;
  • if we email you: the sending and, through an invisible image in the email and links that record clicks, whether and when you open the email and click its links, with IP and browser;
  • if we invite you to try a demo: the contact person's name and email, the personal link to the demo, whether and when you open it and, if you then sign up, the link to your account.

We use Apify to collect this data; we may use GoHighLevel to manage contacts. With the content of the company website we may prepare a demo assistant, which goes through the AI provider (section 8).

Legal basis: our legitimate interest in making the service known to other businesses. Measuring opens and clicks tells us whether the email arrived and helps us not to insist with people who are not interested.

You can object at any time, without giving reasons: from then on we do not write to you again. The emails we use to present the service contain a one-click link to stop receiving them; you can also write to privacy@geniaris.com. After you object, your address stays on an exclusion list, precisely so that we do not write to you again.

12. Who we share data with

We only share data with those we need to provide the service. Most of these providers process data on our behalf or, for customer data, as our sub-processors. Some receive it as independent controllers instead, under their own privacy policies: Stripe for payments and for verifying affiliates, Google for signing in with Google, Meta (WhatsApp, Messenger, Instagram) and Telegram for the messages that go through their platforms.

  • Artificial intelligence: OpenAI (answers, knowledge base search, transcription, voice). Anthropic, Google (Gemini), Groq, Mistral, DeepSeek and OpenRouter: if the customer chooses them with its own key or if we set them for an assistant. Services specified by the customer ("bring your own endpoint"): only with the customer's endpoint.
  • Phone voice: Deepgram, ElevenLabs, OpenAI.
  • Messaging and phone channels: Meta (WhatsApp, Messenger, Instagram), Telegram, Twilio (phone and SMS).
  • Payments: Stripe.
  • Google: sign-in with Google, Google Calendar (only if connected by the customer), Google Analytics (only with consent).
  • Email: the email service provider we use to send emails. If we turn it on, a blind copy of the emails sent by the platform goes to an internal mailbox of ours, for support and checks: it also includes password reset emails and emails that contain data collected by assistants, and today that mailbox is not emptied automatically.
  • Sales contacts: Apify and, if we use it, GoHighLevel (section 11).
  • Infrastructure: the provider that hosts servers, databases and backups; the knowledge base search engine (Qdrant) and the text extraction service for documents (Docling).
  • Customer systems: CRMs, automations, calendars and addresses chosen by the customer (section 9).

The up-to-date list of providers, with their location, is available on request at privacy@geniaris.com.

We may also share data with public authorities when the law requires it.

13. How long we keep data

We tell you how it works today, including where there is no automatic deletion yet.

  • Account. As long as the account is active. When you delete it from your profile, we immediately delete your user, the log of actions on your profile, and your memberships of organisations and teams. The record of your sign-up and acceptances remains, with your name and email at the time, for 10 years after the relationship ends, so that we can show what was accepted.
  • What remains after you delete your account. The organisation is not deleted with a single user: its assistants, conversations, collected contacts and billing data remain. Some records that are needed to reconstruct what happened also remain: the subscription history, the log of uploaded AI keys, support requests and the link to an affiliate. They may contain your name, email or IP at the time. If you want them deleted or anonymised, write to us.
  • Organisation. To delete an organisation and its data, write to privacy@geniaris.com.
  • Billing. For the time required by tax and accounting law.
  • Conversations and data collected by customers' assistants. Today they are not deleted automatically. They stay until the customer deletes them from the dashboard or asks us to delete them. The platform provides for automatic deletion after a set period, but it is not active yet: when we turn it on, we will state the periods here. Conversations are always kept: the setting not to keep them no longer exists. Messages saved while it was turned off stay in the database and cannot be read in the dashboard history. The conversation still appears in the history, within the days the plan shows, and can be deleted like any other; the customer can read those messages only by searching for the person by email or phone number, if the conversation contains that email or number.
  • Conversations with the assistant on our website. We need them to answer you and, if you ask us to contact you, to follow up your request until it is closed. Today they are not deleted automatically: when we turn automatic deletion on we will state the period here; in the meantime you can ask for them to be deleted at privacy@geniaris.com.
  • Deleted assistant. The assistant disappears from the dashboard. The files uploaded to its knowledge base, including those of sources already removed, their search copies, its memory and the images of its widget (icon, avatar, logo) are deleted. Its conversations are emptied as when one is deleted: the messages, the data collected and the contact details of appointments go, and the date and usage remain. The keys and access codes to the customer's systems it used (actions, channels, links to the customer's data) are deleted; actions and channels go to the bin. The content of its other sources stays in the database until the customer asks for it to be deleted: texts and questions-and-answers written by hand, the content of websites read and connected catalogues.
  • Source removed from the knowledge base. The uploaded file, its search copies and the memory pages derived from it are deleted. Texts and questions-and-answers written by hand and the content of websites read stay in the database until the customer asks for them to be deleted.
  • Support requests. We need them for as long as your organisation uses the service, to trace problems already dealt with. Today they are not deleted automatically. You can delete a request from the dashboard as long as nobody from support has replied; after that, write to us and we delete it.
  • Voice demos. Number, IP and browser are needed to make the call you asked for. Today they are not deleted automatically: they stay until you ask for them to be deleted at privacy@geniaris.com.
  • Waiting list. If you do not confirm your email within 7 days, your data is deleted automatically. If you confirm it, it stays until we open registrations and write to you, and then to remember that we invited you and whether you registered; you can ask for it to be deleted at any time at privacy@geniaris.com.
  • Sales contacts. Until you object. After you object, we do not write to you again and your address stays on the exclusion list. The other data collected (company and contact person details, email events, demo invitations, any demo assistant) is not deleted automatically today: to have it deleted, write to privacy@geniaris.com.
  • Website technical session. Deleted after it expires, after about two hours of inactivity.
  • Server technical logs. They are needed for security and troubleshooting. Today their duration is not set by an automatic rule: when it is, we will state it here.
  • Failed operations. If a queued operation fails (for example sending an email), its data stays in a technical log so that it can be retried or the error understood. It may include data written by a visitor. Today this log is not emptied automatically.
  • Cookies. Durations are in the cookie policy.

14. Transfers outside the European Union

Some providers are based outside the European Union, mainly in the United States (for example OpenAI, Anthropic, Twilio, Deepgram), and also process data there. DeepSeek is based in China, a country without an adequacy decision from the European Commission; OpenRouter routes requests to models from other providers, including outside the Union. When the customer chooses them with its own key, the data leaves our servers on the customer's instructions and the customer, as controller, must first check that the transfer is allowed and with which safeguard; for an assistant we set up, the safeguard applied is stated on request.

The GDPR only allows these transfers with appropriate safeguards: an adequacy decision of the European Commission (for the United States, the EU-US Data Privacy Framework, for companies that have joined it) or the standard contractual clauses approved by the Commission. On request at privacy@geniaris.com, we tell you the location of each provider and the safeguard that applies.

15. How we protect data

  • Connections to the service are encrypted (HTTPS).
  • Passwords are stored only in non-reversible form.
  • AI provider keys, channel and integration credentials and appointment contacts are encrypted in the database with AES-256.
  • Each organisation's data is kept separate: one organisation cannot see another's.
  • In technical logs we mask email addresses, phone numbers written in international format (with the + prefix) and the identifiers of conversations on WhatsApp, SMS, Telegram, Messenger and Instagram. Other numbers and IP addresses, however, may appear there.
  • Access to the dashboard requires an account, and roles limit what each member can do.

Encryption of individual conversation messages in the database is not active for every assistant: where it is not, conversations are protected by access control and by the separation between organisations.

If there is a data breach, we inform customers as set out in the Terms of Service and, where the law requires it, the supervisory authority and the people affected.

16. Cookies

We use technical and preference cookies and, only with your consent, Google Analytics and the cookie that credits your sign-up to the affiliate you came from. Names, purposes and durations are in the cookie policy. You can change your choice at any time from "Cookie preferences" at the bottom of every page.

17. Your rights

You can ask us:

  • to access your data and receive a copy;
  • to correct it;
  • to delete it;
  • to restrict its processing;
  • to receive it in a machine-readable format (portability);
  • to object to processing based on our legitimate interest, on grounds relating to your situation: we stop, unless there are compelling legitimate grounds, which we explain to you;
  • to object at any time to sales contacts, without giving reasons: we always stop;
  • to withdraw consent (for example to Google Analytics), without affecting what happened before.

On your own, in the dashboard, you can correct your profile and your organisation's details and delete your account (Profile → Danger zone). You cannot delete your account if you are the last administrator of an organisation with an active subscription: first appoint another administrator or end the subscription. It may also not be possible when data that must be kept is linked to your account, for example an affiliate's commissions or administrative records: in that case the dashboard tells you and shows you who to write to. Cookie choices can be changed from "Cookie preferences"; sales emails stop from the link in the emails or by writing to us.

For everything else, write to privacy@geniaris.com or by certified email to geniaris@legalmail.it. We reply within one month; if the request is complex we may extend this by two more months, and we will tell you within the first month. If you write from your account's email address we recognise you from it; otherwise we may ask you for some information to check that the request comes from you.

If you talked to a customer's AI assistant, you exercise your rights with that customer (section 6).

You also have the right to lodge a complaint with the Italian data protection authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it), or with the supervisory authority of the country where you live or work.

18. Children

AnyDialog is a service for businesses and professionals: accounts are not intended for children.

Our customers' assistants can be reached by anyone, and the platform does not check the age of the person writing. It is up to the customer to assess whether its assistant may be used by children and to inform them appropriately.

19. Changes to this policy

We may update this policy when the service or the law changes. The version and date are always shown at the top. Every time someone signs up, we record which version they were shown. When changes are substantial, we let customers know.