1. Overview
InventoryOS is designed to store operational business data such as inventory, stock locations, sales, expenses, receipts and shipping-label files. This page summarises how those areas are handled.
Last updated: 10 July 2026
Data & Security
InventoryOS stores business-critical inventory, sales, receipt, label and integration data. This page explains what is stored and the protections used.
2. What is stored
InventoryProducts, barcodes, quantities, locations, movement history and workspace settings.
Sales and finance recordsSales, refunds, expenses, receipt uploads, corrections, revenue and profit calculations.
Uploaded filesReceipts, shipping labels, PDFs, image files and generated/cropped label outputs.
IntegrationsWorkspace shipping-label addresses, received label attachments and import metadata, QZ printing preferences and signing requests.
BillingPlan, status, Stripe IDs and subscription events. Full card details are handled by Stripe.
Account securityPassword hashes, verification state, login timestamps, admin/suspension flags and last-seen activity.
3. Security measures
- HTTPS is used for app and API traffic.
- Passwords are stored as hashes rather than plain text.
- Private uploads are intended to be protected by authenticated routes.
- Workspace permissions limit what users can access.
- Admin tools are restricted to authorised admin accounts.
- QZ private keys and app secrets should be stored outside public folders and not committed to source control.
4. Admin and support access
Authorised InventoryOS admins may access account, workspace, plan, billing-status and usage information to provide support, investigate bugs, manage beta testers, apply complimentary plan overrides, handle abuse and keep the service secure.
5. Shipping-label email import
Workspace shipping-label addresses are random and shared only with authorised workspace members. Keep the address private and forward shipping labels only. Resend receives forwarded emails; InventoryOS verifies signed webhook events before processing attachments.
The backend checks the current workspace subscription before receiving and importing labels. Free and Starter cannot use inbound import. Downgrading locks the saved address. Regenerating it disables the old address. Attachment hashes prevent repeated imports within a workspace.
Supported attachments use the existing carrier detection and cropping workflow. Temporary originals are removed after processing. Labels enter the review queue and do not automatically print or remove stock. The integration does not request mailbox permissions.
6. Storage and retention
Operational records and uploaded files are kept while your account is active and for a reasonable period afterwards for recovery, audit, security, legal, support or dispute reasons. You can request deletion by contacting [email protected].
7. Your responsibility
You are responsible for keeping your password secure, checking that your business records are accurate, only uploading files you are allowed to process, and exporting any records you need before deleting your account.