Skip to content
Ilmarinen
  • Home
  • Services
  • Contact
  • ESEspañol
  • ENEnglish

Privacy Policy

Effective date: 2026-11-17

This policy explains what personal data ILMARINEN, LLC (“Ilmarinen”, “we”, “us”) processes, why we use it, who we share it with and how you can exercise your rights. It applies to our website ilmarinen.io and its subdomains (including the page where businesses connect their accounts to our Meta app, which is also called Ilmarinen), to our communications with prospects and clients, and to the services we provide to businesses: integrations with the WhatsApp Business Platform (Meta’s official API), AI agents, workflow automation and CRM integrations.

This document is our privacy notice under Mexican law and our privacy policy under the EU General Data Protection Regulation (GDPR).

On this page

  1. 1.Who controls your data
  2. 2.Our two roles: controller and processor
  3. 3.What data we process
  4. 4.Why we use data
  5. 5.Legal bases
  6. 6.What we never do
  7. 7.WhatsApp Business Platform and Meta
  8. 8.Who we share data with
  9. 9.International transfers
  10. 10.How long we keep data
  11. 11.How we protect data
  12. 12.Your rights
  13. 13.How to request deletion of your data
  14. 14.Data protection contact
  15. 15.Children
  16. 16.Changes to this policy

1. Who controls your data

ILMARINEN, LLC, a limited liability company (LLC) organized in the State of Florida, United States, and registered with the Florida Department of State, Division of Corporations (Sunbiz) under document number L26000517339.

  • Address: 7345 W SAND LAKE RD STE 210 OFFICE 2070, ORLANDO, FL 32819
  • Email: contacto@ilmarinen.io
  • Phone: +1 904 341 2547

2. Our two roles: controller and processor

Depending on where the data comes from, we act in one of two ways:

  • As a controller. We decide how and why we use the data we receive directly: from people who visit our website or contact us, and from people who represent our clients and prospects.
  • As a processor. When we provide services to a business (our “client”), we process the data of its own customers and contacts on its behalf; for example, the WhatsApp conversations the business sends and receives. In that case the business is the controller: it decides how that data is used, and we process it only to provide the service and on its documented instructions.

If you chatted on WhatsApp with a business that uses our services, that business is the controller of your data, so we recommend reading its privacy notice too. You can still contact us and we will help (sections 12 and 13).

3. What data we process

3.1 As a controller

  • Business contact data: name, job title, company, email, phone number, country and whatever you tell us when you write to us, call us or meet with us.
  • Video call data: if we meet by video call, your image and voice during the call (we don’t record it), and what the video call tool logs about your connection, such as the name you join with, when you join and leave, your IP address and your device details (section 8).
  • Contract and billing data for your company: legal name, tax details, billing address, and payment and invoice history.
  • Account connection data. When a client connects its accounts to our app through Facebook Login for Business, we receive:
    • only the name and app-scoped ID of the person who makes the connection; we don’t access their posts, friends or any other Facebook profile data;
    • the identifiers of the business’s Meta accounts (business portfolio, WhatsApp account, messaging account and phone number) and whether the number uses coexistence with the WhatsApp Business app;
    • the status of the connection process, so we can fix problems;
    • the access token Meta issues so we can operate those accounts on the business’s behalf, which we store encrypted.
  • Website technical data: IP address, browser and device type, pages visited, and date and time of access, logged by our hosting and network providers for security and to keep the site running. Our website doesn’t use advertising cookies or third-party tracking tools; our providers may use strictly necessary technical cookies to protect the site. The account connection page also loads the Facebook SDK for JavaScript, which Facebook Login for Business needs. When it loads, Meta receives technical data from your browser (such as your IP address) and may use its own cookies, under its own privacy policy.

3.2 As a processor, on behalf of our clients

