Safety at the table
Lines and veils, what the product records, and what it deliberately refuses to do.
Why a tool has a safety page
Safety tools at a tabletop are an established practice and they are not ours. Lines and veils, the X-card, session zero: these came from the hobby, and a tool that touches them owes the practice a straight answer about what it does and does not do.
Why concealment is called sealed and not veiled
A veil is a real safety practice: content the table agrees happens off screen. Using that same word for a database feature about hidden lore would collide with it, in the interface, in the moment somebody most needs the word to mean what they think it means.
So concealment is sealed throughout, and veil stays available for the thing it already means.
What the product records
A table can record its lines and veils so they are written down rather than living in one person's memory of session one. They are visible to the whole table by default, because a safety agreement nobody can read is not an agreement.
This is built, on the table page of every campaign, and it is on the feature list as running.
What it deliberately does not do
It does not score, rank, or flag a player. It does not send a person's stated limit to anybody outside their own table.
It does not use safety material for any purpose other than showing it back to that table.
Concealment is not a safety tool
Concealing a passage from a player hides information inside a story. It is not a substitute for a conversation about what the table will and will not play through, and the product never presents it as one.