Privacy at MakerBatch

What MakerBatch does

MakerBatch connects supplies, product recipes, variants, orders, incoming supplies, and production steps so sellers can plan work, understand material availability, and keep custom-order details together.

Information you provide

Depending on the features you use, MakerBatch may store:

• Your account name and email address.
• Open-beta acknowledgment timestamp and notice version for accounts created during the open beta.
• Supply quantities, costs, vendor details, recipes, variants, SKUs, and production checklists.
• Order details, customer and personalization notes, statuses, due dates, work-ticket information, and any artwork, reference images, or proof files you upload.
• Incoming supply orders, receiving records, and inventory movements.
• Feedback reports, beta requests, and the contact information you choose to include with them.

Optional Etsy order import

The Etsy integration is optional. Order importing uses read-only shop, transaction, listing, and shipping-address access. MakerBatch also requests narrow transaction-write access so Pro users can deliberately send carrier, tracking number, and shipment date for a finished order. If you connect a shop, MakerBatch uses Etsy OAuth and never asks for your Etsy password.

When you manually import orders or opt in to automatic importing, MakerBatch may store the Etsy shop, receipt and transaction identifiers; recipient name; shipping-address fields Etsy returns; order and expected-ship dates; item titles, quantities, SKUs, variations, personalization; buyer and gift messages; order total and currency; and recipe-mapping results needed for production. MakerBatch does not request or store buyer email, billing address, payment method, card data, or raw Etsy receipt responses.

Authorization tokens remain encrypted and are excluded from business-data exports. MakerBatch does not edit Etsy listings or inventory, message buyers, or create Etsy webhooks. Scheduled Etsy checks run only after you explicitly enable Automatic Order Import. A shipment update occurs only when you choose the Etsy option while marking a finished order shipped; Etsy sends its own buyer notification after a successful update.

Optional Shopify order import

The Shopify integration is optional. Order importing uses read-only order and product access. MakerBatch can also request merchant-managed fulfillment access so Pro users can deliberately send carrier and tracking details for a finished order. If you connect a store, MakerBatch uses Shopify OAuth and never asks for your Shopify password.

Manual previews return minimized order, recipient destination, item, SKU, option, personalization, and mapping details. Selected imports may store the Shopify order, product, variant, and line-item identifiers; recipient and shipping-address fields; order status and dates; item titles, quantities, SKUs, personalization; order total and currency; and recipe-mapping results needed for production. MakerBatch does not import billing addresses, payment methods, card data, buyer email, or raw Shopify responses.

Shopify access and refresh tokens are encrypted and excluded from exports. MakerBatch does not write inventory, refunds, or order contents back to Shopify and does not register Shopify webhooks. Scheduled Shopify checks run only after you explicitly enable Automatic Order Import. A fulfillment is created only when you choose the Shopify option while marking a finished order shipped.

How information is used

We use this information to operate MakerBatch, calculate material availability, show production and order status, build reorder guidance, respond to feedback and historical beta requests, deliver transactional account emails, keep the service secure, and improve the product.

First-party analytics and attribution

MakerBatch uses random first-party visitor and session identifiers on public pages to understand how people find the service and whether those visits lead to signup, onboarding, useful product milestones, and paid subscriptions. The identifiers are not browser fingerprints and do not contain your email address, password, or raw IP address.

For this purpose, MakerBatch may store the landing-page path, referring site and path, recognized UTM source, medium, campaign, content, and term values, and a limited set of product-usage milestones such as signup, onboarding completion, activation, and subscription status changes. URL query values other than recognized UTM fields are not stored for attribution. MakerBatch does not record mouse movement or the contents of orders, recipes, customer messages, or private notes in analytics events.

The public-page tracker uses an HTTP-only visitor cookie for up to one year and an HTTP-only session cookie for 30 minutes. It honors a browser Do Not Track value of 1 by not recording the public-page visit. Account, security, billing, and operational records that are necessary to provide MakerBatch are still processed independently of that browser preference.

If you create an account, MakerBatch may associate the random visitor record with your account so first-touch and last-touch acquisition sources can be compared with later product and subscription outcomes. This analytics remains inside MakerBatch. No third-party advertising pixel or external behavioral analytics provider is used by this implementation.

Subscription and billing analytics

Stripe handles payment methods, card details, billing addresses, invoices, and subscription payment collection. MakerBatch stores the Stripe customer, subscription, invoice, payment, and refund identifiers needed to reconcile verified webhook notices with the correct account. MakerBatch also stores subscription amounts in minor currency units, currency, payment or refund outcome, and effective time so administrators can measure collected subscription revenue, refunds, customer acquisition cost, and attribution. MakerBatch does not place card numbers, payment credentials, or billing addresses into marketing analytics.

We do not sell your business data

MakerBatch does not sell your account, shop, order, supply, recipe, or production data.

Storage and safeguards

MakerBatch stores data and uploaded order files with its production hosting and service providers. We use reasonable technical and organizational safeguards designed for the open beta, including signed-in access controls, user-scoped business records, and private file routes. No online service can promise perfect security.

If you create a customer link, anyone who receives it can upload artwork or reference files and view only the proof files and order details prepared for that review until the link expires or is replaced. Do not send the link to anyone who should not see or add files to the order.

Transactional emails

MakerBatch sends service emails needed to create and verify accounts and may send operational messages related to support or beta access. These are not promotional mailing-list messages.

Exports and deletion requests

Business-data backups include attachment and proof-approval metadata, but uploaded file bytes are not embedded in the JSON download.

Signed-in users can download supported business records from Settings → Data export. Read the public data deletion instructions to request account or workspace deletion. We verify that the request comes from the account owner before completing it.

Open beta changes

MakerBatch is in open beta, so features and this privacy notice may evolve. Material changes will be reflected on this page with an updated date.