Essays
The wrong shape for a collection.
Cloud software solves real problems extremely well: collaboration, access from anywhere, recovery when a device dies, and never thinking about backups again. For most documents most people own, it is simply the correct architecture, and arguing otherwise is nostalgia.
A collection record is an unusually poor fit for every one of those benefits, and an unusually good fit for the corresponding costs. That is not an argument about trust. It is an argument about shape.
Taking the benefits one at a time
Collaboration. Nobody co-edits their watch collection. The document has one author, for its entire life. The single strongest argument for cloud architecture is irrelevant here.
Access from anywhere. Genuinely useful for a calendar. For an inventory of valuables, "reachable from anywhere" is a restatement of the risk — the same property that lets you read it from a hotel lets it be read from somewhere else.
Device loss. Real, and the one legitimate benefit. It is also solved by an encrypted export on a drive in a different building, which costs nothing and creates no permanent second copy under anyone else's control.
And the cost, which is structural
A hosted service must be able to read enough of your data to index it, display it, and support you when something breaks. That is not a flaw in any particular product; it is what the architecture requires. It means a complete, searchable inventory of your valuables exists somewhere you do not control, alongside thousands of others, for as long as the company does.
Then time acts on it. Companies are acquired. Terms are revised. Data is migrated by people who never wrote the original promises. None of that requires anyone to behave badly, and none of it is something you will be consulted about.
The right question
Not "is this company trustworthy?" — a question about the present, asked of a document that will outlive the question. The useful one is: how many copies of this list exist, and who controls each?
That number is the only variable a collector actually governs, and it is the one no security page can improve on your behalf.
Where the software fits — and where it does not
Watch Vault Archive is built so that count stays at one unless you move a copy deliberately. The cost is that the device-loss problem becomes entirely yours — an encrypted backup somewhere else is not a suggestion here, it is the only protection there is. For what the software does today, see how your data is protected.
One thing worth doing today
If your collection lives in a cloud service, export it and read what comes out. Most exports are less complete than the interface suggests — photographs missing, history flattened, attachments absent.
Whatever the export contains is what you actually own. The rest is borrowed.
More essays · How your data is protected · Why local-first still matters