Legal
Privacy Policy
Last updated: 11 September 2026
Draft. This text accurately describes what the system does today, but it has not been reviewed by legal counsel. Review it before submitting it for Meta App Review.
TOPDABA helps a Shopify merchant choose which of their own product photos is used in their Meta product catalog, and keeps that catalog synchronized. This page states exactly what data passes through the service.
What we read from Shopify
The merchant installs an app on their store that grants exactly two
read-only permissions: read_products and read_inventory.
We hold no write permission on the store, and we never modify products,
images, inventory or any other store data.
| Data | Why |
|---|---|
| Products, variants, SKUs, titles, descriptions | Build the catalog feed |
| Product images and their URLs | Show the gallery so the merchant can choose one |
| Prices and compare-at prices | Price and sale price in the feed |
| Inventory quantity and policy | Availability in the feed |
| Store name, domain, currency | Show connection status in the panel |
We do not read customers, orders, payments or any personal data of the merchant's shoppers. The permissions we hold make that impossible.
What we access on Meta
With the merchant's authorization we use exactly one permission,
catalog_management, to attach and maintain the product feed inside
the catalog the merchant selects. We do not create the catalog: the merchant
chooses or creates it in Meta's own dialog.
Meta also grants public_profile automatically to every app and
it cannot be declined. We do not use it: we never read anyone's name or
profile picture.
We do not create, read or manage advertising campaigns, and we do not read advertising metrics. We hold no permission that would allow it.
Data we store ourselves
- The email address and a password hash (scrypt with a per-user salt) of each panel user. We never store the password itself.
- The image chosen for each product variant, and who chose it.
- Products the merchant excluded from the feed.
- Identifiers of the connected Meta Business, catalog and feed.
Access tokens are kept in Google Secret Manager, encrypted at rest, and are never sent to the browser.
Where it lives
On Google Cloud Platform, region us-east1 (United States).
Firestore for records, Secret Manager for credentials, Cloud Run for the
service.
Who else sees it
Nobody. We do not sell, rent or share this data with third parties, and we do not use it for advertising or profiling. The only outbound flow is the product feed that Meta downloads from us, which contains the merchant's own public catalog data.
The product feed is public
Meta's fetcher does not authenticate, so each merchant's feed URL is publicly reachable. It contains only catalog information that is already public on the merchant's storefront: titles, prices, availability, image links. No personal data.
Retention and deletion
Data is kept while the account is active. A merchant can request deletion at hello@topdaba.com and we remove their records, or use the instructions at /data-deletion. Disconnecting the app from Meta automatically deletes the stored Meta connection.