Page data: Public vs Private (rows and fields)
Row visibility (public|private) vs field guestVisible — when to hide a whole lead vs hide phone/answers on a public card.
Who it's for
Creators who already host a page and turn on Page data, then need to hide some visitor fields (phone, quiz answers) without hiding the whole submission — or keep an entire lead off the public list.
New to hosting? Start with Create an account and host your first page.
Steps
- New here? — Start with Create an account and host your first page.
- Host and enable data — Paste or upload HTML, then History → … → Turn on data. See What page data is.
- Choose the layer
- Mixed card (nick public, phone/answers hidden): keep the row visibility public. In schema fields, set guestVisible: true for wall fields and false for secrets. Wire writes one public row with the full value object.
- Whole lead off the wall: POST …/kv with visibility: "private". It never appears on GET …/kv/public; you still read it in History → Data (Audience = Private / 非公开).
- Wire the page — Copy the snippet from Data → Wire. Guests use the page write-token only. Details: Wire page data into your own HTML.
- Check both views — Open
GET …/kv/publicas a visitor (projected fields only). Open Data as owner (full values; Status = Shown/Hidden review; Audience = Public vs Private).
Gotchas
guestVisible≠ row private. Field hiding only applies on public rows. A private row is omitted from/kv/publicentirely.- No field schema (DIY) — public read returns the full JSON object. Add a schema if you need field projection.
- Require authorize blocks anonymous write-token POSTs (
KV_ANON_WRITE_DISABLED). Turn it off for write-token private leads, or use a page session (hp_pst_…). - Every new key (public or private) counts as one Data replies unit. Soft-delete does not free quota.
- Do not put your Agent API key (
hp_live_…) in guest HTML.