Toldo privacy policy
Version 2026-11-16. Last updated: November 16, 2026.
This English version is a courtesy translation. If it differs from the Spanish version, the Spanish version prevails. Read the Spanish version
Some details in this document are still pending. They're marked like this: .
In this document
Toldo is one Shopify app with modules. Which modules a store sees depends on its country and setup:
- Marketplace sync: connects the store to seller accounts on online marketplaces (Mercado Libre first) to keep stock and prices in step, bring marketplace orders into Shopify and pass tracking both ways, and shows the questions buyers ask on its Mercado Libre listings so the merchant can answer them.
- CFDI 4.0 (Mexico): issues Mexican electronic invoices: a self-invoicing portal for buyers, the factura global, credit notes and cancellations. The invoices are stamped by an authorized certification provider (PAC); Toldo is not a PAC.
- KSeF (Poland): issues Polish structured invoices and sends them to KSeF, the national e-invoicing system. WooCommerce and Wix stores use it through our platform API.
- Search: runs the online store's search, with filters and sorting, and sorts the products in its collections.
- Translation: translates the store's content into the languages the merchant chooses and writes the translations to Shopify.
This policy explains what personal data the app processes, why, who receives it, how long we keep it and what rights people have. The public website's forms (the application and the waitlists) have their own privacy notice (aviso de privacidad) at https://toldo.io/en/legal/privacy-notice-mexico (section 11).
1. Who we are
Toldo is provided by LT3 LLC, 30 N Gould St Ste R, Sheridan, WY 82801, United States, Wyoming filing ID 2026-002124508 ("we", "us").
- Privacy contact: privacidad@toldo.io
- Data protection officer: Pending: [Data protection officer contact]
2. Our role
- Merchants' customers (buyers and visitors to its store): the merchant decides why and how its orders are synced and invoiced, and how its store's search and translation work. The merchant is the controller of its customers' data and of any personal data in its store's texts, and we process it on its behalf:
- in the EU, as its processor under Article 28 GDPR. The data processing agreement is at https://toldo.io/legal/dpa.
- in Mexico, as its persona encargada under the Ley Federal de Protección de Datos Personales en Posesión de los Particulares (DOF 2025-03-20).
- in Brazil, as its operador under the LGPD (section 12).
- Merchant accounts: we are the controller of the data we need to run the merchant's account, billing and support.
3. What we process
3.1 Every module
| Category | Data | Source |
|---|---|---|
| Store and account | Store domain; the Shopify access session for the store (access token, refresh token, granted permissions); app settings; plan and monthly usage counts (invoices issued, marketplace orders imported); the store's country, time zone and currency | Shopify, when you install the app |
| Agreement record | The version and time you accepted the data processing agreement, the name you typed, and the seller details at that moment | You |
| Support | Your name, email address and messages, if you contact us | You |
| Alert emails | Your store's contact email, to tell you when something needs your attention (for example, if Toldo loses access to your store or to an account) | Shopify or you |
| Technical logs | IP address, time, store domain, the URL requested (for a search in your store, it includes the search term) and error details of requests to our servers | Automatically |
3.2 Marketplace sync
| Category | Data | Source |
|---|---|---|
| Connected seller accounts | The marketplace, site (e.g. Mercado Libre Mexico), seller account id and nickname, and the account's access and refresh tokens, stored encrypted with a key kept outside the database; connection status, rules (stock, price, order import, who invoices marketplace sales) and the last error | You, when you connect an account, and the marketplace |
| Listing links | Marketplace listing and variation ids, titles, SKUs and barcodes, the linked Shopify products and variants, the last stock and price sent, and sync status. No personal data. | The marketplace and your store |
| Order links | The marketplace order (or cart) id, the Shopify order created for it, its status, the shipment id and the tracking number | The marketplace |
| Buyers' questions (Mercado Libre) | The questions buyers ask on your listings, as they wrote them, with the listing asked about, Mercado Libre's question id and status, your answer and their dates. Never the asker's name, email, phone or Mercado Libre user id, beyond what they write in the question. | The marketplace (your answers: you) |
| Activity log | What was synced or failed, with listing and order references but no customer details | Created by the app |
Buyers' details in marketplace orders. When the app imports a marketplace order, it reads what the marketplace provides to fulfil it and creates the Shopify order. If you ship the order yourself, the app writes the buyer's name, delivery address and, where available, phone into the Shopify order. It doesn't write the buyer's email or create a customer record. We don't keep a copy: our database keeps the order's ids, status and tracking number. The one exception is invoicing (section 3.3): if you choose Toldo to invoice your marketplace sales, the buyer's tax details are stored with the invoice request.
3.3 CFDI 4.0 (Mexico)
| Category | Data | Source |
|---|---|---|
| Issuer setup | The PAC that holds your account, your organization id there, and its API keys, stored encrypted; the serial number and expiry of your CSD (certificado de sello digital). The CSD itself is uploaded to the PAC and never stored by us. Issuing settings, SAT product and unit keys. | You |
| Invoice requests | For a nominative invoice: the buyer's RFC, name or company name, postal code, tax regime, CFDI use and email, stored encrypted; for card payments, the buyer's answer to "credit or debit?"; the request's status and the SAT or PAC error code | The buyer (self-invoicing portal), you (admin), or the marketplace's billing information for its orders |
| Invoice documents | The stamped CFDI (XML), its PDF, its folio fiscal (UUID), series and folio, the receiver's details inside it, the PAC's id for it, cancellation requests and SAT's answers, and a random token for the document link | Created by the app, the PAC and SAT |
| Factura global records | Which orders went into each factura global and their net amounts. No buyer details. | Created by the app |
| Order data for the invoice | Order number and date, items (name, SKU, quantity, price, discount, tax), shipping, currency, payment method, refunds | The order in Shopify, or the marketplace order imported into Shopify |
3.4 KSeF (Poland)
| Category | Data | Source |
|---|---|---|
| Seller details | Business name, NIP, address; optionally KRS, REGON and BDO numbers, bank account (IBAN), place of issue and invoice footer text. For a sole trader these are personal data. | Prefilled from the store, edited by you |
| KSeF connection | Environment (Sandbox or Production); the NIP the connection acts for; your KSeF token, stored encrypted, with only its last 4 characters shown again; short-lived KSeF access tokens, stored encrypted; status and last error | You, and KSeF |
| Buyer data | Name (company or person), billing address, NIP and company name entered in the cart | The Shopify order and the cart block; for WooCommerce and Wix stores, the order sent through our platform API |
| Invoice documents | Invoice XML (FA(3)), UPO, PDF, KSeF number, QR verification link, invoice history and a random token for the document link | Created by the app and KSeF |
3.5 Search
| Category | Data | Source |
|---|---|---|
| Catalog copy | Your products and their variants (title, description, vendor, type, tags, options, SKU, barcode, image, prices, inventory, status and dates), the product metafields you choose for filters (up to 20) and your collections, with their products and their order. The search index holds only the active products published to your online store. No customer data, unless your store keeps some in those metafields. | Your store in Shopify |
| Rules and settings | Your search rules (pin, boost, hide or redirect a search's results), your synonyms, your collections' sorting rules with each collection's previous order, the module's settings and its activity log, with no customer data | You; the activity log is created by the app |
| Order records | For each order search reads, paid or not: its id, its dates (created and last updated), whether it counts as a sale (paid, or paid and partly refunded) and whether it was cancelled. No buyer details. | Your orders in Shopify (those of the last 90 days, and new ones) |
| Sales lines | For each sale, per product: the order id, the product, the units sold (refunded ones left out) and their amount | Your orders in Shopify |
| Search counts | Per day and search term: how many searches there were, how many found nothing and how many clicks their results got. Never a term that looks like an email address, or a long number that found no product. | Your online store, when your customers search |
People who search your store. Your online store sends our servers what your customers search for and filter by and, when they click a result, the term they searched. Search uses no cookies or sessions and, apart from the technical logs (section 3.1), doesn't keep their IP address: it uses it only in the server's memory, as a keyed hash whose key changes every day, to limit requests and to count each IP address once a day per term. As popular searches, other customers are offered only terms searched at least 5 times in 30 days (each IP address counts once a day), on at least two days, that always found products and got at least one click, and never long numbers or anything that looks like a web address. The catalog copy is kept in our database and the search index on our own search server, both at our hosting provider (section 5), not in a third-party search service.
3.6 Translation
| Category | Data | Source |
|---|---|---|
| Translation settings | The languages and markets you translate into, with their variant, tone and your notes for the translator; your glossary, the names never to translate, your brand voice and your options | You |
| Translation records | One per text, language and market: who made its translation (the app, another app or a person), whether it's locked, a fingerprint (hash) of the original and one of the translation, the engine that made it and whether it needs review. Not the text. | Created by the app from your store's content in Shopify |
| Translation memory | The translation of each fragment already translated, identified by a fingerprint of the original, so the same translation is never paid for twice | The translation engines |
| History and usage | Recent translation runs: their kind, status, counts, coverage and estimated cost, with their first failures (which text, in which language and why, sometimes with an excerpt of the text of up to 60 characters); each month's usage (requests, characters, tokens and cost); and which items in your store changed and are waiting to be translated (their ids only) | Created by the app |
The texts being translated. To translate, the app reads your store's texts and their existing translations from Shopify, sends the texts to a translation engine (section 5) and writes the new translations to Shopify. We don't keep a copy of the texts: only their translations, in the translation memory, and sometimes an excerpt in a failure. If your store's texts contain personal data, for example names in reviews stored in custom fields, that memory and those excerpts may contain it too.
We don't place advertising or analytics cookies, in the admin app or on your storefront.
4. Why we process it
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Syncing stock, prices, orders and tracking between your store and your marketplace accounts, and showing your Mercado Libre buyers' questions so you can answer them, on your instructions | 3.2 | As processor: your instructions (Art. 28). For your account: contract (Art. 6(1)(b)) |
| Issuing, stamping, sending, storing, correcting and cancelling invoices, on your instructions | 3.3, 3.4 | As processor: your instructions (Art. 28). For you, issuing invoices is a legal duty (Mexican and Polish tax law) |
| Search, filters and sorting in your online store, search analytics and sorting your collections, on your instructions | 3.5 | As processor: your instructions (Art. 28). For your account: contract (Art. 6(1)(b)) |
| Translating your store's content into the languages you choose, on your instructions | 3.6 | As processor: your instructions (Art. 28). For your account: contract (Art. 6(1)(b)) |
| Running the app and your account; plan limits | 3.1 | Contract (Art. 6(1)(b)) |
| Support | Support data, plus the minimum order or invoice data needed to solve the problem | Contract (Art. 6(1)(b)) |
| Security, abuse prevention and debugging | Technical logs | Legitimate interest in a secure, working service (Art. 6(1)(f)) |
| Our own accounting and legal duties | Account and billing records | Legal obligation (Art. 6(1)(c)) |
We use buyer data only to sync and invoice the merchant's orders, to show the merchant its Mercado Libre buyers' questions and, if the merchant uses search, to count each product's sales. We don't sell personal data, use it for advertising or profiling, or use it to train AI models.
5. Who receives it
- Our hosting provider, as our processor: Render Services, Inc., servers in Virginia, United States.
- Shopify. The app works through Shopify's APIs. It creates the orders imported from marketplaces and writes invoice numbers and document links to app-owned fields (metafields) on the order. If you use translation, it writes your store's translations to Shopify.
- The marketplaces you connect (Pending: [Marketplaces you can connect]), under their own terms and privacy policies. We send them what you ask the app to sync: listing stock and prices, shipment status and tracking numbers, your answers to buyers' questions and, if you choose Toldo to invoice your marketplace sales, the stamped invoice (XML and PDF), which the marketplace makes available to the buyer.
- The PAC (Mexico) that stamps your CFDI, Facturapi, located in the United States, where its servers are. It receives each invoice's content, including the receiver's RFC, name, postal code and tax regime, and passes it to the SAT. Depending on your settings it may also email the invoice to the buyer.
- The tax authorities. Mexico's SAT receives every stamped CFDI through the PAC. Poland's Ministry of Finance receives every invoice sent to KSeF's production environment. Both keep these as tax records under their own laws, not on our behalf: such invoices can't be deleted, only corrected or cancelled.
- Narodowy Bank Polski (NBP). For KSeF invoices in another currency, the app downloads the NBP exchange rate from its public API. Each request contains only a currency code and a date.
- Translation engines, only if you use translation: Anthropic (Claude), located in the United States, and, if we use them alongside or instead of Claude, DeepL (DeepL SE), located in Germany, or Google Cloud Translation (Google LLC), located in the United States. To translate your store into the languages you choose, they receive the texts being translated (for example products, collections, pages, blog posts, menus, your theme and your store policies), with context such as a product's type, vendor and collections, and the translation settings each engine uses, such as your glossary and your notes for Claude. To translate, the app never reads your customers or your orders. If a text being translated contains personal data, for example names in reviews stored in custom fields, it is sent like the rest of the text.
- Authorities, when the law requires it.
6. Where the data is stored
- Our database is hosted in Virginia, United States.
- When data from the European Economic Area is processed outside it, we rely on the European Commission's Standard Contractual Clauses or another valid transfer mechanism: Render Services, Inc. (hosting, United States), under the EU-U.S. Data Privacy Framework, with Standard Contractual Clauses as a fallback; Anthropic, PBC (translation, if used, United States), under Standard Contractual Clauses; Google LLC (Cloud Translation, if used, United States), under the EU-U.S. Data Privacy Framework and Standard Contractual Clauses.
- Mexican law allows us to use processors outside Mexico. We bind them to the same obligations we have.
- For data from Brazil, see section 12.
7. How long we keep it
| Data | Retention |
|---|---|
| Settings, connections, listing and order links, activity log, search's catalog copy, and translation records, memory, history and usage | While the app is installed. After you uninstall, until the store erasure 48 hours later (section 8) |
| Search's order records and sales lines | 120 days from the order's date |
| Search counts | 400 days (about 13 months) |
| Mercado Libre buyers' questions and your answers | Answered or closed ones, 90 days after their last change; unanswered ones, at most 224 days (about 7 months) after they were asked. All of an account's when you disconnect it, and at the store erasure (section 8) |
| Marketplace tokens, PAC keys, KSeF tokens | Until you disconnect or uninstall, then deleted at once |
| Invoice documents (CFDI and KSeF) and invoice requests | While the app is installed, so you can always download them (Pending: [CFDI retention period] for CFDI). Before uninstalling you can download them in monthly ZIP files. After uninstalling we delete them as described in section 8. |
| CFDI held by the SAT, and invoices in KSeF | Kept by the tax authorities under their own rules. In Mexico you can always download your CFDI from the SAT; in Poland from the ministry's Aplikacja Podatnika KSeF |
| Translations written to your store | Kept by Shopify in your store, where they're yours, also if you uninstall the app |
| Backups | Encrypted and overwritten on a rolling basis within 7 days |
| Technical logs | 30 days at most |
| Support messages | Pending: [Support message retention period] |
| Our billing records | As long as accounting law requires |
8. Shopify's privacy requests
Shopify sends apps three mandatory privacy requests (webhooks). We answer each within 30 days.
- Customer data request (
customers/data_request): we prepare a list of the invoices and invoice requests we hold for that buyer's orders and give it to the store owner in the app, with a download of the invoices concerned. If you use search, its activity log says what it keeps of an order, without buyer details, and how many of those orders it holds. - Customer erasure (
customers/redact):- We remove the buyer's personal data from our local copies (invoice drafts, invoice requests, tracking numbers and, in search, the records and sales lines of their orders) unless the law requires it to be kept.
- Invoices accepted by KSeF stay in KSeF. A stamped CFDI stays with the SAT, and we keep its XML because Mexican tax rules require the issuer to keep it. The legal invoice file itself can't be altered.
- We record what we removed and what was kept and why, and we tell the store owner.
- Store erasure (
shop/redact, 48 hours after uninstalling): we delete everything we hold for that store, including connections, tokens, keys, settings, local invoice copies, search's catalog copy and index, and the translation data. Backups expire as stated in section 7.
9. Security
- In transit: all traffic to and from the app over the internet uses TLS.
- At rest: the database and backups are encrypted. Marketplace tokens, PAC keys, KSeF tokens and buyers' tax details in invoice requests are also encrypted with AES-256-GCM, using a key kept outside the database (Render's encrypted environment variables).
- Never shown again: tokens and keys are not displayed after you save them; for KSeF we show only the last 4 characters.
- Your CSD stays with the PAC: if you upload it in the app, the certificate, its private key and its password pass through our server only to reach the PAC. We never store or log them.
- Access: limited to Pending: [Who has production access] who need it, with strong passwords and two-factor authentication. Access to customer data is logged.
- Test data: test and production data are kept apart. Sandboxes receive only test orders and sample invoices, and before anything goes to the KSeF sandbox, the app replaces seller and buyer details with fictional ones.
- Incidents: if a personal data breach affects a merchant's data, we tell the merchant without undue delay, within Pending: [Breach notice period] of becoming aware of it.
10. Your rights
- Everyone: you can ask for access to your data, correction, erasure, restriction, portability, or object to processing. In Mexico, you can exercise your ARCO rights: access, rectification, cancellation and opposition. Write to privacidad@toldo.io. We reply within one month (in Mexico, within 20 business days, as the law requires; in Brazil, within the time limits in section 12).
- Buyers: please contact the store you bought from first. The store is the controller, and we help it answer. Rights over invoices are limited by tax law: an invoice that the law requires a business to keep can't be erased.
- Complaints:
- In Poland: the Prezes Urzędu Ochrony Danych Osobowych (ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl), or the authority in the EU country where you live or work.
- In Mexico: the Secretaría Anticorrupción y Buen Gobierno (https://www.gob.mx/buengobierno), within 15 business days of our answer to an ARCO request.
- In Brazil: the Autoridade Nacional de Proteção de Dados (ANPD), see section 12.
11. The toldo.io forms
When someone applies to the founding-partner program on https://toldo.io, or joins one of its waitlists, we are the controller of that data (name, email, Mercado Libre seller nickname, online store address, order volume and, in the application, current tool and what they want to solve; and, if they answer "How did you hear about Toldo?", their answer). It is covered by the toldo.io privacy notice (aviso de privacidad) at https://toldo.io/en/legal/privacy-notice-mexico, not by this policy; for people in Brazil, section 12 applies too. The site uses no cookies and stores nothing in the browser. It loads an external provider's script that counts visits in aggregate, and our server keeps only daily totals: visits per page, per referring site and per campaign; section 8 of the privacy notice explains this. Against form abuse it keeps a keyed hash of the sender's IP address, never the address itself, for 7 days.
12. Brazil (LGPD)
This section applies when Brazil's Lei Geral de Proteção de Dados Pessoais (LGPD, Lei 13.709/2018) governs the processing of your data. The rest of this policy applies too.
- Who decides about your data: LT3 LLC is the controlador (controller) of merchant-account data and of the data of people in Brazil who use the forms on https://toldo.io. For buyers' data, the merchant is the controlador and we are its operador (processor): we process that data only on the merchant's instructions.
- Purposes and legal bases (art. 7):
- running the app and your account, billing you, giving you support and assessing your application to the program: performance of a contract, or of steps you asked for before entering into one (art. 7, V);
- meeting our legal duties, such as accounting and tax: compliance with a legal obligation (art. 7, II);
- keeping the service secure, preventing abuse and fixing errors: our legitimate interest (art. 7, IX);
- sending you optional news about Toldo: your consent (art. 7, I). If you don't give it, we simply don't send it. You can revoke it at any time.
- International transfer (art. 33): we store data outside Brazil (section 6). We make this transfer as article 33 of the LGPD allows, with contractual safeguards in our contracts with our providers.
- Your rights (art. 18): you have the right to:
- confirm whether we process your data, and access it;
- correct incomplete, inaccurate or out-of-date data;
- ask for anonymisation, blocking or deletion of data that is unnecessary, excessive or processed in breach of the LGPD;
- ask for portability of your data to another provider;
- ask for deletion of the data we process with your consent;
- know which public and private entities we share your data with;
- revoke your consent;
- object to processing we do without your consent, if it breaches the LGPD.
- How to exercise them: write to privacidad@toldo.io. It's free. We answer within the LGPD's time limits: for example, a full statement confirming or giving access to your data within 15 days of your request (art. 19). If you are a buyer, write to the store you bought from first: it is the controlador, and we help it answer.
- Encarregado (DPO): Pending: [Data protection officer contact]
- Complaints: you can also file a petition with the Autoridade Nacional de Proteção de Dados (ANPD), https://www.gov.br/anpd.
13. Changes
We will announce material changes in the app and by email at least Pending: [Days of notice] days before they take effect.
14. Contact
LT3 LLC, 30 N Gould St Ste R, Sheridan, WY 82801, United States, privacidad@toldo.io.