Privacy Policy
Last updated: November 8, 2026
Last updated: November 8, 2026.
This Privacy Policy (Aviso de Privacidad Integral) explains how SERVIACERO ASCEND S.A. de C.V., operating EvaAI, with domicile at Blvd. Adolfo López Mateos 1709, Piso 4, Los Gavilanes, León de los Aldama, Guanajuato 37266, Mexico ("EvaAI," "we," "us"), collects, uses, and protects information when businesses use our software to deploy AI chatbots, connect their messaging channels, when administrators access our website or dashboard, and when we contact businesses as prospects (Section 18). This document constitutes the Aviso de Privacidad of EvaAI in accordance with Mexico's LFPDPPP.
For details on how we process data on behalf of business customers, see our Data Processing Agreement (available at /legal/dpa).
If you have questions, reach us at support@goeva.ai and we will respond promptly.
This Policy is available in English and Spanish. In case of conflict between language versions, the Spanish version shall prevail.
Contact: Message us on WhatsApp
1) Scope
This Policy applies to the EvaAI website, admin dashboard, APIs, and the messaging integrations that we provide to our customers.
It does not govern how our customers handle information they export or store outside of EvaAI.
2) Roles
- For end-user conversations handled by EvaAI on behalf of a business, the business is the controller and EvaAI is the processor/service provider.
- For our website, billing, analytics, abuse prevention, and account administration, EvaAI is the controller.
3) Information We Process
Business account data such as company name, email, phone, messaging channel identifiers, configuration, and billing details.
Message and media data, including message content, attachments, templates, metadata, delivery status, and related conversation history.
Technical and security data like logs, IP addresses, device/browser information, diagnostic events, and fraud-prevention signals.
Support communications that you send to us.
4) How We Use Information
To provide, secure, and improve the EvaAI platform; deliver conversations; enable integrations; and troubleshoot issues.
To operate analytics, billing, compliance, monitoring, abuse prevention, and product development.
To respond to support requests and communicate updates about the service.
5) Sharing
We do not sell personal data.
- Service providers (sub-processors) that host or help deliver our services, including infrastructure, storage, monitoring, email, analytics, payment processing, voice and SMS communications, and artificial-intelligence model providers, under confidentiality and security obligations. A current list of our sub-processors is available in our Data Processing Agreement (/legal/dpa).
- Authorities or third parties when required by law, to enforce our terms, or to investigate abuse.
Measurement of our business customers' ads
When a business has Ads enabled, EvaAI, as processor on that business's behalf and instructions, sends eligible sale, quote, or qualified-lead events from WhatsApp ads to Meta through the business-messaging Conversions API. An event carries its type and time, value and currency only when an amount is recorded, the opaque WhatsApp click identifier (ctwa_clid), and the WhatsApp Business Account identifier. This transmission does not include the customer's phone number, email address, or message content.
EvaAI sends eligible sale, quote, and qualified-lead events to the business's connected Google Ads account through the Data Manager API. Matching uses the Google click identifier (gclid) captured by Eva's web chat, together with gbraid or wbraid when they come with it, or SHA-256 hashes of verified phone numbers or email addresses when eligible. This feature sends no readable phone number, email address, or message content.
With an owner or admin's OAuth authorization, EvaAI reads the connected Google Ads account's identifiers, names, currency, time zone, campaigns, ad groups, ads and ad copy, budgets and status, daily impressions, clicks, spend, conversions, geographic results, and recent change history. It also resolves eligible Google click identifiers to campaigns.
EvaAI stores the synced account settings, ad objects, daily metrics, and change history in the business's Eva account to show Ads reports and changes and generate suggestions. For weekly suggestions, EvaAI may send selected ad settings, copy, recent performance, and Eva-attributed sales to OpenAI's model service to generate proposals; the account owner and chosen members may also receive an email summary of aggregate results. EvaAI does not use information received from Google APIs to train AI models.
An owner or admin can preview and apply proposed Google Ads budget, pause, or ad text changes in Eva and can revert applied changes. If the business enables Automatic mode, Eva may apply budget changes without a separate click on each proposal and may revert its own budget increases or pause campaigns to enforce the business's monthly spend caps. When the business selects a Google Ads account, Eva may create conversion actions for its configured sale, quote, or qualified-lead stages.
The purpose is to measure and improve the business's ads. The business is the controller and determines the applicable lawful basis; EvaAI acts as processor. Meta and Google receive the data for this purpose under the business's own platform agreements, including Meta Business Tools Terms and Google Ads customer-data terms.
The sales-sending setting starts on when the corresponding Ads platform is enabled. Meta receives an event only when the opportunity remains in a conversion stage and the ad, permission, account, and time-window requirements are met. Google sending requires a connected and selected Google Ads account, accepted Google customer-data terms, and Customer data use enabled in Google Ads; Eva checks the terms and effective setting through the Google Ads API before sending. The business can turn off each platform separately in Ads > Settings; turning it back on does not send earlier sales. An owner or admin sees a one-time notice while sending is on. That notice is not a prior consent request.
An owner or admin expressly authorizes OAuth to connect and read ad accounts, can disconnect, and EvaAI stores the Google refresh token encrypted. Google requests include ad_user_data and ad_personalization consent fields: a recorded website ad_user_data grant or denial is sent as such, and otherwise the applicable field is unspecified; ad_personalization is unspecified. Google may limit processing or attribution without required consent.
While Google Ads remains connected, EvaAI retains the synced ad objects, daily metrics, suggestions, change history, and encrypted refresh token without a fixed deletion period. Disconnecting deletes the stored token, connected-account records, synced ad objects, daily metrics, and suggestions, and stops new reads and sends; it does not revoke the OAuth grant at Google; the business can remove EvaAI's access at any time from its Google Account's third-party access settings. Recorded change history and conversion delivery records remain after disconnect until the account deletion described in Section 8.
6) Data Transfers
We operate primarily in Mexico and the United States and may process data in other regions where our infrastructure or service providers are located.
When legally required, we use appropriate safeguards such as Standard Contractual Clauses.
7) Legal Bases
Our customers are responsible for any required notices or consents to their end-users.
- Performance of a contract (providing the EvaAI service).
- Legitimate interests (security, fraud prevention, product operation and improvement).
- Legal obligations (record-keeping, compliance).
- Compliance with Mexico's Ley Federal de Proteccion de Datos Personales en Posesion de los Particulares (LFPDPPP) and its regulations.
8) Retention
We store conversations and configuration data while an account is active to enable features such as inbox history and analytics.
When a subscription is cancelled, we honor the paid period: the service and the AI agent keep running until the end of the period you already paid for. When the subscription terminally ends, at the end of that paid period or after a failed payment once our automatic retries are exhausted, the account is paused.
While paused, most data is held in a reversible state so the account can be reactivated at any time before permanent deletion; reactivation restores the service. During this period the account owner keeps access to log in, manage billing, request a data export, and reactivate.
Certain resources are reclaimed on a staged schedule. A dedicated voice or telephone number, if the account has one, is released approximately 30 days after a voluntary cancellation, or approximately 60 days after a pause caused by non-payment; once released, a later reactivation is assigned a new number.
Approximately 150 days after the pause, if the account has not been reactivated, we permanently and irreversibly delete conversations, personal data, media, and knowledge-base content, and disconnect the messaging channels. Backups containing the deleted data are purged in the ordinary course of our backup rotation.
Fiscal and billing records, including electronic invoices (CFDI), are retained for the period required by Mexican tax law (approximately five years), even after the data above is deleted.
Before permanent deletion, we notify the account owner and offer the option to export the account's data or to reactivate.
9) Security
We use administrative, technical, and physical safeguards appropriate to the data we process, including encryption in transit (HTTPS), access controls, least-privilege practices, monitoring, and audit logging.
No method of transmission or storage is 100% secure; we continually improve our defenses.
10) Cookies and Similar Technologies
We use cookies and similar technologies on our website to provide essential functionality (session management, authentication, locale preferences), improve our services (analytics), and support third-party integrations (payment processing via Stripe, scheduling via Calendly).
We measure our own website traffic first-party: the pages viewed, the site or campaign that referred the visit, the browser and device, the preferred language, and an approximate location (country, region, city) derived from the IP address. The IP address itself is never stored: it is hashed on arrival and discarded, and it is never used to identify you. We also record anonymous navigation and engagement: the pages opened, how far each was scrolled, the time spent actively reading, the sections seen, and clicks on our WhatsApp button. These records are grouped under a random per-visit session identifier that expires when you close the tab, so that we can improve the site; this measurement stores no personal data and no IP address. We do not sell this or any other personal data.
Separately, if you choose to leave your WhatsApp number on our website so that we can write to you, we store that number together with the context of that visit: the page, the campaign, the random per-visit session identifier described above, your browser and the approximate location derived from your IP address. We use it to contact you about EvaAI and, if you reached our website from a Google ad, to measure that ad: we share with Google only a one-way hashed version of the number, which cannot be turned back into it. The same applies to the number you use to write to us on WhatsApp. We never use it to build a profile and never sell it to third parties. You can ask us to delete it at any time at support@goeva.ai.
You can manage cookie preferences through your browser settings. Disabling certain cookies may affect site functionality.
Third-party services used on our site may set their own cookies subject to their own privacy policies.
For users in the European Economic Area (EEA), we provide additional cookie management options as required by applicable law.
11) Rights and Requests
Business administrators can access or update data through the dashboard or by emailing support@goeva.ai.
End-users of our customers should contact the business they messaged. We act as processor and will assist our customers as required by law.
Under Mexican data protection law (LFPDPPP), you have the right to Access, Rectify, Cancel, and Oppose the processing of your personal data (ARCO rights). To exercise these rights, contact privacy@goeva.ai.
We will respond to ARCO requests within 20 business days of receipt, as required by LFPDPPP Article 32.
12) Account Closure and Data Handling
An authorized account owner may request closure via the dashboard or by contacting support. Cancelling the subscription starts the lifecycle described in "Retention": the paid period is honored, then the account is paused, and data is deleted on the staged schedule set out there.
Login remains available throughout: closing or pausing an account never locks the owner out of billing, data export, or reactivation. Fiscal and billing records (CFDI) are retained as required by Mexican tax law even after other data is permanently deleted.
13) Children
Our services are intended for businesses and are not directed to children.
14) Sensitive Data
EvaAI does not intentionally collect sensitive personal data (datos personales sensibles) such as health information, racial or ethnic origin, religious or moral beliefs, union affiliation, political opinions, sexual preference, or biometric data.
Business customers are responsible for ensuring that sensitive personal data is handled appropriately when transmitted through the Services and for obtaining the express written consent required under LFPDPPP for the processing of such data.
15) Automated Decision-Making
The EvaAI platform uses artificial intelligence models to generate automated responses in conversations on behalf of our business customers. These AI agents may qualify leads, route inquiries, provide product information, and perform other automated actions based on their configuration.
Business customers using EvaAI are responsible for disclosing to their end-users that they may be interacting with AI-powered agents. End-users may request human intervention by contacting the business directly.
16) Data Breach Notification
In the event of a personal data breach that may significantly affect the economic or moral rights of data subjects, EvaAI will notify affected parties immediately, as required by applicable law, including LFPDPPP Article 19.
The notification will include the nature of the breach, the categories of data affected, the likely consequences, and the measures taken or proposed to address and mitigate the breach.
17) Consent Withdrawal
You may withdraw your consent to the processing of your personal data at any time by contacting privacy@goeva.ai. Withdrawal of consent does not affect the lawfulness of processing carried out before the withdrawal.
Please note that withdrawing consent for data processing that is essential to providing the Services may require the closure of your account, as we may not be able to continue delivering the Services without processing certain data.
18) Marketing Communications
We may send you service-related communications (account notifications, billing updates, security alerts) which are necessary for the operation of your account and are not optional.
If we send promotional or marketing communications, you may opt out at any time by following the unsubscribe link in the email or by contacting support@goeva.ai. Opting out of marketing does not affect service-related communications.
Business prospecting (B2B)
EvaAI may email businesses that could be interested in our services or in our Referral program, such as marketing agencies. This part of the Policy is the privacy notice for the contact people at those businesses.
Data we process: the business name, its website, the contact email address the business publishes, the name and role of the contact person when the business publishes them, a short note about what its website says about its work (so that our message is relevant), and, if you reply, your reply and our follow-up. We do not process sensitive personal data.
Where it comes from: we find the business in public business directories (such as INEGI's DENUE) or web searches; we take its email address and its contact person's details only from what the business itself publishes on its website or its Google business profile. We do not buy lists and we do not guess email addresses.
Purpose: to introduce EvaAI's services and our Referral program to your business, follow up with at most three emails in total and, if you are interested, schedule a call. We use this data for no other purpose, we do not sell it, and we do not share it with third parties for their own purposes.
Service providers: to verify that an address exists, send and receive these emails and record replies, we use email and verification providers and our own platform, acting on EvaAI's behalf under confidentiality obligations (Sections 5 and 6).
Opting out: you can ask us not to write again at any time by replying "baja" (or "unsubscribe") to any of our emails or by writing to privacy@goeva.ai. We honor it immediately and stop every follow-up. To keep honoring it, we retain only your email address or your business's domain, the date and the reason on a suppression list and use them for nothing else.
If you do not object once we have made this notice available to you, we will understand that you agree to this processing under the LFPDPPP; you can object at any time by the means above. We keep the data only while it is needed for this purpose.
You can exercise your rights of Access, Rectification, Cancellation and Opposition (ARCO) and withdraw your consent by writing to privacy@goeva.ai, as described in Sections 11 and 17.
19) Third-Party Links
Our website and Services may contain links to third-party websites or services not operated by EvaAI. We are not responsible for the privacy practices of those third parties. We encourage you to review the privacy policies of any third-party services you access.
20) Updates
We may update this Policy as our product evolves. If changes are material we will provide at least 30 days advance notice via email or in-product alerts.
21) Shopify Integration Data
When a merchant connects their Shopify store to EvaAI, we receive specific data from the Shopify Admin API to run the merchant's AI agent and the merchant's CRM in Eva on the merchant's behalf. This section discloses what we receive, why, and how long we keep it.
- Catalog data: product titles, descriptions, prices, variants, images, inventory levels, and store locations. Used to answer product, stock, and pricing questions.
- Order data: order number, status, line items, fulfillment and tracking information, plus the email address used at checkout. Used to answer order-status and tracking questions when the end-customer gives the order number and a matching email or phone. If order import is turned on for the store, Eva also keeps the store's orders and checkouts in the merchant's CRM in Eva, to show each contact's purchases and to run the merchant's own automations, such as a message after an abandoned checkout.
- Customer data: name, email, phone number, default address (where granted by Shopify Protected Customer Data Access). Used to recognize a returning customer in a conversation.
- Customer import: while customer import is on, Eva also adds the store's customers to the merchant's own CRM in Eva, with their Shopify tags, order count, last order date, and marketing preferences. Customer import starts on when a store is connected, and the merchant can turn it off. Importing a customer never sends them a message.
- Marketing preferences: while customer import is on, if a customer unsubscribed from the store's SMS marketing in Shopify, Eva leaves that phone number out of the merchant's marketing messages. The merchant is responsible for having the consent required to message its customers.
- Draft order data: drafts EvaAI creates when an end-customer asks for a custom order or invoice. Created on the merchant's behalf at the merchant's instruction.
- EvaAI itself never sells this data and never uses it to profile people, for its own marketing or advertising, or to train AI models.
Purpose Limitation
Shopify-derived data is processed only to operate the merchant's AI agent and the merchant's CRM inside EvaAI, on the merchant's instructions. EvaAI never uses Shopify customer data for its own purposes, such as its own advertising or marketing, profiling, model training, or automated decision-making with legal effects.
Retention
While the merchant remains connected, Shopify data is refreshed via webhooks and a nightly reconciliation job. We retain it for as long as the connection is active.
When the store is disconnected from EvaAI or the app is uninstalled, we delete the store's orders, checkouts, catalog, and connection data within 90 calendar days. Contacts that exist only because of Shopify are deleted. On contacts the merchant also has from other channels or from its own work in Eva, we remove that store's link, the marketing preference imported from it, the store tag, and its purchase totals, and keep the rest of the contact. Backups containing the data are purged within an additional 60 days.
Shopify's privacy requests are handled within 30 days: `shop/redact` deletes the store's data under the rule above; `customers/redact` applies the same rule to that one customer; for `customers/data_request`, EvaAI sends the store owner the data it holds linked to that Shopify customer.
End-Customer Rights
End-customers of a merchant using EvaAI may exercise their rights (access, rectification, deletion, opt-out) by contacting the merchant directly. The merchant is the data controller. Upon receiving the merchant's instruction, EvaAI will execute the requested action on its systems within the response windows set out elsewhere in this Policy.
22) Contact Us
For privacy-related questions or to exercise your data rights:
- General: support@goeva.ai
- Privacy and data protection: privacy@goeva.ai