We are launching the platform on November 23rd. Get a special discount by signing up for the waiting list.Sign up

Privacy policy

How the company handles personal data on this website and in the MosenAI platform: what we collect, why, who receives it, how long we keep it and how to use your rights.

Last updated: 11 November 2026

1. Who we are

This website and the MosenAI platform are operated by Leanicon S.L. (tax ID B05879507), María de Molina, 39, 4ª planta, 28006 Madrid, Spain ("Leanicon", "MosenAI", "we"). For anything about personal data, write to [email protected].

2. Our two roles

We process personal data in two different roles:

  • As controller, we decide why and how data is used. This covers visitors to this website, people who contact us, newsletter subscribers, partner applicants, and the people who administer or use a MosenAI workspace (their accounts, billing and use of the platform). Sections 3 to 7 and 9 to 13 describe it.
  • As processor, we handle the content that a customer company puts into MosenAI or that MosenAI generates for it: documents, conversations with its contacts, call and session transcripts, summaries, files and data from its integrations ("Customer Content"). The customer company is the controller, and we process that content only on its documented instructions, under section 4.4 of our Terms of service, which is the data processing agreement required by Article 28 of the GDPR. Section 8 describes it.

If you have talked to a customer company's agent, that company decides what your data is used for, and you should contact it to use your rights. If you do not know whom to contact, write to us and we will help route your request. We do not decide on the customer's behalf.

3. What we collect as controller

  • Enquiries and demo requests. Name, work email, company or practice, kind of business, your message and, if you book a meeting, the booking details. You give them through the contact form, or through a form and meeting calendar embedded from our CRM provider.
  • Launch waiting list and partner applications. The same data and, for partners, which clients you would deploy for. Please do not send us your clients' personal data.
  • Newsletter and guides. Email address, first name if you give it, language, the page you signed up on, the guide you asked for, the campaign link you came from and any answer the form asks for, such as kind of firm. We first send you a confirmation email, and we keep a record of what you agreed to, the text you saw and when.
  • Cookies and similar technologies. Only if you accept analytics or marketing cookies: identifiers and browsing data such as pages viewed, how you arrived, device and browser, and an approximate location derived from your IP address. The choice itself is recorded with a random identifier, the choice, the banner version, the language and the page, without your IP address or browser details. See the Cookie policy.
  • Technical records of your visit. Our hosting and network providers record each request (IP address, browser, time, page) to deliver the site and protect it from abuse.
  • Workspace accounts. For people who use MosenAI at a customer company: name, work email, role, company, phone if provided, language, time zone, country, sign-in identifiers, and a record of which legal documents were accepted, which version, when and by whom.
  • Billing. Billing contact, legal name, address, tax or VAT number, plan, invoices and payment-provider references. Card details go to the payment provider and do not reach our systems.
  • Usage and technical data of the platform. Security and operating logs, error reports, performance metrics, sign-in security checks by our identity provider (which can include IP address and device information) and usage figures: which features are used, when, for how long and with what result. Usage figures do not contain the content of messages, answers, transcripts or files, and we do not use third-party analytics tools for them.
  • Safety signals. Counts per customer and category of the messages and answers flagged by the platform's automatic checks, processed without their content.
  • Communications with us. Emails and support requests.

We receive this data from you or, for workspace accounts, from the customer company that invited you. Giving us your data on a form is voluntary, but without a name and email we cannot reply. Account and billing data are needed to provide the platform.

4. Why we use it, and on what basis

  • Replying to an enquiry, arranging a demo and assessing a partner application rest on steps taken at your request before a contract (Article 6(1)(b) GDPR).
  • Providing and supporting the platform rests on the contract (Article 6(1)(b)). Security, preventing fraud and abuse, and detecting prohibited uses rest on our legitimate interest (Article 6(1)(f)).
  • Measuring use of the platform to operate and improve it (usage figures without content) rests on our legitimate interest.
  • Invoicing and meeting accounting and tax obligations rest on a legal obligation (Article 6(1)(c)).
  • Keeping proof of which version of our legal documents each customer accepted rests on our legitimate interest and on a legal obligation.
  • Newsletter and guides rest on your consent (Article 6(1)(a)). You can withdraw it at any time with the unsubscribe link or by writing to us.
  • Messages about our products to customers and business contacts rest on our legitimate interest where Spanish law on electronic commerce allows it, and on your consent otherwise. You can object at any time.
  • Analytics and marketing cookies, and the follow-up our sales team does with that data, rest on your consent (Article 6(1)(a) GDPR and Article 22(2) of Spanish Law 34/2002). Strictly necessary cookies need no consent.
  • Customer Content is processed on the customer's instructions. The customer is responsible for the legal basis.

