A seven-day anonymous survey
A short-lived survey makes the collection window visible. The useful promise is specific: a small room, a capped audience, a private owner link, and a seven-day application expiry.
Match the clock to the task
A week can fit a project retrospective, workshop follow-up, classroom pulse, or small community check-in. It gives people a defined response window without turning a temporary question into an indefinite data store.
Put both the closing expectation and deletion boundary in the invitation. If participants need more time, create a new deliberate collection window rather than silently extending an old promise.
Keep the room bounded
CandorKit limits each survey to one through five questions and caps the number of accepted responses. A narrow room is easier to explain, review, and delete than a reusable form accumulating unrelated answers.
The public respondent link is separate from the private owner link. Share the first with participants and keep the second with the person responsible for reviewing and disposing of the results.
- One clear feedback purpose?
- No identity question by default?
- One accountable results owner?
- Response cap matches the group?
Close the data loop
Review results before expiry, summarize only what the task needs, and avoid exporting raw answers unless there is a clear reason. A CSV stays wherever the owner saves it and is not removed by application cleanup.
After seven days, the application rejects new answers and scheduled cleanup removes expired rooms from the live database. This is an application retention boundary, not a claim that every network log or owner-created copy disappears at the same instant.
Put the boundary in the invitation
Tell respondents what is stored, what is not, who can read it, and when it disappears.
Create a bounded survey