1. General information
CreatuAgente (creatuagente.io) is a platform for creating and deploying artificial intelligence agents. The data controller is CONSULTIA LLC (CreatuAgente), a limited liability company organised in New Mexico (United States), with registered address at 1209 Mountain Road Place NE, STE N, Albuquerque, NM 87110, United States, and contact email info@creatuagente.io.
2. Data we collect
- Registration data: name, email address and encrypted password.
- Phone number: used to verify your identity via a one-time passcode (OTP) sent by SMS when creating your account and, where applicable, when changing the number.
- Usage data: conversations generated by deployed agents, usage statistics and credits consumed.
- Payment data: managed by Stripe. We do not store credit card data.
- Integration data: access tokens for third-party services (Instagram, WhatsApp, Gmail, etc.) needed for the agents to work. These tokens are stored encrypted.
- End-user messages: messages sent to deployed agents (and, on Instagram, the comments the agent replies to) are stored to maintain conversation history and give the agent context in subsequent turns.
2.1 If you chat with this website's assistant
On the public pages of creatuagente.io you can open a chat with our own AI assistant, which answers questions about CreatuAgente, recommends a plan and helps you sign up. In that chat CreatuAgente is the data controller (unlike our customers' agents, for which we act as processor). The chat only loads when you click the assistant button.
- What data we process: the messages you write and the assistant's replies, an anonymous visitor identifier and your conversation identifier, which are stored in your browser's local storage (see the cookie policy), and your IP address, which we use to limit abuse. We do not ask you to identify yourself; if you share personal data in the chat, we only process it to answer your query.
- Purpose and legal basis: to answer your questions about the service and help you sign up if you ask (steps taken at your request prior to entering into a contract, Art. 6(1)(b) GDPR) and to improve the assistant and prevent abuse (legitimate interest, Art. 6(1)(f) GDPR). If you sign up from the link the assistant gives you, we record it as the source of your sign-up.
- Who receives it: the same providers that generate the replies of any agent (the AI models and infrastructure described in section 5); it is not used to train AI models or for advertising.
- Session recordings: if you accept analytics, PostHog session recording masks the chat text.
- Retention and your rights: we keep the conversations for as long as they are needed to assist you and improve the assistant, and you can ask for their deletion or exercise your other rights by writing to info@creatuagente.io (section 8).
3. Use of data
We use the collected data to:
- Provide and improve the platform's services.
- Process payments and manage subscriptions.
- Send service-related communications (no advertising without consent).
- Comply with legal obligations.
CreatuAgente lets you connect AI agents with Instagram, Facebook and WhatsApp accounts through the Meta APIs (WhatsApp specifics are detailed in section 4.4). When you enable one of these integrations:
- We store the access token of your page or account in encrypted form so we can reply to messages automatically.
- Direct messages received through Instagram/Facebook and, if the business enables comment replies, comments posted on the connected account's own posts are processed by the configured AI models and stored in our database. If the business uses the dashboard's comment moderation, we read the comments on its own account's posts live, only to show them to the business, and we post, reply to, hide or delete comments only when the business asks us to; comments viewed this way are not stored in our database.
- We do not share your end users' data with third parties, except with the providers needed to generate the responses, detailed in section 4.2 and section 5.
- You can revoke access at any time from your account settings.
- The Meta applications through which this integration works are published by IA CONSULTING (30 N Gould St, Sheridan, Wyoming 82801-6317, United States), a business verified by Meta that acts as the registered developer of the applications. CONSULTIA LLC operates the CreatuAgente platform and processes the data as IA CONSULTING's service provider, under a written agreement consistent with the Meta Platform Terms, and as data processor for the connected business.
4.1 Which Instagram and Facebook data we process, and on whose behalf
The business that connects its account is the data controller of its customers' data; CreatuAgente acts as a data processor on its behalf and under its instructions. With the permissions the business grants through Instagram/Facebook login we process:
- Direct messages (DMs): the content of received and sent messages (text, attachments, and voice notes, which are transcribed to text), their timestamps, and the Instagram-scoped (IGSID) or page-scoped identifiers of sender and recipient, together with the username and profile identifier when the API provides them.
- Comments: only on the connected account's own posts and only if the business enables comment replies: the comment text, the identifiers of the comment and of the post, and the identifier and username of the author. The private reply the agent sends to the author is stored as part of their conversation. In addition, if the business uses the dashboard's comment moderation, we fetch live from Instagram the connected account's recent posts and their comments (text, date, author's username and whether they are hidden) only to show them to the business, without storing them, and we post, reply to, hide or delete comments only at the business's request.
- Connected account: the identifier and username of the Instagram professional account or Facebook page, and its encrypted access token.
- Conversation origin: the reference of the ad, post or link from which the customer started the chat, so the business can measure where its conversations come from.
- Follow relationship: if the business enables the option to reply only to accounts it follows, we ask Meta whether the connected account follows the user who writes and store that information with the contact.
4.2 Who this content is sent to
To generate each response and the internal analyses of the conversation (classification, tags, reports and generated follow-ups), and to describe the images contacts send, the conversation content (messages or comments, together with the agent's configuration) is sent to the AI model providers acting as sub-processors. The active transport for these calls is OpenRouter, Inc., which routes each one preferably to the provider of the model the business has chosen —Anthropic (Claude), Google (Gemini, through Google AI Studio), xAI (Grok) and, for GPT-6 and GPT-6 Luna, Microsoft Azure (EU region) and then OpenAI, DeepSeek and other open-weight models hosted by infrastructure providers, and, if the chosen model refuses to answer, an alternative model through that same route— and, if that provider is unavailable, to another infrastructure provider hosting the same model, always within our account's configuration, which only allows providers that do not use the content to train models and do not retain it except, for a limited period and solely to monitor abuse and keep the service secure: depending on the provider, only content their automated systems flag as potential abuse (which their staff may review) or the logs of a short monitoring period, which they then delete. Because the provider serving each call may vary, the content may be processed in the United States, in the European Union or in other regions; GPT-6 and GPT-6 Luna are preferably served from Microsoft Azure in the EU. Google Cloud Vertex AI remains as the emergency transport, and Google Cloud also transcribes voice notes (Speech-to-Text and Vertex AI), describes the videos that contacts send, generates the embeddings of the messages the agent uses to remember the conversation and, if the business enables voice replies, synthesises the audio (Text-to-Speech); some of these Google services may process the data outside the EU (section 5). None of these providers uses the content to train their models (on OpenRouter, because of our account configuration described above, and on Google Cloud, under its terms of service) or for advertising purposes. Beyond these providers, the content only reaches the features and integrations the business itself enables —for example, its AI assistant through MCP, ManyChat, GoHighLevel, voice with ElevenLabs or lead notifications by e-mail—, which are listed in section 5.
4.3 Retention and how to request deletion
- Retention: conversations, messages, comments and contact data are kept while the business's account is active, to maintain the agent's history and context; on the free plan, messages older than 180 days are deleted automatically. If the business deletes a deployment (the connection between an agent and a channel), its contacts, appointments, recorded sales, webhook receipts, campaigns and conversation analyses are deleted with it, while the conversations and their messages are kept in the account, no longer linked to a channel, until the account is deleted. When the business deletes its account, its contacts are erased immediately and the rest of the data is removed within a maximum of 30 days.
- If the business revokes access from Instagram, Meta notifies us and we immediately delete the access token and deactivate the channel, which stops receiving and processing messages. For Facebook we do not receive that notice from Meta: the business must delete the deployment from the CreatuAgente dashboard (which deletes the stored token) or write to us. If it disconnects Instagram from the CreatuAgente dashboard, we delete the token and the identifiers of the connected account and deactivate the channel. If it disconnects its WhatsApp number from the WhatsApp Business app, we deactivate the channel, which stops processing messages. In all these cases the conversation history is kept for the business until it deletes its account or requests deletion.
- If the business requests deletion of its data through Meta (app data deletion request), we delete the conversations, messages, contacts, appointments, recorded sales, webhook receipts and campaigns of the Instagram channels linked to that account, remove the token and return to Meta a confirmation code with which to check the status of the request. This automatic deletion only covers the Instagram accounts linked at the time of the request: for WhatsApp, and for accounts that are already disconnected, deletion is requested through the route in the next point, and the data is also deleted, to the extent described in the first point, when the deployment or the account is deleted.
- If you are an end user who has messaged an agent on Instagram, Facebook or WhatsApp, you can ask us to delete your data by following the instructions on our data deletion page or by writing to info@creatuagente.io; we will handle the request within a maximum of one month.
4.4 WhatsApp (Cloud API and WhatsApp Business app coexistence)
If the business connects its WhatsApp number to an agent through Meta's WhatsApp Cloud API —including coexistence, which lets it keep using the WhatsApp Business app on its phone with the same number—, the business is the data controller and CreatuAgente acts as a data processor on its behalf. We process:
- Contact: the phone number (wa_id) and WhatsApp profile name of each person who messages the business.
- Message content: text, images, voice notes (which are transcribed to text), video and documents.
- In coexistence, data synced from the WhatsApp Business app: contacts (name and phone number) and conversation history of up to 180 days, capped at 200 messages and 60,000 characters per contact. This imported history does not count towards any counter.
- Messages the business sends from its phone (echoes): they are stored in the conversation, shown in the dashboard and pause the agent in that conversation.
- Connected account: the identifiers of the WhatsApp Business account (WABA id) and of the number (phone number id), and the business token, stored encrypted with AES-256-GCM.
- Purposes and disconnection: we use this data only to generate the business's agent replies, show the conversations in the dashboard and send the follow-ups and templates the business itself configures; never for advertising, for sale or to train models. The content is sent to the AI providers described in section 4.2. The business can disconnect the number at any time from the WhatsApp Business app (Settings → Account → Business Platform) or by deleting the deployment in the dashboard; when disconnected, the channel is deactivated and stops processing messages. Retention and deletion follow what is described in section 4.3.
- Campaign recipients: if the business launches a WhatsApp campaign, we process the phone number, the name and any data the business itself adds for each recipient, whom it selects from its contacts or imports from a CSV file. Before launching it, the business declares that it has those people's permission to contact them on WhatsApp (opt-in); obtaining that permission is its responsibility as data controller. Recipients are only sent Meta-approved templates, never anyone who has opted out (next point), and their send records are deleted automatically some time after the campaign ends and, in any case, when the deployment is deleted.
- Opting out of the business's messages: if a person sends the business's number a message that is only an opt-out word —STOP or BAJA (also “unsubscribe”, “darse de baja” or the “Stop promotions” button)—, they stop receiving the messages the business initiates: follow-ups, appointment reminders, campaigns and templates. If the channel is active they receive a confirmation, and they can receive those messages again by writing START or ALTA; the business cannot remove the opt-out itself. If they write again, the agent and the business can still reply. That opt-out message is not processed by the agent or sent to the AI providers. We keep their number with the opt-out mark solely to be able to honour it (legitimate interest, Art. 6(1)(f) GDPR), for as long as the business keeps that deployment and its account: that is why it is not removed by the automatic clean-up of contacts that no longer have conversations, and it is deleted when the deployment or the account is deleted.
5. Sharing data with third parties
CreatuAgente uses the following third-party services to operate:
- OpenRouter, Inc.: active transport for the calls to the AI models that generate the agent's responses, the internal analyses of conversations (classification, labels, reports and generated follow-ups) and the description of the images that contacts send; it routes each one preferably to the provider of the selected model —Anthropic (Claude), Google (Gemini, through Google AI Studio), xAI (Grok) and, for GPT-6 and GPT-6 Luna, Microsoft Azure (EU region) and then OpenAI, DeepSeek and other open-weight models hosted by infrastructure providers, and, if the chosen model refuses to answer, an alternative model through that same route— and, if it is unavailable, to another infrastructure provider hosting the same model, always within our account's configuration, which only allows providers that do not use the content to train models and do not retain it except, for a limited period and solely to monitor abuse and keep the service secure: depending on the provider, only content their automated systems flag as potential abuse (which their staff may review) or the logs of a short monitoring period, which they then delete. Depending on the provider serving each call, the content may be processed in the United States, in the European Union or in other regions. None of these providers uses the content for advertising purposes.
- Stripe: payment processing.
- Twilio: as a CreatuAgente sub-processor, sending verification codes (OTP) by SMS to verify your phone number. In addition, if the business connects WhatsApp through Twilio, in that role it is connected and contracted by the business itself with its own Twilio account, and it is not a CreatuAgente sub-processor: that account is used to send and receive the messages of that channel (their content and the contact's phone number).
- Google Cloud: hosting of the infrastructure and database in the European Union (Belgium region: Cloud Run, Cloud SQL / PostgreSQL and Memorystore); it also provides file storage (Cloud Storage), served through its global delivery network. Vertex AI is the emergency transport for the AI models, including the description of the images that contacts send when it is active. In addition, Google Cloud generates the embeddings of the knowledge base documents and of the conversation messages (the agent's memory), describes the videos that contacts send, transcribes incoming voice notes (Speech-to-Text / Chirp and Gemini on Vertex AI) and, when the business enables voice replies, synthesises the audio with Text-to-Speech; if the business creates a custom voice, it also processes the voice sample it uploads. Some of these AI services may process the data outside the EU: speech synthesis takes place in the United Kingdom, embeddings are processed in the location Google chooses, and the Gemini and Grok models on Vertex AI (transcription with Gemini, video description and emergency transport) may be processed in the United States. It does not use the content to train models or for advertising purposes.
- Meta (Facebook / Instagram / WhatsApp): sending and receiving messages through their APIs, including the WhatsApp Cloud API.
- PostHog: product analytics (heatmaps and session recording) for the dashboard and website, with data hosted in the European Union and a signed data processing agreement. Only enabled with your prior consent.
- Composio: connectors to the third-party tools the business chooses to link to its agent (Google Calendar, Google Sheets, Gmail, HubSpot, etc.). It only receives the data the agent sends to those tools; it has no access of its own to conversations.
- Resend: transactional e-mail to the platform's customers (verifications, service notices and, if the business enables it, new-lead notifications with an excerpt of the conversation).
- ElevenLabs: it is connected and contracted by the business itself with its own key, and it is not a CreatuAgente sub-processor. When the business enables voice-note replies with ElevenLabs, it receives only the text of the reply to be voiced.
- Meta Platforms (Meta Platforms Ireland Ltd. and Meta Platforms, Inc.): measurement of our own ads with the Meta pixel and the Conversions API, only if you consent: by accepting the “Marketing” category or by ticking the optional box at sign-up. It receives your account events (sign-up, free trial, checkout started and first payment) with your email, phone number and identifier hashed (SHA-256), the IP address, the browser and, if you arrived through an ad, the click identifier; the pixel and the _fbp/_fbc cookies only if you accept the “Marketing” category. You can withdraw your consent at any time, and the data may be processed in the United States (see section 9).
- The business's AI assistant (MCP connection): it is connected and contracted by the business itself, and it is not a CreatuAgente sub-processor. If the business connects its own AI assistant (for example, Claude, ChatGPT or Grok) through the MCP connection, that assistant, on the business's instructions, can read its agents (their configuration and prompt), deployments, conversations, analyses, metrics, knowledge base, tags, prompt versions and credit usage and, if the business grants it write permission, propose and apply changes to its agents' prompt, settings, knowledge base and tags.
- Cloudflare Turnstile: when enabled, anti-bot verification for sign-up, login, password recovery, resending the OTP code, accepting invitations and the public demo chat. It receives technical data from the browser and the IP address, not the content of conversations.
- ManyChat: it is connected and contracted by the business itself, and it is not a CreatuAgente sub-processor. If the business manages any of its channels with ManyChat, ManyChat delivers to us the messages of the contacts on those channels and receives the agent's replies to send them.
- GoHighLevel: it is connected and contracted by the business itself, and it is not a CreatuAgente sub-processor. If the business connects it, GoHighLevel sends us the messages of its contacts for the agent to answer and the lead, appointment and sale events the business configures, and it receives the agent's replies, which we post to the business's GoHighLevel conversation through its Conversations API and with its token, and the new-lead notifications (lead.capturado) the business enables.
- Calendly: it is connected and contracted by the business itself with its own account, and it is not a CreatuAgente sub-processor. If the business gives its agent access to its Calendly (through Composio), the agent checks the available times and books appointments with the name and e-mail the contact provides, and Calendly sends us, through its signed webhook, the booking events of that account (bookings, cancellations, reschedules and no-shows, with the e-mail of the person booking). We record as the agent's appointments the bookings we can attribute to one of its links, conversations or contacts, and discard the rest.
We do not sell personal data to third parties. International transfers: CONSULTIA LLC, which operates the platform and processes the data, is incorporated in the United States, and several of the providers above, including the AI model providers, may process the data in the United States or in other regions outside the European Union, so using the service involves international transfers of personal data.
6. Health data, legal data and other special categories
Some businesses that use CreatuAgente, such as clinics, practices or law firms, serve customers who may share in the conversation with the agent health data or other special categories of data (Article 9 GDPR), data about their legal matters, or data relating to criminal convictions and offences (Article 10 GDPR). The following applies to this data:
- Controller and processor: as with the rest of its customers' data, the business is the data controller of this data and CreatuAgente acts as a data processor, on its behalf and under its instructions.
- Legal basis and information: to process special categories of data, the business needs one of the exceptions in Article 9(2) GDPR (usually the data subject's explicit consent, or whichever applies to it) and must inform its customers accordingly. In the legal profession, the business must also respect professional secrecy.
- Minimisation: the business should configure its agent to ask for no more data than is strictly necessary, without collecting medical records, diagnoses or complete documentation through the chat, redirect that information to a channel of its own and erase the data it no longer needs, through the deletion routes described in section 4.3.
- No training or advertising: like the rest of the conversation content (section 4.2), this data is not used to train AI models or for advertising purposes, and the model providers they are routed to through OpenRouter do not retain it except for a limited period and solely to monitor abuse and keep the service secure, on the terms of that section (which include possible review by their staff of content flagged as potential abuse).
- Recipients: this data is received by the same third parties as the rest of the conversation content, described in section 5: (a) as CreatuAgente sub-processors, the AI model providers through OpenRouter, Inc. and Google Cloud (hosting, embeddings, voice, images and videos), and Composio or Resend when the business enables tools or lead notifications by e-mail; (b) the services the business itself connects and contracts, which are not CreatuAgente sub-processors: the platform of the channel the conversation comes through (Meta, its Twilio account, ManyChat or GoHighLevel), voice with ElevenLabs, its Calendly account, its webhooks and its AI assistant through MCP.
7. Data retention
Data is kept while the account is active; on the free plan, messages older than 180 days are deleted automatically. If you delete a deployment, its contacts, appointments, recorded sales, webhook receipts, campaigns and analyses are deleted with it, and its conversations and messages are kept in your account, no longer linked to a channel, until you delete it. When you delete your account, we immediately deactivate your deployments and erase your contacts and your phone number together with its verification status; the rest of your personal data and that of your agents —including the conversations, messages and appointments of all your channels— are deleted within a maximum of 30 days, unless there is a legal obligation to retain them. If a WhatsApp contact opts out by writing STOP, we keep their number with that mark, solely to honour the opt-out, for as long as the deployment exists (section 4.4). Instagram, Facebook and WhatsApp data additionally have the specific mechanisms described in sections 4.3 and 4.4. Copies that the AI model providers may retain for security, described in section 4.2, are not subject to these periods: they delete them at the end of their limited period.
8. User rights
You have the right to access, rectify, erase and port your data, as well as to object to its processing. To exercise these rights, contact info@creatuagente.io. Learn how to delete your data on our data deletion page.
9. Cookies
We use necessary technical cookies to keep your session working and, only if you consent, product analytics cookies (PostHog) for heatmaps and session recording of the dashboard. The legal basis for analytics is your consent, which you can withdraw at any time; recordings are kept for a maximum of 30 days. Form fields and areas holding sensitive data (conversations, prompts, knowledge base, tokens and payment details) are masked or blocked in recordings. We do not record or measure the conversations of our clients' end users: the portal, public demos and custom domains are excluded entirely. Only if you accept the “Marketing” category, which is separate from analytics, we load the Meta pixel (cookies _fbp and _fbc) on the home, industry landing, contact, sign-up and billing pages. In addition, only if you consent, by accepting that category or by ticking the optional box at sign-up (separate from cookies), our server sends Meta Platforms (Conversions API) your account events (sign-up, free trial, checkout started and first payment), together with your email, phone number and user identifier hashed (SHA-256), the IP address and browser you act from, the plan amount and, if you arrived through an ad, the click identifier, plus those cookies if you accepted the category, to measure which ads work. If you only tick the box and reject cookies, we do not load the pixel or use Meta cookies: only those events are sent, from our server. The legal basis is your consent, which you can withdraw at any time from “Cookie preferences” (by turning off “Marketing”), by clicking “Reject” in the cookie notice or with your browser's GPC signal; your most recent explicit decision always prevails, including over the sign-up box. When you withdraw it, we stop sending events, delete those cookies from your browser and erase the IP address, browser and cookies we had stored. Meta also processes this data in the United States: the international transfer relies on the EU-U.S. Data Privacy Framework, under which Meta Platforms, Inc. is certified, and on the European Commission's standard contractual clauses. See our cookie policy for details.
10. Security
We implement technical and organizational measures to protect data: token encryption, HTTPS communications, restricted database access and periodic audits.
11. Contact
For any questions about this policy, you can contact us at info@creatuagente.io.