01 · CHECK-IN
What you share
A city you choose, who you traveled with, roughly when you visited, the best bit, your biggest hassle, optional food, welcome and safety ratings, and whether you would return. You can also add an optional comment of up to 280 characters. We record when the report was submitted.
We do not ask for an account, name, email, exact trip dates, GPS location, photos or contacts. Earlier reports retain the prices, queues, expectations and souvenir answers from the earlier questionnaire.
“Anonymous” means there are no dedicated identity fields. It does not mean network anonymity, verified unique travelers, or a guarantee that nobody can infer something about you. Your own words can identify you, so leave names, contact details and private addresses out of comments.
02 · THE SHARED CLOCK
A new reveal. Every week.
Each collection, called a drop, lasts seven days. The first collection began on 5 September 2026 and reveals on 12 September 2026. Every Saturday, the previous drop becomes eligible to view and the next one starts accepting reports immediately.
The reveal is automatic, based on server time. Nobody needs to press a button, run a job, or leave the site open. The website does not close after seven days. A trip submitted after the boundary joins the new week; earlier trips keep their original week.
Choose Real weekly results on the globe to explore completed drops. The newest completed drop is selected unless you choose an older one or open a shared city link. The countdown always points to the next reveal. The Example globe remains fictional.
This is a shared weekly window, not a fresh seven-day wait for every visitor. A Friday submission usually has a shorter wait than a Sunday submission. A calendar reminder helps you return; we do not send email notifications.
03 · ON THE GLOBE
What becomes public
Overall collection totals are public, including reports from hidden city groups. City answers and comments stay sealed until their reveal and publication thresholds are met.
After the reveal, cities with at least three reports in that drop can show their total and combined return-choice counts. Counts of reports from each questionnaire may also be visible. Version-specific categories and ratings need three reports from that questionnaire; each optional rating needs three non-skipped answers.
City results and version-specific answers below their thresholds remain unpublished for that drop. Their reports do not roll into the next week to reach the minimum. Skipped answers never become neutral ratings, and old questions are not reinterpreted as new ones.
These are self-selected trip experiences, not verified visitor counts or representative city rankings. Safety describes how a trip felt, not a crime rate. Three-report suppression reduces small-group exposure, but someone who knows other contributions may still infer information from totals or changes.
Every sample report and example comment is fictional. Examples are kept separate from the real database and never count toward a live reveal.
04 · IN YOUR OWN WORDS
Your written comment
A comment is optional. Before submitting, you see a preview and agree to publish the text. Editing it resets that agreement. Leading and trailing whitespace is trimmed; the comment is displayed as plain text, without interpreting links, markup or embeds.
Your comment stays sealed until its weekly reveal and until the city has at least three current-questionnaire reports in that drop. A single comment can then appear individually, even if the other reports have no comments. A comment is public text, not an anonymous statistic.
The globe previews one note per eligible city. City reports show complete notes, with more loaded in pages of twelve. Notes carry no name, precise submission time, other individual answers or private ticket details. Their public display keys cannot authorize deletion.
Comments are personal statements. They are not verified or automatically moderated, and no external AI or moderation service receives them. Keep your note about your own trip and leave out identifying details. An operator may remove a comment separately from the report.
05 · KEEP THIS BIT PRIVATE
Your private ticket
Your browser creates a random private deletion key and saves the pending report before sending it. If browser storage is blocked or full, the report is not sent. If the connection drops after saving, you can safely retry the same report after reloading.
The server stores a one-way hash of the deletion key. The key stays in your browser or downloaded ticket backup and is sent only when submitting or deleting the report. It is never placed in a public link or result.
Anyone with your ticket can delete that report. Keep backups private. Importing a ticket reads it locally; its key is sent to the server only if you choose to delete the report. Clearing browser storage without a backup can leave you without the key needed to delete it.
06 · YOUR EXIT ROUTE
Changing your mind
Open Your tickets on the home page and delete the relevant report. Its answers and comment are removed from the database, and future result reads exclude them. If a city or question group falls below its minimum, the affected city results or version-specific answers become unpublished again.
A small deletion record retains only the report ID, hashed key and deletion time, with no answers, city, comment or collection. This prevents an old network retry from bringing the report back.
Already-open browser views, screenshots and copies made by other people cannot be recalled. Provider backups or recovery snapshots may retain deleted records under the hosting provider’s backup policy. Restores must preserve deletion records so removed reports are not accidentally republished.
07 · KEEPING THE EXPERIMENT RUNNING
Cookies & hosting
Baggage Claim runs on hosted infrastructure with a connected database. Visiting or submitting does not depend on the creator’s computer staying on or on access to the source repository.
A necessary one-day session cookie helps limit repeated submissions. Temporary session hashes and daily keyed network-address hashes provide hourly abuse controls. They are separate from trip reports; raw network addresses are not written into the app’s answer database.
These temporary buckets expire within two hours of their hourly window’s start and are cleaned on a later relevant request. Expired entries can remain until traffic resumes. Cloudflare and the hosting platform can process IP addresses and infrastructure logs under their own policies.
There are no advertising cookies, analytics SDKs, mailing lists or email reminders. A calendar download is the reminder option.
08 · AFTER THE TRIP
How long data stays
Browser storage has no automatic expiry for tickets or pending reports. A pending report includes your answers and comment so an interrupted submission can be recovered. It is removed after its completed ticket is safely saved or the server definitively rejects it. Completed tickets remain until removed or your site storage is cleared. Downloaded backups must be deleted separately.
Active reports and the minimal deletion records do not have an automatic expiry in this version. A weekly reveal does not erase the previous week. The results picker lists the latest twelve completed drops, and older results remain accessible through their saved links.
This page describes how the app currently handles your data. For your own report, your private ticket is the self-service deletion method.