Privacy Policy

What Catalog Health stores

Effective Oct 28, 2026. This page describes the current Catalog Health application operated by Bez Leda Studios. If the product changes, we update this page.

Who we are

Bez Leda Studios provides Bez Leda Catalog Health (“the app”) at cataloghealth.bezledastudios.com. Contact: cataloghealth@bezledastudios.com.

What the app is for

The app audits BigCommerce catalog quality for stores that install it. It is not a payment processor, CRM, or customer-data platform. Card charges for Pro, Growth, and Business go through BigCommerce Unified Billing, not through us.

Data we store

For each installed store we keep only what the product needs:

• Store identity. Store hash, optional account UUID, name, domain, secure URL, timezone, currency, install status, plan, complimentary override fields, and scan timestamps.
• OAuth users. BigCommerce user id, name, email, locale, and the store–user link (including owner flag and last seen).
• Access token. The BigCommerce store token, encrypted at rest with the application key. Hidden from logs and API serialization.
• Optional AI key. A merchant-supplied OpenAI key, encrypted the same way. Used only for that store’s suggestion generation. We do not use another store’s key.
• Catalog copies. Product, variant, brand, and category fields needed to score health (names, SKUs, descriptions, prices, inventory flags, image counts, SEO fields, category/brand links). We do not store customer records, order contents, payment methods, or checkout data.
• Health records. Scans, issues, ignored issues, health scores, rule settings, and catalog standards.
• Tools. Export file metadata and generated CSVs, bulk-fix previews/results, and AI suggestions the merchant asked to generate.
• Monitoring. Notification preferences, email address for alerts, and dispatch history (including a held state when email delivery is not configured).
• Billing copies. Local subscription rows (plan, status, BigCommerce subscription/checkout ids, period dates). We do not store card numbers. BigCommerce invoices the merchant.
• Operations. Webhook event payloads used for catalog updates, audit log actions, and failed-job text in the application database.
• Owner admin. A separate admin session flag. Admin credentials live in environment configuration, not in merchant store rows.

What we do not collect

• Shopper personal data, customer lists, or order history
• Payment card data
• Marketing pixels or third-party advertising trackers on these public pages
• Testimonials or case-study content about your store

How we use it

We use store data to sync the catalog, score products, show the merchant dashboard, send opted-in operational email, create BigCommerce checkouts the merchant starts, and operate the app. Encrypted tokens are used only to call BigCommerce APIs for that store. AI keys are sent only to the configured provider when that store generates a suggestion.

Uninstall and retention

When BigCommerce sends the uninstall callback we:

1. Mark the store uninstalled and stop scans, webhooks we still hold, and merchant sessions for that store.
2. Clear the BigCommerce access token and any stored OpenAI key immediately. We cannot keep using those secrets after uninstall.
3. Best-effort delete webhook registrations we created. BigCommerce also removes platform webhooks for the app.
4. Keep the remaining store records (catalog copies, issues, scores, users, billing copies, audit entries) for 30 days so a reinstall can pick up the same store hash without starting from nothing.
5. After that window, a scheduled job permanently deletes the store row and cascaded store-scoped records, plus export files on disk. Webhook events and audit rows for that store are deleted in the same pass. A user account is deleted only if it is no longer linked to any store.

We do not claim that uninstall wipes every copy instantly. Nightly PostgreSQL dumps can retain a snapshot for up to 3 days, then they rotate. Those dumps are on the application server, not an off-box archive. Email us if you want the remaining live copy purged before the 30-day window ends. We will run that purge; we cannot promise a backup that has not yet rotated is already gone.

Uninstall does not cancel a BigCommerce Unified Billing subscription by itself. Cancel paid plans in Settings → Subscription before or after you uninstall, or manage them in the BigCommerce invoice.

Remove user

If a store owner revokes a user’s app access, we delete that user’s link to the store. We do not delete the store’s catalog data.

Sharing

We do not sell store data. We share it only with:

• BigCommerce, when the merchant installs, loads, or asks us to write catalog fields they confirmed
• The AI provider the merchant configured, only for that store’s generate request
• The hosting and email operators that run this application, under their processing terms
• Authorities if required by law

Cookies and sessions

The merchant app uses a session cookie after BigCommerce load. Public help and legal pages do not require a login cookie. We do not use advertising cookies.

Requests

Email cataloghealth@bezledastudios.com with your store hash to ask what we hold, to request an earlier purge after uninstall, or to correct a user email we stored from BigCommerce. There is no self-serve “download everything” portal. Issue CSV export exists for entitled stores inside the app and is not a full personal-data export.