Privacy Policy

Last updated: October 29, 2026. This policy describes how New Customer Notifier (“we”, “the app”) handles information when you install and use the app on BigCommerce.

Who we are

New Customer Notifier is a BigCommerce application that emails addresses you choose whenever a new customer is created on your store (store/customer/created). The service is operated at https://notify.monkeybutler.dev.

Information we collect

Store identity — BigCommerce store hash and related account identifiers needed for OAuth, webhooks, and billing.
OAuth access token — encrypted at rest; used only to call BigCommerce APIs required for install, webhook registration, looking up new-customer details for the email (including store name when you enable that field), and uninstall cleanup.
Notification recipients — email addresses you enter in the app settings. Addresses that permanently fail at the mail provider (invalid or undeliverable) may be moved to a suppression list so we stop retrying them; you can add them again in settings to retry.
Email content choices — optional subject line (words and customer/store fields), and which details you include in the alert body: store name, customer profile link (BigCommerce admin URL for that customer), name, email, company, and customer id.
Webhook / job metadata — customer id, store hash, deduplication keys, and job status so we can send one email per new customer and retry safely. We do not retain full raw webhook payloads long-term.
Billing state — plan status, trial end, subscription identifiers used for BigCommerce billing, any scheduled cancellation date, and any staff-granted complimentary access window for your store.
Operational logs — request and error logs from our host (may include store hash, job ids, and non-secret status codes). Logs are used for reliability and support.

Operator-side mail settings (for example the From address and display name used to send notifications) are configured by us for the service as a whole; they are not merchant personal data you enter in the store settings screen.

How we use information

Deliver new-customer notification emails (and optional merchant-initiated test emails) to your configured recipients
Authenticate Load / Uninstall callbacks and keep your install working
Enforce trial, paid plan, and complimentary-access rules when billing enforcement is enabled
Respond to support and privacy requests you send via the Feedback tool

We do not sell merchant or customer data. We do not use store customer lists for our own marketing.

Processors / subprocessors

BigCommerce — platform OAuth, webhooks, and billing
Hosting / database — application hosting and database
Email provider — transactional mail via the configured provider (typically Resend; optionally Postmark or Amazon SES)
Feedback service — optional in-app Feedback overlay / inbox

Those providers process data only as needed to run the service under their own terms.

Retention and deletion

While the app is installed we retain store settings, encrypted tokens, job and deduplication records, and any suppressed recipient addresses needed to operate notifications. On uninstall we delete the store row and related settings and jobs, clear deduplication records for that store, clear the app session cookie when possible, and remove our webhook destination from the store when the BigCommerce API still accepts our token.

We keep a minimal billing record after uninstall (store identifier, plan status, trial end date, any complimentary-access end date, and the BigCommerce subscription identifier and cancellation date). It contains no access tokens, recipients or settings. We keep it so a reinstall continues your existing trial, credit, or paid subscription instead of starting over or billing you twice. If a paid subscription is still active when you uninstall, we may email your notification recipients once to let them know billing continues. Ask us via Feedback to delete this record.

Email provider and host logs may retain limited metadata for a short operational window after uninstall. For privacy or deletion requests, use the in-app Feedback tool; we respond within 5 business days.

Security

Access tokens are encrypted at rest. Sessions use signed HTTP-only cookies. Mutating settings requests require a matching browser origin. Webhook requests are signature-verified. Transmission uses HTTPS. Staff operations panels (when enabled) require a separate high-entropy operator token and are not framed inside BigCommerce.

Feedback tool

Our apps may include an optional Feedback overlay (same feedback service used across our products). You choose when to use it; it is not always-on recording.

A screenshot is optional. We do not capture the screen unless you choose Add a screenshot.
If you add one, it stays on your device while you compose. We upload it only if you tap Send.
If you cancel, nothing is uploaded.
Submissions may include your note, annotation marks, page URL, basic device/browser context, and optional store identifiers from this app. When Feedback posts through this app, we attach the store hash from your signed session (merchants cannot override that identifier).
Replies appear in the Feedback Messages view on the same browser that sent the feedback.

Children

The app is for business use on BigCommerce stores and is not directed at children.

Changes

We may update this policy when product or legal requirements change. Material changes will be reflected on this page; continued use after posting constitutes notice for marketplace purposes.