1. Who we are
InventoryOS provides inventory, sales, expenses, barcode, dispatch and printing tools for resellers, Manufacturing mode for small manufacturers, and a separate InventoryOS Retail service for shops and service businesses. For this policy, “InventoryOS”, “we”, “us” and “our” means the InventoryOS service.
Dylan Smith trading as InventoryOS
Business and returns address: 6 New Hall Avenue, Manchester, M30 7LE, United Kingdom.
Email: hello@inventoryos.co.uk.
2. Personal data and business data we collect
Account dataName, email address, password hash, verification status, admin/suspension status and account timestamps.
Inventory dataProducts, descriptions, barcodes, active stock quantities, boxes, shelves, locations, movements and workspace settings.
Sales and recordsSales, refunds, expenses, receipts, corrections, revenue, profit and dashboard figures entered into InventoryOS.
Uploaded filesReceipt images, PDFs, shipping labels, cropped label files and other files uploaded to use the service.
Shipping-label email dataEmails and attachments you send or forward to your workspace shipping-label address, email subject and processing history, attachment hashes used to prevent duplicates, and cropped label files.
Printing dataPrinter preferences, label previews, print requests and QZ Tray signing information needed to send labels to supported printers.
Billing dataPlan, subscription status, Stripe customer/subscription IDs and billing events. InventoryOS does not store full card details.
Technical dataIP address, browser/device information, login events, error logs and last-seen activity used to secure and operate the service.
3. How we use data
- To create and manage your InventoryOS account and workspace.
- To provide inventory, stock movement, sales, refunds, expenses, barcode, dispatch and printing features.
- To receive and process shipping-label attachments you choose to send to your workspace address.
- To process subscriptions, billing states and plan access through Stripe.
- To provide support, investigate bugs, prevent abuse and keep the service secure.
- To improve InventoryOS using aggregated or operational usage information.
4. Shipping-label email import
Pro and Business workspaces can use a shared InventoryOS email address to receive shipping-label emails and attachments. You choose which emails to forward, either manually or using your email provider’s forwarding rules. InventoryOS does not connect to, search, read or change your mailbox.
Resend receives forwarded emails and makes them available for processing. InventoryOS downloads supported attachments, crops shipping labels and adds them to your workspace’s Dispatch Centre. Shipping labels may contain names, addresses, tracking references and other personal information about recipients. Forward only the information needed for dispatch.
InventoryOS stores cropped labels, email subjects, processing history and attachment hashes for this workflow. Verified forwarding-confirmation text may be shown to the workspace owner or admin to complete setup, and is removed from InventoryOS after seven days. Temporary local originals are removed after processing; received emails and attachments may also be retained by Resend under its service retention arrangements. Workspace members with access to Dispatch Centre can view the shared queue. We do not sell this information or use it for advertising.
Downgrading locks future imports but retains the address and existing labels. Upgrading can reactivate the address. Regenerating the address disables the old address; you must update forwarding rules. To stop forwarding entirely, remove those rules in your email provider. Contact us for help with data deletion.
5. Lawful basis
We normally process data because it is necessary to provide the service you request, to comply with legal obligations, or because we have a legitimate interest in operating, securing and improving InventoryOS. For optional InventoryOS marketing emails, we rely on your separate opt-in consent, which you can withdraw. Marketing consent is not a condition of creating an account. Contract and legitimate interests support necessary account, security, support and requested service messages; legal obligations can require us to keep certain billing records.
6. Who data is shared with
We only share data where needed to run InventoryOS, provide integrations, or meet legal requirements.
- Stripe for subscription checkout, billing and payment status.
- Resend to receive forwarded shipping-label emails and attachments and to send service emails.
- Cloudflare for website delivery, routing, security and website visit/performance analytics. The public site includes Cloudflare’s Web Analytics beacon. See our Cookie Policy and Cloudflare’s analytics information. Database, storage and other infrastructure services are also used to operate InventoryOS.
- Legal or regulatory bodies where required by law.
InventoryOS is not affiliated with Vinted, eBay, Meta, Amazon, Google or Stripe unless specifically stated.
7. Storage, retention and deletion
We keep account and workspace data for as long as your account is active or as needed to provide the service. Uploaded files, inventory history, sales records and billing records may be kept after cancellation where needed for account recovery, legal, tax, security or dispute reasons.
You can request deletion of your account and associated workspace data by emailing hello@inventoryos.co.uk. Some records may be retained where we are legally required or have a legitimate reason to keep them.
8. Your rights
Depending on your circumstances, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data. Contact us at hello@inventoryos.co.uk to make a request.
You also have the right to complain to the UK Information Commissioner’s Office if you are unhappy with how your data is handled.
9. Security
We use measures such as HTTPS, password hashing, access controls, protected upload routes, workspace permissions and secret-key separation to protect your data. No system is completely risk-free, so you should use a strong password and keep your login details private.
10. Retail, manufacturing and support records
Manufacturing records include materials and measurements, recipes, source and finished batches, expiry and recall status, equipment usage, maintenance history and saved timer deadlines.
Retail records include business and shop display names, product and service catalogues, suppliers, prices and costs, stock events, sales, receipts, returns, cash movements, counts, wastage, staff assignments and management approvals. Staff numbers and protected PIN credentials are used for till access; private PINs are not printed on staff QR cards or receipts. The cashier’s number can appear on receipts and sale records.
If a shop uses customer tools, its records may include customer names and contact details, loyalty identifiers and QR cards, purchase history, bookings, preorders, collections and deposits. Customer email receipt requests include the recipient email address, sale information, delivery state and billable sending usage. Resend delivers these transactional receipts using the shop display name and a configured verified sending address. Receiving a shop receipt does not subscribe the customer to InventoryOS marketing.
Help requests record the signed-in account email, selected workspace, topic, message, timestamps and support status. They are available to authorised support administrators and are also sent to the support email inbox. Archiving a request marks it complete; it does not itself delete it.
11. Optional marketing and service emails
When you choose the mailing-list opt-in, we record your choice and may use your account email to send product updates, feature announcements, feedback requests and relevant offers about InventoryOS. You can ask to be removed by emailing hello@inventoryos.co.uk or use an unsubscribe option where supplied. We keep enough preference information to honour an opt-out.
We do not sell or give your mailing-list details to unrelated organisations for their own marketing. Service providers such as Resend may process them on our behalf to deliver our emails. Necessary account verification, password reset, billing, support, receipt and requested operational reminder messages are separate from optional marketing.
12. When you upload other people’s information
The business operating a workspace or Retail shop is responsible for the customer, employee, supplier and recipient information it chooses to enter. It should provide its own privacy information, identify an appropriate lawful basis, restrict staff access and respond to requests concerning its business records. InventoryOS processes those workspace records to provide the service to that business. Contact us about data-processing arrangements or assistance with a request.
We are responsible for our own account administration, subscription, security, support and optional InventoryOS marketing activities. Do not upload unnecessary sensitive information, payment-card security codes or passwords belonging to customers or suppliers.
13. Local copies, store deletion and exports
Retail PWAs may keep operational snapshots and pending cash sales in browser storage on the device used. Unsynced data stays on that device until a successful sync; clearing site data or losing the device can remove that copy. Use device access controls and shared-device sign-out or till locking.
Store deletion is a separate owner-controlled action. Its workflow requires an emailed CSV backup and confirmation before permanent deletion. The backup is sent to the verified account login email and can contain customer, sales and other business records. Products have their own CSV; login credentials and staff PINs are excluded. Keep emailed exports secure and sync every device before deleting a store. Your account, other shops and shared staff are not deleted by deleting one store.
Subscription cancellation alone does not delete business records. Some billing, security, legal and deletion-audit information may need to remain after operational data is removed. Provider-held email copies, delivered attachments and your own exports are not erased by deleting an app record.
14. Provider locations and transfers
Our email, payment, delivery and infrastructure providers may process information outside the UK. UK data protection requirements apply to those transfers. Contact hello@inventoryos.co.uk for details of the relevant providers, processing locations and applicable transfer arrangements.
We do not use solely automated decisions about people that produce legal or similarly significant effects. Stock alerts, price suggestions and production calculations are operational aids that users review.
15. InventoryOS Shop orders
For hardware orders we collect the customer name, email, billing and delivery addresses, chosen product and colour, order amount, payment references, invoice, order status, tracking reference and support correspondence. Stripe handles payment details; we do not store full card details. An InventoryOS account or subscription is not required to buy hardware.
We use these records to fulfil your purchase, send confirmations, invoices and tracking updates through Resend, deal with returns and meet tax and legal obligations. We share the delivery name and address with the delivery carrier, normally Royal Mail. Authorised Shop administrators can access orders. We retain necessary accounting and order records for applicable legal periods and to handle disputes. A purchase alone does not subscribe you to marketing. If you separately choose email updates on the Shop, we record the wording, time and email you provided. We activate this choice only after a paid order using that email. Unfinished choices expire after 24 hours. You can withdraw consent at any time by emailing hello@inventoryos.co.uk or using the unsubscribe option in a marketing email. We keep consent and withdrawal records to honour your choice. Existing InventoryOS account preferences also apply.
16. Changes to this policy
We may update this policy as InventoryOS changes. The latest version will be available on this page with the updated date shown above.