A seven-day anonymous survey

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.

CandorKit limits each survey to one through five questions and caps the number of accepted responses. A narrow survey is easier to explain, review, and delete than a reusable form accumulating unrelated answers.

The public respondent link is separate from the private results link. Share the first with participants and keep the second with the person responsible for reviewing and disposing of the results.

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.

Submitted responses stay in the private results view until the survey expires after seven days. At expiry, the survey and results links stop working. The next daily cleanup deletes the expired survey and its responses from CandorKit's live database. This application retention boundary does not remove network logs or owner-created copies at the same time.