Toldo privacy policy
Effective date: Pending: [Effective date]. Last updated: 2026-11-16.
This privacy policy covers Toldo's KSeF module in Poland. Toldo's privacy policy for every module: Privacy policy.
Some details in this document are still pending. They're marked like this: .
In this document
Toldo is a Shopify app that issues Polish VAT invoices from Shopify orders and sends them to KSeF, the national e-invoicing system of the Polish Ministry of Finance. It can also run your online store's search, with filters and sorting, sort the products in your collections and translate your store's content into the languages you choose, if you use those modules. This policy explains what personal data the app processes, why, who receives it, how long we keep it and what rights people have.
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
- For merchants' customers (buyers and visitors to its store): the merchant who installs Toldo decides why and how invoices are issued, 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 act as its processor under Article 28 GDPR. The data processing agreement is at https://app.toldo.io/legal/dpa.
- For merchant accounts: we are the controller of the data we need to run the merchant's account, billing and support.
3. What we process
| 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 invoice counts | Shopify, when you install the app |
| Seller details | Business name, NIP, address. Optionally: KRS, REGON and BDO numbers, bank account (IBAN), place of issue, 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 ever shown again; short-lived KSeF access tokens, stored encrypted; connection status and the last error | You, and KSeF |
| Buyer data | Name (company name or the person's name), billing address, NIP and company name entered in the cart | The order in Shopify, and the cart block (saved on the order as cart attributes) |
| Order data for the invoice | Order number and date, items (name, SKU, quantity, price, discount, VAT rate), shipping charges, currency, payment method and date, refunds | The order in Shopify |
| Invoice documents | Invoice XML (FA(3)), UPO (the official KSeF receipt), PDF, KSeF number, QR-code verification link, invoice history, and a random token for the document link stored on the order | Created by the app and KSeF |
| Search: 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 |
| Search: 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 |
| Search: order records and sales lines | 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; for each sale, per product: the units sold (refunded ones left out) and their amount. No buyer details. | Your orders in Shopify (those of the last 90 days, and new ones) |
| Search: counts per term | 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 |
| 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, memory and history | One record per text, language and market (who made its translation, whether it's locked, hashes of the original and of the translation, the engine, whether it needs review), without the text; the translation memory (the translation of each fragment already translated, identified by a hash of the original); recent runs, with their first failures (sometimes with an excerpt of the text of up to 60 characters); each month's usage; and the ids of items in your store that changed and are waiting to be translated | Created by the app and the translation engines from your store's content in Shopify |
| Support | Your name, email address and messages, if you contact us | 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 |
We don't request or store buyers' email addresses or phone numbers. We don't place advertising or analytics cookies, in the admin app or on your storefront. The cart block saves the NIP and company name in Shopify's cart, not in cookies of ours.
Search and translation data exist only if you use those modules. When your customers search, your online store sends our servers what they 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, 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, not in a third-party search service.
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.
4. Why we process it
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Issuing invoices, sending them to KSeF, storing documents and making corrections, on the merchant's instructions | Buyer data, order data, documents, seller details, KSeF connection | As processor: the merchant's instructions (Art. 28). For merchants, issuing invoices to business buyers is a legal duty under the Polish VAT Act (Art. 6(1)(c)). |
| Search, filters and sorting in your online store, search analytics and sorting your collections, on the merchant's instructions | The search data in section 3 | As processor: the merchant's instructions (Art. 28) |
| Translating the store's content into the languages the merchant chooses, on its instructions | The translation data in section 3, and the texts being translated | As processor: the merchant's instructions (Art. 28) |
| Running the app and the merchant's account; limits per plan | Store and account data, seller details | Contract (Art. 6(1)(b)) |
| Support | Support data, plus the minimum 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 issue and manage the merchant's invoices 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
- The Polish Ministry of Finance (KSeF). The app sends each invoice to KSeF in the merchant's name, using the merchant's own KSeF token. An invoice includes the buyer's name, address and NIP. Invoices sent to KSeF's production environment become tax records held by the tax administration under Polish law. They can't be deleted; mistakes are fixed with corrective invoices. The ministry processes this data as a controller under the law, not on our behalf. In Sandbox mode the app uses only the ministry's test system (KSeF TEST), which may receive fictional data only. Before sending, the app replaces seller and buyer details with fictional ones, and it sends only Shopify test orders there.
- Our hosting provider, which processes data on our behalf as a sub-processor: Render Services, Inc., servers in Virginia, United States.
- Narodowy Bank Polski (NBP). For orders in another currency, the app downloads the NBP average exchange rate from NBP's public API. Each request contains only a currency code and a date. NBP receives no personal data.
- Shopify. The order data comes from the merchant's Shopify store. The app writes the KSeF number and a signed document link to an app-owned field (metafield) on the order in that store. If you use translation, it also writes your store's translations to Shopify.
- Translation engines, only if you use the app's 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, your orders or your invoices. 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
- Data is stored in Virginia, United States.
- If a provider listed above processes data outside the EEA, we use 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.
7. How long we keep it
| Data | Retention |
|---|---|
| Seller details, settings, invoice documents and local invoice copies | While the app is installed. Before uninstalling, you can download every invoice in monthly ZIP files (XML, UPO, PDF). After uninstalling, we delete it as described in section 8. |
| Search's catalog copy, rules and settings; translation settings, records, memory, history and usage | While the app is installed. After uninstalling, we delete them as described in section 8. |
| Search's order records and sales lines | 120 days from the order's date |
| Search counts per term | 400 days (about 13 months) |
| KSeF token and KSeF access tokens | Until you disconnect or uninstall, then deleted at once |
| Invoices in KSeF | Kept by KSeF, not by us, for 10 years from the end of the year they were issued. You can download them at any time in 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): when a buyer asks a store for their data, we prepare a list of the invoices and documents we hold for that buyer's orders and send it to the store owner: a notice in the app with a download of the invoices concerned (ZIP). 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 unless the law requires it to be kept, and we delete search's records and sales lines of their orders.
- Invoices already accepted by KSeF stay in KSeF. Polish law requires them, and they can't be deleted.
- We record what we removed and what was kept and why, and we tell the store owner.
- Store erasure (
shop/redact, sent 48 hours after a store uninstalls the app): we delete all of that store's data, including the KSeF connection, seller details, 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.
- The KSeF token: encrypted with AES-256-GCM, using a key kept outside the database. It is never shown again after you save it; we display only its last 4 characters.
- Access: limited to Pending: [Who has production access] who need it. They use strong passwords and two-factor authentication, and access to customer data is logged.
- Test data: test and production data are kept apart. Sandbox mode uses fictional data only.
- 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, so the merchant can meet its own GDPR deadlines.
10. Your rights
- Everyone: you can ask for access to your data, correction, erasure, restriction, data portability, or object to processing based on legitimate interest. Write to privacidad@toldo.io. We reply within one month.
- 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. For example, an invoice that the law requires a business to keep can't be erased.
- Complaints: you can complain to a data protection authority. In Poland that is the Prezes Urzędu Ochrony Danych Osobowych (ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl). You can also complain in the EU country where you live or work.
11. Changes
We will announce material changes in the app and by email at least Pending: [Days of notice] days before they take effect.
12. Contact
LT3 LLC, 30 N Gould St Ste R, Sheridan, WY 82801, United States, privacidad@toldo.io.