Yes, even without a login system, you can still provide each buyer with a personalized "purchase history" page using static files and tokenized URLs. The key lies in how you structure and automate these pages within your Jekyll site. Just like with tokenized download pages, we can create a unique static page per buyer that lists all products they've purchased — complete with download links, timestamps, and other metadata. Why Build Purchase History Pages in a Static Site? There are several advantages: No database required: All data is embedded directly in markdown or YAML. Works offline: Buyer history can be cached or even saved locally. Privacy-friendly: No login means no cookies, no passwords, no data tracking. Easy to revoke: Just delete the file from the repo to revoke access. Step-by-Step: Creating a Purchase History Page for Each Buyer 1. Define the Data Model Use a data file (YAML or JSON) that stores purchases per buyer: ```y...