Last updated 29 September 2026
This deployment of Mavericks Commerce is hosted and operated by Mavericks Commerce ("the operator"). This policy describes what the service stores for each business that uses it, who can see it, and for how long. Each business decides what it enters about its own customers and staff; the operator keeps the systems that hold it.
The business itself: its name, address, phone, email, tax rate, timezone, logo and settings. Its staff: each person's name, email address, role, permissions, a hash of their password (never the password), and the times they sign in.
Its customers: names, business names, contact details, tax identifiers and tax-exemption certificates, price lists and per-customer prices, credit terms and balances — and, for a customer the business invites to its portal, that person's email address and a hash of their password.
Its records: products and stock movements, register tickets, invoices, quotes and sales orders, purchase orders, vendor returns, counts, payments, uploaded product pictures, a copy of every email the service sent on the business's behalf, and an audit log of sensitive actions naming who did what and when.
Every one of those records is scoped to the business that created it. No business can read another's, and nothing in the service aggregates data across businesses.
The service runs as a single instance on infrastructure the operator rents or owns. The hosting vendors and sub-processors involved are the company hosting the machine and its storage, the mail relay that delivers the messages a business sends (receipts, invoices, invitations, password resets), and the storage that holds the nightly backups. Each sees only what it needs to do its job, under its own terms with the operator; the operator keeps the current list and shares it with a business's owner on request.
A business's records are kept for as long as the business is active, and after it is closed until the operator and the business agree otherwise. Closing a business deactivates access and deletes nothing. The audit log is never pruned: it is the record of who changed what, and it survives every other change to the business.
The operator takes a backup of the database and the uploaded pictures every night and keeps a fixed number of recent copies. Backups exist to restore the whole service after a failure; they are not a way to recover a single record on request, and a record deleted or changed in the service persists in the backups until those copies age out.
The operator can read the database and the backups in order to run the service: to set a business up, to answer a support request, to restore after a failure, and to check that the system is healthy. The operator does not use a business's records for any other purpose, does not sell them, and hands a copy of them to nobody but the business's own owner — and then only through the exports the product itself offers, never as a copy of the shared database.
A customer whose business has invited them to the portal sees their own prices, sales orders, invoices and statement — the records the business keeps about them, presented back to them. The business, not the operator, decides who is invited and what they can see; questions about those records go to the business first. Portal sign-ins are kept apart from staff sign-ins: a portal account can never reach a business's staff screens.
Passwords are stored only as salted hashes. Sign-in attempts are rate-limited, and password-reset and invitation links work once and expire. A changed password ends every other session on that account.
Sign-in attempts are counted to slow password guessing: the counts are keyed on a one-way hash of the email address or of the link, and on the client's network address only when a trusted proxy supplies it; no password is kept with them, and old counts are removed as new attempts arrive.
Questions about this policy, and requests about the data held for you, go to sahilsohani16@gmail.com.