When we operate a client business’s WhatsApp and its integrations, we process on that business’s behalf:

  • WhatsApp data of the people who chat with the business: phone number; the business-scoped user ID that Meta assigns; the WhatsApp username, if the person has one (in that case, we may not receive their phone number); profile name; message content (text and files exchanged in the conversation); metadata (date, time, type and ID of each message and, if the conversation starts from an ad, the ad data Meta sends); and delivery statuses (sent, delivered, read or failed).
  • If the business uses coexistence (it keeps using the WhatsApp Business app on its phone): also the messages the business sends from the app and, only if it agrees to share them when connecting, its app contacts and a one-time copy of its one-to-one chats from up to the last 180 days.
  • Data from its CRM and other connected tools: the contact and follow-up data the business records (for example, name, phone, email, notes and service history) when we connect WhatsApp to its CRM or database.
  • Content processed with AI: so that the business’s AI agent can understand a question, answer it and know when to hand the conversation to a person, we send our AI providers the conversation text needed for that; if someone sends a voice message, its audio, to turn it into text; and, if the agent is set up to analyze them, the images and documents shared in the conversation (section 8).

As a controller, we don’t collect sensitive data. If a business’s service involves sensitive data (for example, health data at a clinic) or someone shares it in a conversation, we process it only on that business’s behalf and on its instructions; the business must have the legal basis and the express consent the law requires.

4. Why we use data

4.1 As a controller

  • To answer your questions and prepare proposals.
  • To follow up on your inquiry or on the proposal you requested, for twelve months after our last contact with you (section 10). If you don’t want us to, tell us and we’ll stop.
  • To enter into and perform contracts with our clients: onboarding, setup, support, billing and collections.
  • To connect and manage our clients’ Meta accounts and control who has access to them.
  • To protect our website and systems and prevent fraud and abuse.
  • To comply with legal, tax and accounting obligations, respond to your rights requests and keep a record of how we handled them, and respond to valid requests from authorities.
  • To defend our rights in case of claims.

We receive account connection data (section 3.1) from Meta: we only use it to connect and manage the client’s accounts, keep the service secure and comply with a legal obligation.

4.2 As a processor

Only to provide the services each client hired, and on its instructions:

  • Send and receive WhatsApp messages on the business’s behalf. Outside the 24-hour customer service window, which starts each time a person messages the business, we send only message templates approved by Meta; within it, we reply to that person.
  • Manage the business’s WhatsApp accounts on its behalf: phone numbers, message templates and settings.
  • Run the business’s AI agent, which answers with that business’s information and rules and hands the conversation to someone on its team when needed.
  • Automate its workflows (n8n) and sync data with its CRM.
  • Provide support and maintenance, troubleshoot and keep the service secure.

5. Legal bases

European Union and Spain (GDPR, Article 6)

PurposeLegal basis
Answering questions, preparing proposals and following up on themSteps taken at your request before entering into a contract (Art. 6(1)(b)) or our legitimate interest in responding to business inquiries and following up on them (Art. 6(1)(f))
Entering into and performing the contractPerformance of a contract (Art. 6(1)(b)), if the contract is with you as a professional. If it is with the company you work for, our legitimate interest in entering into and performing that contract (Art. 6(1)(f); in Spain, Art. 19 LOPDGDD)
Connecting and managing client accounts and controlling accessPerformance of a contract (Art. 6(1)(b)), if you are the client. If the client is your company, our legitimate interest in providing the service it hired. In both cases, also our legitimate interest in security (Art. 6(1)(f))
Protecting the website and systemsLegitimate interest in security (Art. 6(1)(f))
Complying with legal, tax and accounting obligationsLegal obligation (Art. 6(1)(c)), where EU or Member State law imposes it. Where another law that applies to us imposes it, such as U.S. tax law, our legitimate interest in complying with it (Art. 6(1)(f))
Responding to your rights requests and keeping a record of how we handled themLegal obligation (Art. 6(1)(c), read with Arts. 5(2) and 12 to 22 GDPR) and our legitimate interest in being able to show we handled them (Art. 6(1)(f))
Responding to valid requests from authoritiesLegal obligation (Art. 6(1)(c)), where EU or Member State law imposes it. Where another law imposes it, our legitimate interest in complying with it, only as strictly necessary (Art. 6(1)(f)). In an emergency, protecting someone’s life or physical safety (Art. 6(1)(d))
Defending against claimsLegitimate interest (Art. 6(1)(f))

