Tidro Privacy Policy
Effective date: the date this policy is first published with the Tidro Sync listing on the Shopify App Store.
Tidro ("we", "us") makes Shopify apps for merchants who run more than one store. This policy covers every Tidroapp (each "the App"). It explains what data the App collects when a merchant installs it, why, how long we keep it, and how merchants and their customers can exercise their privacy rights.
Today one Tidro app is available: Tidro Sync, which keeps stock levels, and optionally product information, in sync between Shopify stores owned by the same merchant. Sections 1 to 6 describe what Tidro Sync processes. Before any other Tidro app (such as Tidro Pixel, Tidro AI or Tidro POD) becomes available, we will add what it collects to this policy.
Tidro apps are used by merchants (businesses running Shopify stores). For data about a merchant's customers that the App receives through Shopify, the merchant is the controller and we act as a processor on the merchant's behalf, under our Data Processing Addendum.
1. Data we collect
We only collect data through the Shopify APIs, using the permissions the merchant approves at install. We do not use cookies or trackers in the App, and we do not collect data from store visitors.
Store and account data
- The store's Shopify domain (for example example.myshopify.com), install and uninstall dates, the permissions (access scopes) granted, and the time we last received an update from the store.
- Shopify access tokens and refresh tokens. They are encrypted at rest with AES-256-GCM and are never written to logs. They are deleted as soon as the App is uninstalled.
- Pool settings the merchant enters: pool name, matching and safety settings, location mappings, buffers, and an optional alert email address used only to send sync alerts.
- When a staff member opens the App, Shopify sends a short-lived session token that identifies the store and the staff user. We use it only to authenticate the request and do not store the staff user's identity.
Catalog and inventory data
- For each product variant: product and variant IDs, product and variant titles, SKU, barcode, inventory item ID and whether inventory is tracked.
- Location IDs and names.
- Available quantities per item and location, the shared (pooled) quantity, and a history of each stock change: time, store, cause (order, manual edit, reconcile, restore, etc.), quantity before and after, and status.
- Snapshots of quantities taken before bulk changes, so they can be restored.
Order data (without customer information)
- When an order is created, cancelled or refunded, we keep only the order ID and order number, the variant IDs and quantities of its line items, and restock flags. We use this solely to explain stock changes (for example "Order #1004") and to recognise restocks.
- We do not store customer names, email addresses, phone numbers, postal addresses, payment details or any other customer profile data. Order webhooks are reduced to the fields above before they are saved.
Product sync data (only if the merchant turns product sync on)
- Product information from the chosen source store needed to copy it to the other stores: titles, descriptions, images (by URL), vendor, product type, tags, options and variants, SKUs, barcodes, weights, prices, compare-at prices and costs, selected metafields, collection membership and status.
- Links between each source product and its copies, a fingerprint (hash) of the values written, and the previous values of every field we change (so the change can be undone).
Technical data
- Server logs with the store domain, request paths, timestamps and error messages, used for security and troubleshooting. Our hosting provider may process IP addresses of incoming requests as part of operating the network.
2. How we use data
We use the data above only to:
- provide the App's features: match items across stores, keep stock (and, if enabled, products) in sync, hold suspicious changes for review, take snapshots and restore them, show history and the health dashboard, and send alerts;
- apply plan limits (number of shared items and stores);
- secure, operate, debug and support the App.
We do not sell data, share it for advertising, build customer profiles, or make automated decisions about the merchant's customers. We do not use store data to train machine-learning models.
3. Sharing
Data stored for one store is shown only to stores in the same pool, and only to the extent needed for syncing (for example SKUs, quantities, store domains, location names and change history). Stores join a pool only by entering the pool's connect code, so the merchant controls which stores share data.
We share data with service providers that run the App for us (hosting and database, email delivery) under contracts that require them to protect it and use it only to provide their service. We disclose data if the law requires it. If the App is sold or transferred, this policy continues to apply to the data.
4. Where data is stored and how it is protected
- All traffic between Shopify, the App and the merchant's browser is encrypted with TLS.
- Data is stored in a managed PostgreSQL database whose storage is encrypted at rest. Access tokens are additionally encrypted by the App.
- Each store's data is separated by store and pool in every query. Access to production systems is limited to the people who operate the App.
- Data may be processed outside the merchant's country. Where required, transfers rely on appropriate safeguards such as the EU Standard Contractual Clauses.
5. Retention
- History and before-values of changes are kept for the history period of the pool's plan (30, 90 or 365 days) and then deleted. Snapshots are kept for 30 days (the latest snapshot of each pool is always kept so it can be restored).
- Raw update records (reduced webhook data) are deleted 7 days after they are processed; order references used for attribution are deleted after 30 days.
- Uninstall: access tokens are deleted immediately and syncing for that store stops. All remaining data for the store is deleted when Shopify sends the shop/redact request (48 hours after uninstall), or at the latest 30 days after uninstall.
- Leaving a pool: the store's data stops being shared with the pool. Shared stock totals and pool history that don't identify the store's customers may remain with the pool owner until they expire under the plan's history period.
- Backups are kept for a limited period (no more than 30 days) and then overwritten.
6. Privacy requests (GDPR, CCPA and similar laws)
Shopify forwards privacy requests to each Tidro app through its mandatory compliance webhooks, and we handle them as follows:
- customers/data_request (a customer asks a merchant for their data): the App stores no customer personal data, so there is nothing to export. We confirm receipt. Order numbers kept for attribution, if any, are available to the merchant in the App's History page.
- customers/redact (a merchant asks to erase a customer's data): the App stores no customer personal data. Any order references for the listed orders are removed within 30 days.
- shop/redact (sent 48 hours after a merchant uninstalls the App): we delete all data stored for that store within 30 days, normally immediately.
Merchants can also contact us directly to access, correct, export or delete their store's data, or to ask questions about this policy. Customers of a store should contact the merchant first; we will help the merchant respond. We answer requests within 30 days.
7. Children
Tidro apps are business tools for merchants and are not directed at children.
8. Changes
We may update this policy when a Tidro app or the law changes. We will post the new version at the same address with a new effective date, and notify merchants in the App or by email for material changes.
9. Contact
For privacy questions or requests, email support@tidroapps.com.