Read what your site collected

Everything your site collects (form messages, sign-ups, RSVPs) is append-only from the page: a visitor’s browser can add an entry but can never read the list back. Reading is reserved to you, the owner. No terminal, no technical skill required.

Reading submissions

Two ways, same data:

• In your dashboard: open your project and go to the Collected data tab. Every store your site fills up appears there with its count — form submissions, saved values, and counters (votes, likes, ratings). Click one to browse it: submissions show their fields and when they arrived, paginated; counters show each tally, highest first.
• Ask your AI: “what did my form collect this week?”, “read me the last five sign-ups”. The assistant reads your sites only, and what it sees is exactly what the dashboard shows.

Why the page itself can’t read them

There’s no “list submissions” call in the page on purpose. If the page could read the bucket, anyone visiting could too; the page’s token is public by nature. Keeping reads owner-only is what makes a public contact form safe by construction.

Private per-member journals aren’t shown here

If a store is a private journal — a page where each signed-in member keeps their own entries, only possible on an organization page — you’ll see it listed with a count, but not its content. Those entries belong to each member and are readable only by them, never by you. That privacy is enforced in the platform itself, not just hidden from the dashboard. Each member reads back and erases their own entries directly, and a private journal always has an auto-delete window, so this data never lingers indefinitely.

Removing one entry (moderation)

If your page shows what visitors write — a feedback wall, a public board, questions from an audience — sooner or later something turns up that shouldn’t stay: spam, an insult, a message posted by mistake.

Open the store, find the entry, and use Delete on its row. Only that entry goes; everything else stays exactly as it was. It’s removed for good — from the public page and from disk — so there’s no undo.

This is not the same as erasing a person

Delete removes a piece of content. Erase a person’s data (below) removes everything tied to someone, across all your stores, and is recorded as an erasure request. Use the one that matches what you’re actually doing — your audit trail should tell the truth about it.

Private journals can’t be moderated

Entries in a private per-member journal belong to their author. You can’t read them, so you can’t remove them either. Each member deletes their own.

Starting a fresh round

Counters only ever go up — a visitor can add to them, never set or lower them. When you want a clean slate (a new vote, next month’s meetup, a second run of the same poll), open the counters store and use Reset: every tally goes back to zero and counting starts again.

Erasing someone’s data (right to erasure)

When someone asks you to delete their data, open the Collected data tab, find Data & privacy, and choose Erase a person’s data: type their email and confirm. Bailey removes every record tied to that value across all your stores, and tells you how many it removed.

It’s immediate and permanent. The action is recorded in your audit log (the email itself is never logged).

Automatic deletion (retention)

You don’t have to remember to clean up. When you declare a data store with an auto-delete period (see Data & privacy), Bailey sweeps old records for you on a schedule and drops anything past its retention window.