What the notebook stores
The site uses browser storage for saved show IDs, the current show budget and the eight-page zine draft. There is no reader account or device synchronization. Another person using the same browser profile can see that work. Clearing site data removes it.
If persistent storage fails, the site tries storage for the current tab session. If that also fails, changes can last only while the current page remains open. A message explains the fallback. Download work you want to keep, especially before closing a private-browsing window.
This backup contains all saved show IDs, budget notes and zine text. It is readable JSON for your records; this edition does not include a backup import tool. Individual tools also export readable or printable files.
Clear this browser’s RiotWithMe notebook
Download anything you want to keep first. This removes saved shows, the budget and the zine draft from this browser. It does not remove a contribution already sent to the server.
What a contribution sends
The show and correction form sends its type, subject, source link, details, optional contact email and any date, venue, age or affected-page information you entered. An editor can read those fields. Public receipt pages expose only the receipt ID, received date, contribution type, review status and any published event link.
Publication uses the details an editor explicitly enters into the public event record. Your email is not copied into that record automatically. Do not submit private addresses, ticket barcodes, access arrangements or sensitive information about another person. The review form is for public facts and their sources.
Contributions and private review notes remain in the server’s review history until the site operator removes them. This edition has no automatic deletion schedule. To request a correction or removal, use the correction form, identify the receipt or public page, and use this privacy page as the source link if no other public source applies. Do not include sensitive proof in the initial request.
Operational data
The application uses a temporary, keyed hash of a connection’s address to limit repeated submissions and editor login attempts. It does not put the raw address in the contribution record. Rate-limit entries expire, and old entries are removed when the limiter next runs. The server or hosting provider may keep its own request logs.
Authorized editors receive a session cookie that lasts up to eight hours. It is used for review access. There is no reader login cookie, newsletter enrollment or automatic email confirmation in this edition.
Analytics
We use Google Analytics to count visits and see which pages people read. It records the pages you view, the site that sent you, your approximate region and your device type.
If you're in the EU, the UK or Switzerland, it runs without cookies. Everywhere else it sets first-party cookies so it can tell a return visit from a new one.
Google explains what it does with this data in How Google uses information from sites that use its services. You can opt out with Google's opt-out add-on or any content blocker.
Ads
This site shows no ads.
Links and downloads
Official ticket and venue links open external sites with their own policies. The site does not send notebook text in filter URLs. Downloaded budget, zine and notebook files do contain the text you wrote, so check a file before sharing it.
Fonts and the archive photograph are served from this site. There are no embedded social feeds or map trackers. The map is an original diagram with ordinary links to the city guides.