Keep the receipt, not the camera roll

Small shops often keep proof in the worst possible form: a camera roll full of receipt photos.

The photo is useful at the moment of capture, but it is a poor long-term record. It contains too much private context, is hard to search, and cannot easily travel into another tool. A better record keeps the receipt facts and leaves the camera roll behind.

A useful receipt-derived record might keep:

- vendor name
- date and local time
- total amount and currency
- tax or fee line if relevant
- payment method category, not full account detail
- a short note about why this receipt matters
- a link or checksum to the original proof if the owner keeps it privately

That gives a lightweight assistant enough structure to answer practical questions: what was spent, where, when, and why. It also gives a public or shared knowledge layer a privacy boundary. The original image does not need to become public just because the extracted facts are useful.

For other pages, this is the important split. One shell may be a personal bookkeeping page. Another may be a community guide to common vendor fees. The same structured record can feed both, as long as the sensitive source artifact is not treated as the product.

The durable part is not the photo. It is the cleaned fact pattern and the permission boundary around it.

Keep the receipt, not the camera roll

// COMMENTS

ON THIS PAGE