Security

Security is a practice, not a one-time checklist. This page describes the choices we have made so far.

Payments

Customers pay stores directly today, so BatchDrop handles no customer card data at all. Store owners' subscription cards are collected and stored by Stripe and never reach BatchDrop's servers. We act on billing events through signed webhooks, and every webhook's signature is verified before we change an account's state.

Passwords

Passwords are stored as one-way hashes. We never store them in a form we could read back.

Customer sign-in

Buyers sign in with a one-time code sent by SMS rather than a password, so there is no password for a buyer account to have stolen.

Transport

This website is served over HTTPS.

Data isolation

Each store's customers, drops, and orders are scoped to that store. One store cannot see or reach another store's data.

Consent enforcement

SMS broadcast eligibility is checked again at the moment a message actually sends, not just when it was queued, so if someone replies STOP between scheduling and sending, they will not receive that message.

Reporting a vulnerability

Email support@batchdrop.io with details of what you found. We will acknowledge your report and keep you informed as we work on it. Please give us a reasonable window to fix an issue before disclosing it publicly, and do not test against real stores or real customer data.