Where we rely on legitimate interest we have weighed it against your rights, and you may object (section 11). We do not take decisions based solely on automated processing that produce legal or similarly significant effects on anyone.

5. Who receives it

We do not sell personal data. We share it with:

  • Providers that process data for us (processors): cloud hosting and storage in the EU; content delivery and security; CRM, forms and meeting scheduling; email delivery and newsletter; payments; artificial intelligence models, speech and document-text services; telephony and messaging (only when a customer uses those channels); error and performance monitoring; and, only with your consent, analytics, tag management and sales-intelligence tools. They act on our instructions under contracts with confidentiality and data protection obligations.
  • Services a customer connects with its own accounts (storage, CRM, accounting, calendars or others): data flows as the customer decides.
  • Authorities, where the law requires it, and advisers or acquirers in a corporate transaction, under confidentiality.

Customers can ask us at [email protected] for the current list of sub-processors that handle Customer Content. We tell customers' administrators about changes at least 30 days beforehand (Terms of service, section 9).

6. International transfers

  • This website is hosted in the European Union. Some of the providers in section 5, such as analytics, CRM, newsletter or sales-intelligence tools, are or have affiliates outside the European Economic Area. When personal data leaves the EEA we rely on an adequacy decision (for example the EU–US Data Privacy Framework, for recipients that adhere to it) or on the standard contractual clauses approved by the European Commission. You can ask for a copy of the safeguards at [email protected].
  • The platform hosts and processes Customer Content in EU regions, including the artificial intelligence models, speech recognition and document-text services it uses. We do not currently process Customer Content outside the European Economic Area. If that changes, we will update this page and tell customers' administrators at least 30 days before. If a customer connects a service or channel that runs outside the EEA, the data needed for that feature goes there at the customer's instruction.

7. How long we keep it

Data we keep as controller

  • Enquiries, demo requests, partner applications and CRM records: 24 months after our last contact with you, then deleted or anonymised, unless you become a customer.
  • Newsletter: until you unsubscribe. We then keep only the record of your consent and of your unsubscription for three years, to defend claims.
  • Cookie-choice records: three years.
  • Technical records of site visits: only as long as needed to operate and protect the site.
  • Workspace accounts: while the workspace is active and, after it closes, up to twelve months.
  • Billing records: as long as tax and commercial law require, currently six years.
  • Records of accepted legal documents: for the life of the workspace and six years more.
  • Usage figures: the detail for ninety days; per-person daily figures for twenty-five months.
  • Operating logs: up to ninety days. Database backups: fourteen days.

Customer Content (where we are the processor). It is kept for as long as the customer keeps it: the customer's administrators can delete conversations, documents and knowledge sources at any time, and a deleted knowledge source is removed together with its stored files. When the contract ends the customer has 30 days to recover its data, after which we delete Customer Content and the workspace's data; backups drop out within fourteen days. Some deletions also happen automatically today: chat attachments when the conversation ends, finished automation run records and their action ledgers after ninety days (a platform setting), call metadata after ninety days, and data-export archives after seven days. We keep what the law requires us to keep.

8. Customer Content (where we are the processor)

We process it only on the customer's documented instructions. Specifically:

  • Location. It is hosted and processed in EU regions (section 6).
  • Separation. Each customer has its own database schema and its own partition of the search index, so one customer's records and searches are separate from another's.
  • Keys. A customer-specific encryption key is created for each customer when its workspace is set up, and the customer's credentials and session transcripts are encrypted under it. Connections to the platform are encrypted in transit.
  • Artificial intelligence. We configure the model providers so that Customer Content is not used to train their models, and we do not use it to train ours.
  • Record. Every interaction, tool call and escalation is logged, and the customer can export the record. Every uploaded file is scanned for malware before it is accepted.
  • Export. A customer's administrators can export all of the workspace's data.
  • Requests from individuals. They go to the customer, which is the controller. We help it respond.
  • Special categories of data. We do not ask for them. The customer decides whether to enter any and needs a lawful basis to do so. MosenAI is not offered for decisions about recruitment, creditworthiness, life or health insurance, triage or the evaluation of students.
  • Recording. A customer that records a session is responsible for the lawful basis and for consent. The platform stores the recorder's consent attestation with the transcript.
  • Staff access. Our team does not read Customer Content in normal operation. Support access goes through a signed session that expires after two hours and is logged with the operator's identity, start and end. It is used only when a customer asks for support, to investigate abuse or a security incident, or when the law requires it.
  • Breaches. We tell the customer of a personal data breach affecting its content without undue delay and in any case within seventy-two hours of becoming aware of it (Terms of service, section 4.4).

