This is a translation of the Spanish version of Platica's privacy notice. If there is any discrepancy, the Spanish version prevails.
This notice explains how personal data is processed on Platica's website, through its services and through its integrations. The AI integrations section and its annexes form part of this same notice.
Data controller and contact
We are CREACIÓN DE RIQUEZA S.A. DE C.V. (Mexican tax ID, RFC CRI130411KA6), operating as Platica.mx. Our address is Lázaro Cárdenas 3857, Jardines de San Ignacio, Zapopan, Jalisco, postal code 45040, Mexico.
For privacy questions, requests concerning your data and withdrawal of consent, write to hola@platica.mx.
Purposes of processing
Primary purposes. We process the data needed to provide the products and services requested, manage accounts and connections, enforce permissions, respond to support requests and protect the service. Depending on the feature used, this may include account and contact data, communications, documents and technical logs. The AI integrations section details their categories and purposes.
Secondary purposes. We may process data for promotions, information about features, product analytics and the other secondary purposes described in this notice. Communications may be sent by email, SMS, WhatsApp or other channels used for your service. You can opt out of these purposes by writing to hola@platica.mx with the subject “Secondary purposes”. Opting out will not affect the provision of the service requested.
ARCO rights and requests
You may exercise the rights of access, to learn about your data and how it is processed; rectification, to correct inaccurate or incomplete data; cancellation, to request its erasure where applicable; and opposition, to request that it not be processed for certain purposes.
Send your request to hola@platica.mx. Include:
- Your name and a means of receiving notifications.
- The right or request you wish to exercise, the data related to the request and information that allows us to locate it. For an access request, you do not need to describe every piece of data beforehand.
- Proof of your identity and, if acting through a representative, proof of their identity and authority to represent you.
- For rectification, the changes requested and the documentation supporting them.
Do not send identity documents, passwords, API keys or authentication codes through platic or a conversation with an AI assistant. Use the privacy contact channel for the identification procedure.
We will communicate our determination through the means you provided within a maximum of 20 business days after receiving your request. Where applicable, we will give effect to it within 15 business days after communicating the response. These periods may each be extended once for an equal period where circumstances justify it.
Data cancellation requests are handled in accordance with applicable legal obligations. Some data may need to be kept to meet those obligations, and recovery copies may remain until they expire; see the retention annex.
Website cookies and technologies
The public website uses cookies, browser storage and measurement technologies to understand navigation, link usage and performance, and to measure campaigns. Its code includes Google Analytics, Meta Pixel, LinkedIn Insight, Apollo and PostHog. Depending on the technology, browser identifiers, pages visited, interactions and technical connection information may be processed.
You can restrict cookies and storage through your browser settings. Some features may be affected. For questions or objections to secondary purposes, use the contact channel indicated in this notice.
These public website technologies are separate from the features of the platic connector and the web app session recordings described in the annex. PostHog session recording is disabled on the public website.
See the privacy policies of Google, Meta, LinkedIn, Apollo and PostHog.
Withdrawing consent
You can request withdrawal of consent by writing to hola@platica.mx, following the identification and request procedure in this notice. Withdrawal may affect features that require the corresponding processing. Processing cannot always be stopped immediately where there is a legal obligation to keep or process the data.
Revoking an AI connection, canceling a subscription and requesting data deletion are separate actions; see retention and controls and the retention annex.
Recipients and transfers
Companies supporting payment collection, service email and promotional communications may be involved, as well as infrastructure providers and the features described in the recipients annex. The AI platform you connect and configured webhook destinations receive the data needed for authorized operations. Not every feature uses every provider.
The integrations section explains recipients and international transfers, together with the applicable documents.
Changes to this notice
Changes will be published at platica.mx/privacidad, with the update date. You can access the language versions from this same page.
Integrations with AI assistants and platforms
This section supplements Platica's privacy notice for the use of platic, Platica's connector for AI assistants, in ChatGPT, Claude, Cursor, Grok and other compatible platforms, when available. The identity, address and contact channels of the data controller are set out in this same notice.
Platica's role regarding the data
Platica is the data controller for the account, connection and usage data of people who connect platic. For the contacts, conversations and documents that each organization adds to its workspace, Platica acts as a data processor on behalf of that organization, which is the controller of that data. If you are a contact of an organization that uses Platica, please direct your requests to that organization; if we receive them directly, we will forward them and help the organization respond.
What data is used and why
The organization that manages the workspace adds its contacts, conversations and documents and configures its users and permissions. Platica processes that data to provide the requested features. When you connect platic, access is limited to the authorized workspaces and the permissions in effect.
Depending on the feature used, these categories are processed:
- Account and connection: name, email, user and workspace identifiers, roles, permissions, and dates of authorization, use or revocation.
- Contacts and communications: names, phone numbers, emails, notes, tags, custom fields, messages, comments, participants, files, images, audio, video and transcripts.
- Operations and agents: instructions, configuration, knowledge documents, templates, campaigns, scheduled messages and usage data.
- Technical logs: request identifiers, IP address, connecting client information, dates, parameters, results, errors and security events.
- Use of the Platica web app: navigation, performance and error events, and session recordings with on-screen text masked.
Primary purposes. This data is used to authenticate the connection, enforce permissions, run the authorized operations and automations, verify usage, troubleshoot issues and protect the service. The integration does not request access to the AI platform's history, memories or files; it only receives what the platform sends to run each operation.
Secondary purposes. We also use data for product analytics, web app session recording, and quality and cost monitoring of AI features. These purposes are not necessary to provide the service. You can opt out by writing to hola@platica.mx with the subject "Secondary purposes"; opting out will not affect the service.
Model training. Platica does not use workspace data or platic results to train artificial intelligence models, and does not authorize its providers to do so.
Data you should not include. Only use data you are authorized to process and share. Do not include passwords, API keys, authentication codes, government IDs, payment card data or health information in platic operations. Do not include other sensitive personal data or data about minors either. Authentication is handled through Platica's connection flow.
Who receives the data
The AI platform you choose receives the results of permitted operations, which may contain contact and communication data. Infrastructure, messaging, AI, search, document processing, analytics, diagnostics and email providers may also be involved, depending on the feature and configuration. Webhook destinations you configure receive the selected events and their data. See the annex on recipients and applicable documents.
International transfers
The providers listed in the recipients annex may process data outside Mexico, mainly in the United States. Providers acting on Platica's behalf do so as data processors under data processing agreements. Results are delivered to the AI platform you connect at your instruction, which is necessary to provide the service you request; that platform processes them under its own terms.
Retention and controls
Workspace data does not expire automatically by default. You can manage its deletion or request it through the privacy channel. The retention and deletion annex details retention periods and their exceptions.
You can review permissions, choose the authorized workspaces, remove the connection from the platform you use and ask Platica to revoke access. Revoking authorization prevents further use, but disconnecting platic does not delete existing data in Platica or copies the AI platform keeps under its own policy; for the latter, use that platform's privacy controls.
To exercise your rights of access, rectification, cancellation or opposition, or to revoke your consent, write to hola@platica.mx following the procedure in this notice. Do not send passwords or API keys.
Annex: platic data retention and deletion
This annex is part of Platica's privacy notice and supplements the section on AI integrations. It distinguishes active data, technical logs and recovery copies.
| Category | Retention and deletion |
|---|---|
| Workspace operational data, including contacts, communications and documents | Kept while part of the workspace, with no general automatic expiration. You can manage its deletion or request it through the privacy channel. When the owner requests deletion of the workspace and meets the service conditions, the process starts after 7 days and can be canceled before it begins. Deletion runs in the background, and copies in backups remain until those backups expire, as indicated below. |
| Application and API logs | 30 days. They may contain request information and, especially for errors, their results. |
| Infrastructure audit logs | 400 days. |
| Integration and webhook logs | 30 days, followed by automatic deletion, which may be delayed. Some historical logs have no expiration date; you can request their cancellation. |
| Copies of notifications received from messaging channels | Recent ones expire after 30 days. Older ones, which may include messages and contact data, have no automatic deletion and are being purged. You can request their cancellation. |
| Other operational logs | Between 7 and 30 days. |
| Attachments sent through web chat | 365 days. |
| Contact import files | Kept after the import and currently not deleted automatically; they are being purged. Imported contacts remain in the workspace regardless of this file. You can request their cancellation. |
| Analytics events and AI event metadata | 84 months (7 years). Events beyond that period are deleted in the next monthly cleanup. |
| Input, output and tool content of AI events | 30 days for events recorded since June 2026; afterwards the event is kept without those fields. Events recorded between December 2025 and May 2026 keep that content within the general event period while their purge is completed. |
| Web app session recordings | 30 days for new recordings, with on-screen text masked. Earlier recordings may show on-screen content and network requests, and expire according to the period in effect when they were recorded. |
| Database recovery history | 7 days. |
| Weekly database backups | 98 days from creation. Deleted data may remain in these backups until they expire. |
| Files deleted from storage | Recoverable for 7 days after deletion. |
| Authorization records | Expiration or revocation prevents use of the permission, but its records have no automatic deletion period. You can request their cancellation through the privacy channel. |
| Tax and billing records | May remain after a workspace is deleted. Their cancellation is assessed under applicable legal obligations. |
Deleting a contact does not always delete all of its data. The deletion feature may mark it as deleted and keep its phone number, conversations and related identifiers. To request cancellation of your personal data, use the procedure in this notice.
Copies that an AI platform, messaging channel or webhook destination processes under its own terms follow their own retention rules. See the recipients annex and the receiving service's controls.
Annex: recipients and applicable documents
This annex is part of Platica's privacy notice. Which services are involved depends on the connected platform, the feature, the channel and the configuration used. Listing a provider does not mean all data is sent to all of them.
AI platform and destinations you choose
When you connect platic, the chosen platform receives the results of authorized operations. These may include contact, conversation, document or workspace record data. How it processes its own copies depends on its policies, terms, account type and configuration.
| Platform | Applicable information |
|---|---|
| ChatGPT / OpenAI | Privacy policy, with links to regional versions. |
| Claude / Anthropic | Privacy policy; for business services, also the commercial terms and data processing addendum, depending on the service contracted. |
| Cursor | Privacy policy. |
| Grok | xAI privacy policy; if you use Grok within X, also see the X privacy policy. |
Webhook destinations you configure receive the selected events and the data they contain. When you send messages or take other authorized actions, the channel and recipients receive the information needed for that action.
Services that may be involved in Platica features
These providers process data on Platica's behalf under the listed documents, where applicable to the contracted product. Platica remains responsible for its obligations under this notice and its agreements with customers.
| Function and data needed | Services and documents |
|---|---|
| Infrastructure, authentication, storage and technical logs | Google Cloud / Firebase: Google privacy, Firebase privacy and security, Firebase data processing terms and Google Cloud data processing addendum, depending on the product. |
| AI processing of instructions, content, documents or results, depending on the configured model | Google / Gemini: privacy and Gemini API terms. Microsoft / Azure: privacy, data protection addendum and information on models sold by Azure. OpenAI API: privacy and API data usage. Anthropic API: privacy, commercial terms and data processing addendum. |
| Routing of AI requests when the model uses AI Gateway | Vercel: privacy, data processing addendum and AI product terms. The provider that runs the model depends on the configured route. |
| Messaging and social networks: content, participants, attachments, identifiers and statuses | Meta: privacy. WhatsApp: business data processing terms. Bird / MessageBird: privacy. |
| Search and retrieval of content indexed for the feature | Typesense: privacy. Chroma: privacy. |
| Processing of documents and pages provided as knowledge | LlamaIndex / LlamaParse: privacy. Jina AI: legal documents, which refer to the Elastic privacy statement and the Elastic data processing addendum. |
| Product analytics, web app session recording and AI monitoring; service email | PostHog: privacy. AI monitoring may include messages, outputs, arguments and tool results, with the periods set out in the retention annex. Resend: privacy. |
The model name alone does not identify the recipient: a model hosted on Azure is processed by Microsoft, while a direct call to its maker's API follows a different path. The feature's configuration determines which services are involved.
