Your data
Export, offline behavior, switching servers, and self-hosting.
Where your inventory lives, how to get a copy of it, and what is visible from our side.
Exporting to CSV#
Under Settings → Export the mobile app offers Export Items as CSV and Export Bins as CSV, which hand the file to the usual share sheet. The web dashboard has the same two exports on your account page, and individual bins can also be exported from the bin itself.
The columns are the same wherever the file came from:
| Export | Columns |
|---|---|
| Items | Name, Description, Quantity, Min Quantity, Barcode, Tags, Bin, Room, Location |
| Bins | Name, Description, Room, Location, Item Count |
Files lead with a UTF-8 byte-order mark, so accented characters survive Excel.
Photos are not in the export. The CSV is the text record only. If you are keeping an off-site copy for insurance, the pictures are the part that needs a separate plan.
Working offline#
The mobile app keeps its own database on the device. Everything works with no connection (adding, editing, photographing, searching) and syncs when a connection returns.
Two things need the server: Smart Scan, because the vision model runs there, and the semantic half of search. Keyword search against local data keeps working regardless.
Switching servers#
Signing in to a different server, cloud to self-hosted or one NAS to another, is supported and does not strand the device. The server address is remembered across sign-outs, so going back to your own server is a password, not a setup.
A device holds one inventory at a time. Signing in somewhere new, or as a different account on the same server, replaces what is on the device with what that account has. The app asks first, and if you are holding changes that never reached a server it tells you how many before you decide.
What switching does not do is move anything. The CSV is a way out, not a way back in: there is no import, so an inventory built on cloud has to be built again to live on your own server.
Self-hosting#
The same app runs against a backend on your own hardware, typically a NAS. Photos, database, everything: on a machine you own, on your network.
Backups become yours with it. Nobody else is taking them, and a copy that lives in the house it documents is not a backup.
Deleting your account#
You can delete your account from Settings in the app, or from the account page on the web. Both ask for your password.
It is a real deletion rather than a flag. The rows go, the photos are destroyed outright, and none of it is reversible, so export first if there is any chance you want the record.
What we can see#
On cloud, photos live in private storage and are served through links that expire after a few minutes; there is no public bucket and no permanent image URL. Usage of the paid AI features is logged per call, because that is what makes the meter in Settings → AI possible.
What none of that changes is who holds the keys. Your item text sits in ordinary database columns and your photos are ordinary files in our storage, so we could read your inventory and open your photos if we chose to. No feature in the product shows them to us and nothing is sold or shared for advertising, but that is a practice rather than a lock, and the privacy policy says so in the same words. Running your own server is the version of this app where the question does not arise.
On a self-hosted setup, none of the above involves us at all.
Two exceptions, whoever is running the server. Scanning a barcode sends the code to two public product catalogs; Barcodes covers what is sent and how to avoid it. And search sends text to an embedding provider: your query when you search, and the name, description, tags, room and location of each bin and item when you save it.