If we ever ask for your consent (Art. 6(1)(a)), you can withdraw it at any time; this won’t affect earlier processing. Where we rely on legitimate interest, you can object (section 12). Giving us your data is voluntary, but without it we can’t answer you or provide the service.

When we act as a processor, the legal basis is determined by the client business, which is the controller.

Mexico (LFPDPPP)

Under Mexico’s Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP):

  • We don’t need your consent to enter into and perform our contract with you, bill and collect, comply with legal, tax and accounting obligations, respond to requests from authorities and defend our rights under the contract (Article 9, items I, IV and VII). That is also why we don’t ask for your express consent for your payment history.
  • We do need your consent to answer your questions, prepare proposals and follow up on them while you are not yet a client, to protect the website when you only visit it, and to process the data of the person who connects the accounts or represents a client company. It is tacit: you give it if you don’t object after we make this notice available to you. You can refuse or revoke it at any time (section 12). If you do, we may not be able to help you; if you only refuse the follow-up, we stop it and keep helping you.

As a controller, we don’t process your data for advertising or marketing.

6. What we never do

  • We don’t sell, rent or trade personal data.
  • We don’t use data for our own advertising or to target or personalize ads. As a processor, we only send the promotional messages that a client business chooses to send to its own contacts who agreed to receive them (section 4.2). Nor do we use WhatsApp data to track people or to build or enrich profiles of them. If a client business asks us to record its conversations in its CRM or to tag its contacts, we do it only on its behalf, on its instructions and based on the content of those conversations.
  • We don’t use data obtained through WhatsApp, not even in anonymized, aggregated or derived form, to create, train or improve AI models, and we only hire providers whose terms prohibit them from using it for that.
  • We don’t use one client’s data to serve another client.

7. WhatsApp Business Platform and Meta

Our WhatsApp services run on the WhatsApp Business Platform, provided by Meta. Each client business accepts Meta’s terms and policies directly with Meta and pays Meta directly for WhatsApp usage. Meta processes WhatsApp data under those terms and policies: generally as a processor for the business and, for purposes such as the safety and integrity of its platform, as a controller. We also handle that data in line with those terms and policies:

  • WhatsApp Business Messaging Policy
  • Meta Terms for WhatsApp Business Platform

We use data obtained through Meta’s platforms only to provide the service to the client business, in accordance with those documents and the Meta Platform Terms. We only share that data with the client business, with the providers in section 8 that need it to provide the service, with the business’s own tools when it instructs us in writing, and when a law or a valid order requires us to disclose it.

8. Who we share data with

We use these providers to run our website and services. Each one receives only the data it needs for its function. Meta is not our provider: each client business contracts it directly (section 7); we list it because messages go through its platform.

ProviderWhat we use it forData it processesWhere
Meta (Meta Platforms, Inc. and its affiliates)WhatsApp Business Platform: sending and receiving messages. The client business contracts it directly with MetaWhatsApp data and the business’s account dataUnited States and other countries where Meta has infrastructure
Hostinger International Ltd.Virtual private server (VPS) that runs our automations (n8n) and our databasesData that flows through the automations and client data, including messages, account identifiers and encrypted tokensUnited States (server in Boston) and other countries from which Hostinger or its sub-processors provide support or store backups
Vercel Inc.Hosting for this website and for the account connection pageTechnical browsing dataUnited States (primary processing) and other countries where Vercel or its sub-processors operate; content delivered through its global network
Anthropic, PBCAI processing of messagesConversation text needed to respond, and images and documents, if the agent analyzes themUnited States, Australia and countries in Europe and Asia to which Anthropic routes inference and, for safety review, support or incident response, other countries where Anthropic or its affiliates operate
OpenAI OpCo, LLCAI processing of messages, including speech-to-text transcription of voice messagesVoice message audio, conversation text needed to respond, and images and documents, if the agent analyzes themUnited States and other countries where OpenAI or its sub-processors process data
Groq LLCAI processing of messages, including speech-to-text transcription of voice messagesVoice message audio, conversation text needed to respond, and images and documents, if the agent analyzes themUnited States, Canada, Finland, United Kingdom, Australia and Saudi Arabia (countries where Groq has data centers) and other countries where its sub-processors operate
Google (Google LLC and its affiliates)Email (Google Workspace)Emails we exchange with you and their attachmentsUnited States and other countries where Google has data centers or support teams
Zoom Communications, Inc.Video calls with prospects and clientsName, image, voice and chat messages of meeting participants, and technical data about their connectionUnited States and other countries where Zoom, its affiliates or its sub-processors process data

