Your data
Where your data lives
Your Puter account holds the records; this page explains what is stored, where, and what leaves the device.
On this page
Everything is stored in your own account
Inventory has no server of its own. Products, families, locations, suppliers, orders, activity, saved counts, daily snapshots, and your settings are all written to your Puter account’s key-value storage. Product photos go to your Puter drive, under an inventory/images folder, and the product record keeps only the path to the file.
Because the data is yours, signing in on another device shows the same inventory, and there is no separate account to create, no seat to buy, and nothing to migrate if you stop using the app: export CSV or download a JSON backup at any time.
What this device keeps
The built app also keeps a local mirror of the data it last saw, and a queue of writes made while the connection was gone, in the browser’s own storage. That is what lets a stockroom with no signal keep working. The mirror is a convenience; your account is the record.
The mirror is bound to the account that created it. Signing in as someone else on a shared browser clears it before reading anything, and signing out clears it too. If the browser refuses local storage entirely, the session simply keeps that state in memory instead and carries on.
Photos, and why the files stay small
A photo you attach is shrunk to 800 pixels on its longest side and re-encoded in the browser before it is uploaded, which turns a phone photo into tens of kilobytes. That is what makes thumbnails in a long list workable at all.
A JSON backup carries the reference to a photo rather than the image itself, so keep your own copies of any pictures that matter independently. Photos are best effort throughout: a picture that will not upload never blocks the product from saving.
What leaves your device
Traffic goes to Puter to read and write your data, and the app loads the Puter SDK and its own files. Nothing about your inventory is sent anywhere else, and the public documentation and guides you are reading now load without a session and without contacting the app’s storage.
Exports and backups are produced in the browser and downloaded straight to your device; they are not uploaded anywhere first.