KNOW WHAT YOU’RE SHARING

A room for your people.
A clear view of its limits.

Use a room for information you intend to share with the people who receive its invitation. The link controls access to the conversation.

Unlisted rooms and invitation links.

Room links use long random identifiers. There is no public room directory, and room pages are marked not to be indexed by search engines. Anyone with the link can read the question, names and participation status. People can join while the question is being framed or responses are open.

After the host opens discussion, individual submitted views and explanations are visible to anyone with the room link. A participant can forward the link or copy information they have seen. An unlisted link is not a confidential channel.

What is saved on the server.

CivilPact stores room questions, option descriptions, chosen participant names, submitted responses, priorities, outcomes, round history and timestamps. The host’s Sites account identifier controls the room. The app does not store the host’s email or profile name in room records.

Guest room sessions use a random token in a room-specific, HTTP-only browser cookie. A hash of that token is stored with the participant. The token identifies a browser session, not a verified individual. Using a different browser or clearing cookies can lose access to that participant’s response.

What stays on your browser.

The new-room form and response drafts use versioned browser storage. Response drafts are specific to a room, round and participant. They are not submitted until you choose Send. Browser storage and cookies can be cleared by browser settings or private browsing; keep the tab open when a draft-storage warning is shown.

The host signs in with ChatGPT through Sites. That service handles its sign-in session and basic profile authorization. CivilPact uses the account identifier for ownership.

Hidden responses and deliberate discussion.

Before discussion opens, the server sends only your own individual response back to your room session. Other participants and the host can see participation status but not your choices, priority or notes. When the host opens discussion, those submitted views become visible to the room and stop accepting edits for that round.

Later rounds keep the earlier record. Archiving closes the invitation link while preserving the room, and the host can restore it. Closing a link cannot recall copies that others already made. There is no permanent-deletion control in the current app.

Operation and limits.

The app uses short-lived, hashed network counters to limit repeated creation and joining requests. These counters do not store raw IP addresses and are removed after their short expiry. Hosting and sign-in services may retain their own operational logs under their policies.

The app includes no advertising pixels or third-party analytics scripts. Its font files are served locally. Your room content is not sent to an AI model or automatically emailed to participants. Rooms refresh from the server only while the page is visible.