Privacy · PRV-10
Privacy Policy
This policy explains how Enigmatech Mexico SAPI de CV collects, uses, shares, protects and deletes personal data when you use the EnigmaSuite platform, and what choices and rights you have.
1. Who we are
Enigmatech Mexico SAPI de CV ("Enigmatech", "we", "us"), a company organized under the laws of Mexico, develops and operates EnigmaSuite, a business management platform offered as a service (the "Platform"). The Platform includes the web application at app.enigmasuite.com and customers' custom domains, its APIs, its mobile apps and this Trust Center.
Our registered address is Velázquez 324, Col. La Estancia, 45030 Zapopan, Jalisco, Mexico. Our Data Protection Officer can be reached at [email protected], and by phone at +52 33 1024 1040.
2. Our role
Businesses (our "customers") use the Platform to run their operations: sales, inventory, warehouses, fulfillment, logistics, invoicing, human resources and more. That means we handle personal data in two different roles:
- As a processor, on behalf of our customers. Data our customers upload, collect or connect to the Platform, for example their buyers' orders from TikTok Shop, belongs to the customer. The customer decides why and how it is processed, and we process it only on the customer's instructions and under our data processing terms. If you are a buyer, employee or end user of one of our customers, that customer's own privacy policy applies to your data, and you should contact the customer first.
- As a controller, for our own purposes. We decide how to process the account data of our customers' users, billing data, Platform logs and support interactions. This policy is our privacy notice for that data.
3. Personal data we process
3.1 As a controller
- Account data: name, email, phone number, organization, role and sign-in credentials of the people who use the Platform. Passwords are stored only as salted hashes.
- Billing data: legal name, tax ID, billing address and contact, and payment history. Card details are collected and held by our payment processor, not by us.
- Usage and security data: IP address, browser and device information, sign-in times, and records of actions taken in the Platform (audit logs).
- Support data: the messages and files you send us when you ask for help.
3.2 As a processor for our customers
Whatever our customers choose to manage in the Platform, for example: buyers' names, addresses, phone numbers and emails; order and shipment details; employee records; and data received from the sales channels, marketplaces and social accounts the customer connects (see section 4).
4. Data from TikTok Shop and other connected platforms
A customer can connect its TikTok Shop and Amazon seller accounts, and other sales channels such as Mercado Libre or Shopify, to the Platform. The connection is made by an administrator of the customer, through the platform's own authorization screen, and can be removed at any time.
4.1 What we receive from TikTok Shop
- Shop information: shop identifiers, shop name, region and the seller's account name.
- Authorization tokens that let our servers call the TikTok Shop API on the seller's behalf.
- Catalog data: products, variants, prices, inventory and listing status.
- Order data: order identifiers, items, amounts, status, and the shipping, fulfillment, cancellation and return information TikTok Shop provides, including the buyer's name, shipping address and phone number where TikTok Shop makes them available so the seller can deliver the order.
4.2 How we use it
Only to provide the features the seller uses in the Platform: keeping products, prices and inventory in sync; importing orders and fulfilling them from the seller's warehouse; sending shipping and tracking updates back to TikTok Shop; handling cancellations, returns and customer service; and showing the seller reports about its own shop.
4.3 What we never do with it
- We do not sell, rent or trade it.
- We do not use it for advertising, to market to buyers, or to build profiles.
- We do not combine it with other sellers' data or share it with other customers.
- We do not use it to train artificial intelligence models.
- We do not disclose it to anyone except the subprocessors listed in section 7, the service providers the seller itself configures (for example its shipping carriers), or authorities when the law requires it.
4.4 How long we keep it
For as long as the seller keeps the shop connected and needs the data for the purposes above. When the seller disconnects the shop or asks us to, we delete the stored tokens within 30 days and the data received from TikTok Shop within 90 days, unless the seller is legally required to keep specific records (for example, for tax purposes). We follow any stricter rule set by TikTok Shop's terms.
4.5 YouTube accounts connected to the social media planner
A customer's user can connect a YouTube channel to the social media planner of the Platform. EnigmaSuite uses the YouTube API Services; by connecting a channel, the user agrees to be bound by the YouTube Terms of Service, and Google's handling of data is described in the Google Privacy Policy.
The connection is made through Google's own consent screen. With the user's permission we access:
- Channel information (
youtube.force-ssl): channel identifier, name and avatar, to show which channel is connected. - Video upload (
youtube.upload): to publish the videos, titles, descriptions and privacy settings that the user creates and schedules in the Platform. - Comments (
youtube.force-ssl): to read the comments on videos published from the Platform and to post the replies the user writes. We only post a comment when the user sends it. - Authorization tokens that let our servers call the YouTube Data API on the user's behalf. They are stored encrypted in our secrets vault, never in plain text.
We store the channel identifier, name and avatar, the tokens, the posts scheduled from the Platform and the results of publishing them, and the comments and replies on those videos (comment text, author name and identifier, and date) so the user can follow each conversation in the Platform.
EnigmaSuite's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, the restrictions in section 4.3 also apply to YouTube data: we do not sell it, use it for advertising, share it with other customers or use it to train artificial intelligence models, and our personnel do not read it except with the user's consent, for security purposes or when the law requires it.
Revoking access and deleting data. The user can disconnect the channel at any time from the social media planner, and can also revoke EnigmaSuite's access from the Google security settings page. When the channel is disconnected in the Platform, we delete the stored tokens immediately. Revoking access from Google makes the tokens stop working right away; to have them and the rest of the data received from YouTube deleted, disconnect the channel or write to us (see section 12), and we delete that data within 30 days of the request. Videos already published on YouTube stay on YouTube and can only be removed there.
4.6 Pinterest accounts connected to the social media planner
A customer's user can connect a Pinterest account to the social media planner of the Platform, so the Pins the user creates and schedules there are published to that account. The connection is made through Pinterest's own authorization screen, and Pinterest's handling of data is described in the Pinterest Privacy Policy. With the user's permission we access:
- Account information (
user_accounts:read): account identifier, username, account type and profile picture, to show which account is connected. - Boards (
boards:readandboards:write): to list the user's boards so the user can choose where each Pin goes, and to create a new board when the user asks for it. - Pins (
pins:readandpins:write): to publish the images, titles, descriptions and destination links that the user creates and schedules in the Platform, and to confirm that each Pin was published. - Authorization tokens that let our servers call the Pinterest API on the user's behalf. They are stored encrypted in our secrets vault, never in plain text.
We store the account identifier, username and profile picture, the tokens, the posts scheduled from the Platform and the results of publishing them (the Pin identifier and link). We do not read or store the user's other Pins, boards, followers or any data about other Pinterest users. The restrictions in section 4.3 also apply to Pinterest data: we do not sell it, use it for advertising, share it with other customers or use it to train artificial intelligence models.
Revoking access and deleting data. The user can disconnect the account at any time from the social media planner; we then revoke the token with Pinterest and delete the stored tokens immediately. The user can also remove EnigmaSuite's access from the apps section of their Pinterest account settings. To have the rest of the data received from Pinterest deleted, disconnect the account or write to us (see section 12), and we delete that data within 30 days of the request. Pins already published stay on Pinterest and can only be removed there.
4.7 Google Calendar and Google Tasks connected to the sales agenda
A customer's user can connect their own Google account to the sales agenda of the Platform, so the visits they schedule with their accounts and contacts appear in their Google Calendar, with a Google Meet link when the visit is virtual. The connection is made through Google's own consent screen, each user connects only their own account, and Google's handling of data is described in the Google Privacy Policy. With the user's permission we access:
- Account information (
openid,email,profile): the email address and name of the Google account, to show which account is connected. - Calendar list (
calendar.calendarlist.readonly): the names and identifiers of the user's calendars, so the user can choose in which calendar each visit is published. We cannot change the list. - Calendar events (
calendar.events): to create, move and delete the events of the visits the user schedules in the Platform, including the Google Meet link Google generates for a virtual visit; and to read the user's events in the calendars they choose (title, place, start and end, status and Meet link) so the agenda can show when the user is busy and avoid double booking. - Tasks (
tasks): to create in Google Tasks the follow-up commitments the user records in the Platform, and to mark them as done in the Platform when the user completes them in Google Tasks. - Authorization tokens that let our servers call the Google Calendar and Google Tasks APIs on the user's behalf. They are stored encrypted in our secrets vault, never in plain text.
We store the account email, the tokens, the list of the user's calendars, the identifiers that link each visit and commitment with its event or task in Google, and a copy of the events described above for the period shown in the agenda. Those events are visible only to the user who connected the account. We do not store the attendees, descriptions or attachments of those events, and we do not access the user's contacts, email or files.
EnigmaSuite's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, the restrictions in section 4.3 also apply to Google Calendar and Google Tasks data: we do not sell it, use it for advertising, share it with other customers or use it to train artificial intelligence models, and our personnel do not read it except with the user's consent, for security purposes or when the law requires it.
Revoking access and deleting data. The user can disconnect the account at any time from the calendar settings of the Platform; we then revoke the token with Google, delete the stored tokens and delete the copy of the user's events immediately. The user can also revoke EnigmaSuite's access from the Google security settings page, which makes the tokens stop working right away. To have the rest of the data received from Google deleted, disconnect the account or write to us (see section 12), and we delete that data within 30 days of the request. Events and tasks already created in Google stay there and can only be removed in Google.
4.8 Zoom meetings and Zoom Calendar connected to the sales agenda
A customer's user can connect their own Zoom account to the sales agenda of the Platform, so that the virtual visits they schedule, and the meetings their contacts book from the user's public booking page, get a Zoom meeting link; and, if the user's Zoom account includes Zoom Calendar, so that those visits appear in their Zoom Calendar and their Zoom Calendar events are taken into account when the agenda shows when the user is busy. The connection is made through Zoom's own authorization screen, each user connects only their own account, and Zoom's handling of data is described in the Zoom Privacy Statement. With the user's permission we access:
- Account information (
user:read:user): the Zoom user identifier, account identifier, email address and name, to show which account is connected. - Meetings (
meeting:write:meeting,meeting:update:meeting,meeting:delete:meeting): to create, move and delete the scheduled meeting of each visit or booking, with the visit's title, time and duration. We store the meeting identifier, join link and passcode. We never store the host start link. - Calendar list (
calendar:read:list_calendar_lists): the names and identifiers of the user's Zoom calendars, so the user can choose which calendars the agenda reads and where each visit is published. - Calendar events (
calendar:read:list_events,calendar:write:event,calendar:update:event,calendar:delete:event): to create, move and delete the events of the visits the user schedules in the Platform; and to read the user's events in the calendars they choose (title, place, start and end, and status) so the agenda can show when the user is busy and avoid double booking. - Authorization tokens that let our servers call the Zoom API on the user's behalf. They are stored encrypted in our secrets vault, never in plain text, and a single connection serves both meetings and Zoom Calendar.
We store the account identifier and email, the tokens, the list of the user's calendars, the identifiers that link each visit with its meeting and its calendar event, and a copy of the events described above for the period shown in the agenda. Those events are visible only to the user who connected the account; other users of the same customer see only that the user is busy. We do not access the user's recordings, chats, contacts, meeting participants, email or files. The restrictions in section 4.3 also apply to Zoom data: we do not sell it, use it for advertising, share it with other customers or use it to train artificial intelligence models.
Revoking access and deleting data. The user can disconnect Zoom at any time from the video calls settings of the Platform; we then revoke the token with Zoom, delete the stored tokens and delete the copy of the user's events immediately. The user can also remove only Zoom Calendar from the calendar settings; we then stop reading the user's calendars and delete the copy of their events immediately, and keep the token only for the user's meetings. The user can also remove EnigmaSuite from the installed apps page of the Zoom App Marketplace: Zoom notifies us, and we delete the stored tokens and the copy of the user's events right away. To have the rest of the data received from Zoom deleted, write to us (see section 12), and we delete that data within 30 days of the request. Meetings and events already created in Zoom stay there and can only be removed in Zoom.
4.9 Amazon seller accounts connected through the Selling Partner API
A customer can connect its Amazon seller account to the Platform. The connection is made by an administrator of the customer through Amazon's own authorization screen (Seller Central), and the seller can revoke it at any time, in the Platform or in Seller Central. We never ask a seller for its Amazon password or access keys. With the seller's authorization we receive, through the Amazon Selling Partner API:
- Account and catalog data: the seller's identifiers and marketplaces, listings, prices, inventory and fulfillment settings.
- Order data: order identifiers, items, amounts, status, fulfillment channel (merchant-fulfilled, Fulfillment by Amazon or Seller Flex), shipments, tracking, cancellations, returns and reimbursements.
- Buyer personal information, only for orders the seller ships itself: the buyer's name, shipping address, phone number and the email address Amazon provides, requested with a short-lived Restricted Data Token for each order, and shipping labels for orders the seller fulfills from its own Seller Flex site. We do not receive buyer information for orders Amazon ships.
- Authorization tokens that let our servers call the Amazon API on the seller's behalf. They are stored encrypted in our secrets vault, never in plain text.
How we use it. Only to provide the features the seller uses: keeping listings, prices and inventory in sync; importing orders; and fulfilling the orders the seller ships itself (picking, packing, printing the shipping label, handing the package to the carrier, confirming shipment and tracking to Amazon, and handling cancellations and returns). Buyer personal information is used only for that shipping and to meet the seller's legal and tax obligations.
What we never do with it. Besides the restrictions in section 4.3: we do not use it to market to Amazon customers or to request, write or change reviews; we do not aggregate it across sellers or share it with other customers or affiliated companies; we do not use it to build insights about Amazon's business or to offer data services; we do not use it to train artificial intelligence models, and our AI-assisted features do not receive buyer personal information obtained from Amazon.
How long we keep it. Buyer personal information obtained from Amazon is deleted no later than 30 days after the order is delivered, unless the law requires the seller to keep a specific record for longer (for example, a tax invoice), in which case only that record is kept, encrypted and with restricted access, and only for the period the law requires. Shipping labels are generated on demand and handed to the seller's warehouse; we do not keep copies. All other data received from Amazon is deleted within 30 days after the seller disconnects its account, Amazon asks us to delete it, or we are no longer entitled to it. Deletion covers backups as they rotate. Details are in the Amazon Selling Partner API Data Protection Statement and the Data Retention and Deletion Policy.
5. How we use personal data as a controller
- To create and manage accounts and provide, maintain and support the Platform.
- To authenticate users and protect the Platform, our customers and their data (fraud prevention, security monitoring and incident response).
- To bill for the service and meet tax and accounting obligations.
- To send service, security, billing and legal notices.
- To comply with the law and respond to lawful requests from authorities.
- To improve the Platform using aggregated or de-identified information.
- With your consent, to send you news and offers about EnigmaSuite. You can opt out at any time using the link in each message or by writing to [email protected], and opting out does not affect the service.
We process personal data on the basis of our contract with you or your organization, our legal obligations, our legitimate interest in keeping the Platform secure, and your consent where the law requires it.
6. Cookies and similar technologies
The Platform uses cookies and browser storage that are strictly necessary to keep you signed in, remember your preferences (such as language) and protect your session. Public pages that a customer publishes through the Platform (for example event pages or online forms) may use analytics tools the customer chooses to enable; those tools are governed by the customer's own privacy policy.
7. Who we share data with
We use the following service providers (subprocessors) to run the Platform. Each one processes data only on our instructions and under data protection terms.
| Provider | Purpose | Location |
|---|---|---|
| Supabase, Inc. | Database, authentication, file storage and server functions | United States |
| Amazon Web Services, Inc. | Application servers, storage of tax files, and facial verification only where a customer enables it | United States |
| Cloudflare, Inc. | DNS, content delivery, TLS and DDoS protection | Global network |
| Stripe, Inc. | Billing for Platform subscriptions | United States |
| Twilio Inc. (SendGrid) | Transactional email | United States |
| Resend, Inc. | Operational alerts to our staff | United States |
| Anthropic, PBC and OpenAI, LLC | AI-assisted features; only the content users submit to those features. Their commercial terms do not allow them to train models on that content. | United States |
Customers may also connect services under their own accounts, such as payment gateways, sales channels, shipping carriers, maps or email providers. Those services receive data on the customer's instructions and under the customer's own agreements with them.
We may also disclose personal data when the law requires it, to our professional advisors under confidentiality, or to a successor in a merger or acquisition that takes on the obligations of this policy. We do not sell personal data.
8. Where data is stored
Platform data is stored and processed in the United States, in the infrastructure of the providers listed above. Traffic passes through Cloudflare's global network, encrypted. Our personnel, based in Mexico, access data remotely only when needed to provide and support the service. We protect data transferred to and stored in the United States with encryption, contractual safeguards and the controls described in our security policies.
9. How we protect data
We encrypt data in transit (TLS) and at rest (AES-256), isolate each customer's data at the database level with row-level security, apply role-based access with multi-factor authentication, keep third-party tokens in an encrypted secrets vault, log security-relevant activity, scan our code and dependencies for vulnerabilities, and follow a documented incident response process. Details are in our Trust Center.
10. How long we keep data
We keep personal data only as long as needed for the purposes described here:
- Customer data, including data from connected platforms: while the customer's contract is active. After it ends, the customer has 30 days to export its data, and we then delete it from our systems within 90 days (backups are overwritten as they rotate).
- Account data: for the life of the account, then as needed to address claims.
- Billing and tax records: for the period required by law.
- Security logs: at least 12 months and up to 24 months. Logs do not contain buyer personal information.
Data from TikTok Shop follows the rules in section 4.4, and data from Amazon follows the stricter rules in section 4.9, including deletion of buyer personal information no later than 30 days after delivery. Our full schedule is in the Data Retention and Deletion Policy.
11. Your rights
Where Enigmatech is the controller, you can ask us to give you access to your personal data, correct it, delete it or stop using it for a specific purpose (your ARCO rights under Mexican law), and you can withdraw your consent or limit how we use or disclose your data. Write to [email protected] with your name, how we can reply to you, proof of identity (or of your authority to act for someone else) and a description of your request. We will reply within the time limits set by the LFPDPPP.
If your data is in the Platform because one of our customers put it there (for example, you bought from a seller on TikTok Shop), please send your request to that customer. If you contact us instead, we will pass your request to the customer within 5 business days and help them answer it. We also assist TikTok Shop and sellers when they need us to delete, correct or provide data in response to a buyer's request.
12. How to request deletion
- Sellers: disconnect TikTok Shop (or any other channel) from the Integrations section of the Platform, and write to [email protected] from an administrator account if you also want the data already received to be deleted.
- Buyers and other individuals: write to [email protected] with the subject "Data deletion request", and include the name of the business you dealt with and, if you have it, your order number.
- Social accounts connected to our social media planner: see our data deletion instructions. For YouTube you can also revoke access from your Google account permissions (see section 4.5), and for Pinterest from your Pinterest account settings (see section 4.6).
We confirm receipt within 5 business days and complete verified requests within 30 days, unless the law requires the data to be kept longer.
13. Breach notification
If a security incident affects personal data, we notify affected customers without undue delay and no later than 72 hours after confirming it, and we notify platform partners such as TikTok Shop within 24 hours when data obtained from them is involved. When Amazon Information may be involved, we notify Amazon within 24 hours of detecting the incident, even before it is confirmed. We also notify individuals and authorities when the law requires us to.
14. Children
The Platform is a business tool and is not directed to children. We do not knowingly collect personal data from children as a controller.
15. Changes to this policy
We review this policy at least once a year and update it when our practices or the law change. The version number and date at the top show the current version. If we make a material change, we tell customer administrators by email or in the Platform before it takes effect.
16. Contact and complaints
For any question about this policy or your personal data, contact our Data Protection Officer at [email protected]. If you believe your data protection rights have been violated, you can also contact the Mexican authority responsible for the protection of personal data.