When a client business instructs us in writing, we send the data it chooses, from the data we process on its behalf, to its own tools, such as its CRM or database. The business hires, pays for and controls those tools itself and remains the controller of that data: they are not our providers and, since each business chooses its own, they are not listed in the table.

We may also share contact, contract and billing data with professional advisers (for example, accountants or lawyers) bound by confidentiality, when they need it to advise us. We don’t share with them the data we receive from Meta or the data we process on behalf of our clients. For our own operations, we also use messaging, accounting and banking providers, which process the contact, contract and billing data they need for their function.

Requests from authorities

We only disclose personal data to an authority when a law or a valid order requires it, or in an emergency involving an imminent risk of death or serious physical injury, to prevent that harm. The emergency exception never covers data we received from Meta or data we process on behalf of a client: we pass those cases on to the client right away. When we receive a request, we:

  • review whether it is lawful and, if we believe it isn’t, ask the authority to withdraw or narrow it and use the legal remedies reasonably available to us;
  • disclose only the minimum data necessary;
  • document each request, our response, the legal reasoning behind it and who was involved; and
  • notify the affected client if the request concerns its data, unless a law or an order prohibits it.

9. International transfers

ILMARINEN, LLC is a U.S. company, our team accesses our systems remotely from Mexico and Argentina, and several of our providers process data in the United States or other countries. As a result, your data may be processed outside your country.

  • From the European Union: the United States has a European Commission adequacy decision (Article 45 GDPR) only for companies certified under the EU-U.S. Data Privacy Framework. When we send data to a U.S. provider that isn’t certified, or to another country in section 8 without an adequacy decision, we use the standard contractual clauses approved by the European Commission (Article 46(2)(c) GDPR), included in its data processing agreement. When a business in the European Economic Area, or one subject to the GDPR, entrusts us with data, we sign those clauses with it (module two, controller to processor). You can ask us for a copy of these safeguards at contacto@ilmarinen.io and read the standard clauses on EUR-Lex.
  • In Mexico: sharing data with our providers, which act as processors, doesn’t require your consent, and neither does sending the data we process on behalf of a client business to its own tools when it instructs us to (section 8): that business, as the controller of the data, decides it. Other than that, we don’t transfer your data to third parties, except where the law allows it without your consent, such as responding to a request from a competent authority.

10. How long we keep data