9. Security

We apply technical and organisational measures appropriate to the risk, described on our Trust page. They include separation between customers; customer-specific keys for credentials and session transcripts; roles with a configurable permission matrix; optional two-factor authentication; short-lived signed links; malware scanning of uploads; a record of every action; and hosting in EU regions. No system is perfectly secure. If a personal data breach occurs, we will notify it as the law and the data processing terms require.

10. Cookies and similar technologies

We use strictly necessary cookies without asking. Analytics and marketing cookies are used only if you accept them in the cookie banner, and you can change your choice at any time with Cookie settings. The full list, with the purpose and duration of each cookie, is in the Cookie policy.

11. Your rights

You have the right to access your data, to have it rectified or erased, to restrict or object to its processing, to receive it in a portable format and to withdraw your consent at any time, without affecting what was done before. You also have the right not to be subject to decisions based solely on automated processing that significantly affect you; we take none.

To use them for data we hold as controller, write to [email protected]. We may ask you to confirm your identity. We reply within one month; if your request is complex we may extend that by up to two more months, and we will tell you why. It is free unless it is manifestly unfounded or excessive. For data we process as processor, contact the customer company that controls it, and we will help it respond.

You may also complain to the Spanish Data Protection Agency (Agencia Española de Protección de Datos, www.aepd.es (opens in new tab)).

12. Children

MosenAI is for businesses and is not directed at children. We do not knowingly collect children's data as controller. If a customer's contacts may include minors, the customer is responsible for the lawful basis and, where Spanish law requires it (under 14 years of age), for the consent of their parents or guardians.

13. Changes to this policy

We update this page when our practices change and show the date at the top. We tell workspace administrators at least 30 days before significant changes take effect.

14. Google user data

MosenAI lets a customer connect its Google account so that its agents and automations can work with Google Calendar and Google Drive. This section describes how we handle the information we receive from Google when a customer does so.

What we access

We access only what the person who connects grants on Google's consent screen:

  • Google Calendar: the person's calendars and events, to show availability and to read, create and change events for the booking features the customer configured (scopes calendar.readonly and calendar.events).
  • Google Drive: only the files and folders the person picks in Google's file picker, and the files the service itself creates, to read them and to save files the customer's automations produce (scope drive.file). We do not request access to the rest of a Drive.
  • Basic profile: the email address of the connected Google account, to show which account is connected.

A customer that connects its own Google credentials decides which scopes it grants. The data is then Customer Content and section 8 applies.

How we use it

We use this information only to provide and improve the user-facing features the customer configured and the person approved. We do not use it for any other purpose.

What we never do

We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models. We do not use it for advertising, including retargeting or interest-based advertising, and we do not sell it. We do not transfer it to others except (a) to the processors, including artificial intelligence model providers, that we need to deliver the feature the customer configured, under contracts that do not allow them to use it for their own purposes; (b) to comply with the law; or (c) as part of a merger, acquisition or sale of assets, with notice to affected users.

Who can see it

Our staff do not read Google user data unless the customer asks us to for support, it is needed to investigate abuse or a security incident, the law requires it, or it is aggregated and anonymised. Any such access goes through the signed, time-limited and logged support session described in section 8.

Compliance with Google's policy

MosenAI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (opens in new tab), including the Limited Use requirements.

Storage and protection

The access credentials we receive from Google are stored encrypted in our EU-hosted database and are used only to carry out the connected features. Google data is fetched from Google when a feature runs. We do not keep a copy of calendar data, except what appears in the conversations and records that the customer's agents produce and the files an automation saves to the customer's workspace. That workspace is hosted in the European Union and protected as described in section 9.

Retention and deletion

When a customer or user disconnects Google, we delete the credentials we hold and stop accessing their Google data. Content that an automation already saved in the customer's workspace stays there until the customer deletes it (section 7). To have data deleted, write to [email protected].

Withdrawing access

You can disconnect Google in MosenAI at any time. You can also review and remove MosenAI's access at myaccount.google.com/permissions (opens in new tab). Removing access there ends it for every workspace that used that Google account to connect to MosenAI. Disconnecting in MosenAI deletes our stored credentials; it does not revoke the grant at Google, so use the Google page if you want Google to record the removal.