Privacy & Data Use · current product behavior
You can explore without an account. If you make Casebook entries, this page explains what stays on this device, what moves into a private signed-in Casebook, what is sent to Simply Swiftie, and what is public information.
This is a plain-language description of how the product works today. It is not legal advice or a contractual guarantee.
The four places to know
Your cases, examinations, favorites, bracelets, memories, selected tour nights, preferences, and other Casebook work are saved in this browser. A small marker also remembers whether you have seen the latest What’s New entry.
This is local to this browser profile. Anyone who can use that profile may be able to see it.When you choose ChatGPT/Sites sign-in, Casebook records are copied to account-scoped D1 storage so they can follow you across signed-in devices.
The app checks the signed-in account before returning this state. It is not placed in the public archive.Memory images and the photos or short videos you add to a tour night are stored in private R2 media storage.
Media routes check the signed-in owner. Uploaded keepsakes are not added to public tour pages or public source records.Feedback notes and a small engaged-visitor record are sent to the app’s D1 database. The details are explained below.
Feedback is not published, but it is separate from your private Casebook and has different controls.Without sign-in
The browser’s local storage holds the work you create: cases and evidence, examination progress, saved news choices, favorite tour nights, personal tour-night details, memories and attached memory images, bracelet designs, your chosen era and name, personalization answers, and backup status.
Clearing this site’s browser data can remove that copy. Simply Swiftie does not provide automatic recovery for a browser-only Casebook, so use the JSON export if you want a portable backup.
After the first qualifying pointer or keyboard interaction on a visible page, the app may set a one-year, HTTP-only cookie for an anonymous “engaged detective” count. For an unsigned browser, D1 receives a one-way hash of the cookie’s random token; for a signed-in visit, it stores a hash derived from the account identifier. The record also includes its kind and created/last-seen times. The raw identifier is not shown in the public count.
This is a rough browser count, not a promise that one browser equals one person. The product does not currently offer a separate self-service screen for this record.
Optional sign-in
ChatGPT/Sites sign-in supplies Simply Swiftie with an account identifier, email address, and display name. The app uses them to recognize the account and keep its Casebook separate.
Simply Swiftie does not receive or store your ChatGPT password. Password handling stays with the sign-in provider.
The account record and Casebook state can include your cases, examination history, favorites, bracelets, memories, personal tour-night details, profile preferences, saved news decisions, Site Watch decisions, and sync revision information.
Memory images and personal tour-night photos or MP4 videos are stored separately as private media. The Casebook stores the details needed to load those files for the signed-in owner.
Public cases, sourced Taylor history, tour facts, public photographs, source links, and Site Watch change receipts remain public. Adding a personal night or memory does not rewrite the public record.
Feedback · available without sign-in
The feedback record stores the category you choose, your note, the product area you were viewing, a short case-number context when present, and the submission time. It does not ask for a name, email address, or account.
A hidden blank field is used to reject obvious automated submissions. It is not a visitor profile field.
Your browser creates a random retry key for the note. Retrying the same unconfirmed note reuses that key so the app can avoid duplicate records; editing the note creates a new key. The feedback table stores an ID derived from that key, not a reply address.
There is no feedback inbox, download button, or self-service deletion control for visitors today. Do not include contact details or sensitive information unless they are genuinely needed for your request.
Public information & other sites
Controls available now
The Casebook can export a JSON backup and restore from one. The export tries to include private memory images. It includes personal tour-night descriptions and media references, but it does not package the uploaded tour-night photo or video files themselves.
You can remove memories, bracelets, favorites, and private tour-night media in the product. Removing a memory causes its private cloud image to be deleted on the next successful Casebook save; removing a tour-night upload calls its private media deletion route directly.
Signed-in settings include “Delete my cloud Casebook.” It removes Casebook state, private uploads, saved news and Site Watch decisions, and private-night ownership, then clears the local Casebook copy and signs out. The interface treats this as permanent and offers no undo.
It does not delete the underlying ChatGPT/Sites account, Simply Swiftie’s account-identity mapping, feedback submissions, or the engaged-visitor record. Those records have no self-service delete screen today; use the privacy-question route below to ask about correction or deletion.
If a local and signed-in Casebook differ, the app asks which copy should lead and downloads the unchosen copy as JSON before replacing it. This is conflict protection, not a general backup or deleted-item recovery service.
Browser data remains until it is cleared or replaced. Private Casebook data remains until you change or delete it. Site Watch run records older than 90 days are removed. The product does not currently publish a deletion timetable for feedback, visitor records, account identity mappings, or every public source record.
Minors & family memories
Family memories can be meaningful without including full names, ages, schools, home addresses, schedules, medical details, private accounts, or anything else that could identify or locate a child. Use first names, nicknames, broad dates, and the least detail that still preserves the memory.
The public “22” Hat archive deliberately limits reported information about minors, but personal Casebook text and uploads are still your responsibility. Simply Swiftie does not currently perform age verification or provide a parental-consent workflow.
Questions, corrections, or deletion requests
Open “Drop a clue,” choose A note, and say that your message is about privacy. Include the feedback receipt or the specific record only if you have it. There is no promised response time, identity-verification workflow, or automatic deletion process behind this route today.
Open a privacy note →