DataRetention
Data we process on behalf of a clientFor as long as the service lasts, until the client asks us to delete it or, unless the client must keep it, until the person it relates to asks us to delete it (section 13). If the client asks, we return it within 30 calendar days after the service ends and before deleting it. We delete it from our live systems within 30 calendar days after the service ends or after we receive the deletion request, and from backups when they expire, no later than 90 days after we delete it from our live systems
Account connection data (name and ID of the person who connected, account identifiers and tokens)For as long as the service lasts. If the client removes our app from its business portfolio, the token stops working; to have the rest of the connection data deleted, the client must email us (see Data Deletion). When the service ends, we delete it within the timelines in the row above
Prospect contact dataTwelve months from our last contact with you (the last time you wrote to us, spoke with us or met with us)
Contact data of the people who represent our clientsFor as long as the relationship with the client lasts and, once it ends, twelve months from our last contact with you. Anything recorded in contracts or invoices is kept with them (next row). The account connection data we receive from Meta, including the name of the person who connected the accounts, is deleted within the timelines in its own row
Client data (contract and billing)For the duration of the relationship and, afterwards, seven years from the end of the tax year each document relates to (for the contract, from the end of the year in which the relationship ends). For example, a 2026 invoice is kept until December 31, 2033. We keep it longer only if a law requires it or while an audit, claim or proceeding is open. Data about a breach of contract (for example, an overdue payment) is deleted 72 months after the date of the breach, unless a law requires us to keep it longer or a claim is still open
Record of requests from authoritiesFive years after the request is closed, unless a law requires a different period
Record of deletion requests (reference number, dates, channel, client business, and what we deleted and when; never message content)Five years after we close the request, unless a law requires a different period. We use it only to show that we handled the request. While backups that may contain the data exist (90 days at most), we also keep the phone number or WhatsApp ID, only to delete the data again if we restore a backup; after that, we remove it from the record
Record of other rights requests (dates, channel, right exercised and how we handled them; never message content)Five years after we close the request, unless a law requires a different period. We use it only to show that we handled the request
Technical logsUp to 90 days, depending on the system
Video call dataYour image and voice, only during the call (we don’t record it). Zoom keeps what it logs about your connection (the name you join with, when you join and leave, your IP address and your device details) for up to 15 months after the video call, unless the law requires it to keep that data longer or it needs it for the security of its platform
Data our AI providers keep after processing it (among other purposes, to detect abuse)Up to 30 days. If Anthropic flags content as violating its policies, it may keep it for up to 2 years. None of them uses it to train models
Execution history of our automations (may include messages)Deleted automatically from our live systems within 30 days

The periods in this table apply to our live systems, except the ones for Zoom and our AI providers, which apply to their own systems. If data is also in one of our backups, it is deleted when that backup expires, no later than 90 days after we delete it from our live systems. Until then we don’t use it and, if we restore a backup, before using it we delete again anything that should already have been deleted. Email is different: when we delete an email, Google, our email provider, may take up to 205 days to delete it from its own systems, including its backups, unless the law requires it to keep the email longer. Google also keeps a log of each email (sender, recipient and subject) for up to 6 months, and we can’t delete that log. None of this affects the data we receive from Meta, such as WhatsApp conversation data, identifiers and tokens, because it doesn’t go through our email.

11. How we protect data

  • Encryption in transit: the connections with the WhatsApp Business Platform, our website and our providers’ APIs, through which we receive and send data, use HTTPS (TLS).
  • Encrypted access tokens: we keep them as n8n credentials, which n8n stores encrypted.
  • Restricted access: on our side, only the members of ILMARINEN, LLC can access our automations (n8n), our client database and the Meta accounts we manage.

To report a security vulnerability, email contacto@ilmarinen.io with the subject “Security”.

No system is infallible. If a security incident affects data we process on behalf of a client, we will notify that client without undue delay, with the information we have, so that, as the controller, it can notify the authorities and affected individuals where the law requires. If it affects data we control, we will notify the authorities and affected individuals ourselves where the law requires.

12. Your rights

Depending on the law that applies to you, you can:

  • Access your data and learn how we process it.
  • Rectify it if it is inaccurate or incomplete.
  • Delete it (erasure or cancellation).
  • Object to its processing, including processing based on our legitimate interest.
  • Request portability: receive it in a structured, commonly used format.
  • Restrict its processing in certain cases.
  • Withdraw or revoke your consent, where processing is based on it.

Right to object. You can object at any time, on grounds relating to your particular situation, to our processing of your data based on our legitimate interest. If you object, we will stop, unless we have compelling legitimate grounds that override your interests or need the data to establish, exercise or defend legal claims.

In Mexico, these are your ARCO rights (access, rectification, cancellation and objection); you can also revoke your consent and ask us to limit the use or disclosure of your data.

