MogDock holds your orders, your customers and your suppliers. Below is how that data is separated, encrypted, backed up and reached — described plainly enough that a marketplace reviewer or your own IT person can judge it.
Every tenant record carries an organization key, and the filter is applied where data is read — not by a screen that remembers to check. Cross-organization access is an explicit, greppable exception, not a default.
Sensitive values — integration credentials and API tokens among them — are encrypted at the application layer under a key belonging to your organization, wrapped by an envelope key that can be rotated.
TLS on every connection; encryption at rest on the database and on stored files.
The database is dumped on a schedule and the backup is stored encrypted. Restore procedures are exercised and verified; we do not claim point-in-time recovery.
Consequential actions are written to an audit trail you can read: who changed what, when. Billing and entitlement changes are recorded as events of their own.
Permissions are per capability, not per job title. A warehouse user who scans stock cannot read financial reports, and nobody gets admin by accident.
Our support staff cannot enter your account at will. Access is requested, shown to you in-app, granted by you, time-limited, and logged for the record.
Connectors request only the scopes needed to import orders. Marketplace-sourced personal data is retained no longer than each provider's developer policy permits and is deleted on their schedules, including required deletion endpoints.
A data-handling policy, a change-management process and an incident-response plan are maintained as documents and followed in practice. Available on request during review or procurement.
MogDock is built by Upstage Creations, a US manufacturer of teleprompters and AV hardware. It started life as the internal system running that company's own operation: orders arriving from several marketplaces at once, stock counted on a shelf, wholesale accounts with their own pricing, warranty claims against serials sold two years earlier.
Every module exists because something went wrong without it. The unmatched-payments queue exists because payments arrived that matched no order. The claim-cost tracking exists because warranty repairs were invisible in cost of goods. The reorder list exists because parts ran out between counts.
It is still the system that business runs on today. MogDock is the multi-tenant edition of it, opened up to other small product businesses — same codebase, your data in your own isolated organization.
Company: Upstage Creations · Product: MogDock · Support: support@mogdock.com · Privacy: privacy@mogdock.com
Write to support@mogdock.com and we will send the policy documents and a walkthrough of the integration scopes.