As a controller, we don’t make decisions based solely on automated processing that produce legal effects for you or similarly significantly affect you. When we run an AI agent on a business’s behalf, that business decides what is automated and is responsible for complying with the rules on automated decisions; the agent answers questions and, when needed, hands the conversation to a person.

How to exercise them. Email us at contacto@ilmarinen.io with the subject “Privacy rights” and include:

  • your name and a way to reply to you;
  • if Mexican law applies to you, a document that proves your identity or, if you act on behalf of someone else, your authority to represent them; in other cases, we will only ask for it if we have reasonable doubts about who you are;
  • the right you want to exercise and the data it concerns;
  • any detail that helps us find the data (for example, the phone number or the business you chatted with).

You can also ask us through another channel, for example by phone or by letter to our address. We won’t refuse your request for that reason, although we may ask you for the details listed above to handle it.

If you ask for a correction, tell us the change and, where applicable, attach supporting documents.

Timelines. We will respond without undue delay: within one month if the GDPR applies, or within 20 business days if Mexican law applies; in Mexico, if your request is granted, we will carry it out within 15 business days of our response. If the law allows us to extend a deadline, we will tell you. For deletion requests, the timelines in section 13 also apply; if the GDPR applies to you, we never take longer than one month. Exercising your rights is free. If Mexican law applies, we may only charge for reproduction, copies or shipping, and nothing if you give us an electronic means, such as your email. If the GDPR applies, we may charge a reasonable fee for additional copies or if your request is manifestly unfounded or excessive. If you ask for access, we send you your data in an electronic file.

If we process your data on behalf of a business, we will forward your request to that business, which is the controller, and help it respond. You can also contact the business directly.

Complaints. You can lodge a complaint with the relevant data protection authority:

  • in Spain, the Spanish Data Protection Agency (Agencia Española de Protección de Datos, www.aepd.es);
  • in Mexico, the Ministry of Anti-Corruption and Good Governance (Secretaría Anticorrupción y Buen Gobierno), through a data protection request (solicitud de protección de datos) filed within 15 business days after our response or, if we don’t respond, after our deadline has passed;
  • in other European Union countries, the authority of the country where you live, work or where the alleged infringement took place; and
  • elsewhere, the authority where you live.

13. How to request deletion of your data

Follow the instructions on our data deletion page. In short: email contacto@ilmarinen.io with the subject “Eliminar mis datos” (or “Delete my data”) and include the phone number or WhatsApp username you used, the approximate date of the conversation and, if you know it, the business name; if you represent a business or connected its accounts, its business portfolio or WhatsApp account ID, or its phone number; if you contacted us or were our client, the email address or phone number you used. We acknowledge your request within 3 business days and complete the deletion within 30 calendar days.

14. Data protection contact

The person designated to handle data protection matters, including ARCO rights requests, is Carlos Dominguez Delgado.

  • Email: contacto@ilmarinen.io
  • Address: 7345 W SAND LAKE RD STE 210 OFFICE 2070, ORLANDO, FL 32819

15. Children

Our website and services are aimed at businesses and professionals, not children, and as a controller we don’t knowingly collect children’s data. If a client business serves minors on WhatsApp, that business is responsible for complying with the rules that apply to that processing. If you believe you gave us a child’s data, email us at contacto@ilmarinen.io and we will delete it.

16. Changes to this policy

We may update this policy. We will post each new version on this page with its effective date and, for significant changes, notify our clients by email. If a change would let us use data we already hold in a new way, we won’t apply it to that data without your consent. The version you see here is effective as of 2026-11-17.

© 2026 ILMARINEN, LLC · 7345 W SAND LAKE RD STE 210 OFFICE 2070, ORLANDO, FL 32819 · Sunbiz (Florida) L26000517339 · +1 904 341 2547 · contacto@ilmarinen.io

Ilmarinen is a brand of ILMARINEN, LLC.

  • Privacy Policy
  • Terms of Service
  • Data Deletion

WhatsApp, Facebook and Meta are trademarks of Meta Platforms, Inc.