# Collect responses

> Give your artifact a form and read the answers back.

Kind: guide · ~2 min · Verified v0.71.0 · Next: [Collections, insights and dashboards](https://pr-767-stg.superartifacts.app/docs/workspace-data.md)

![The artifact Data tab with collected responses.](https://pr-767-stg.superartifacts.app/screenshots/docs/collect-responses-light.0d34be59.webp)

*Answers arrive on the artifact's Data tab.*

You will have a page that collects answers and a place to read them.

**Make an RSVP that collects answers**

```prompt
Using the Event RSVP template, build me an RSVP page for something I am planning — ask me one question first. Publish it, send me the link, and tell me where the answers will appear.
```

## One policy

The agent publishes one `policy` with the artifact. Here is a small example; each field's description explains the choice in place.

```json
{
  "policyVersion": 1,
  "writes": "append-only",
  "perUser": "single",
  "read": "own",
  "retentionDays": null,
  "recordCap": { "perVisitor": 1, "perArtifact": 500 },
  "fields": [
    {
      "name": "attending",
      "type": "boolean",
      "required": true,
      "pii": "none",
      "description": "A yes or no answer, required before submission."
    },
    {
      "name": "name",
      "type": "text",
      "required": false,
      "pii": "contact",
      "description": "A person's name is contact data."
    }
  ]
}
```

`own` lets a visitor read their own answers through the artifact. The owner can read the collected answers with their agent. Fields can be added later; previously collected fields keep their meaning.

## Read, export, erase

**Read the answers and locate the export**

```prompt
Read the responses to <artifact> with super_data, tell me where its Data tab and export are, and explain how to erase a response if someone asks. Erase nothing until I name the response.
```

The **Data** tab shows responses and the schema to people allowed to work with the data. The owner sees raw answers. The agent can download an export through the responses export endpoint; the export follows its access, including any masking. `super_data` lets the owner's agent read answers back.

Erasure removes stored responses, rather than only hiding a table row. A visitor can erase their own data; the owner can erase a named response. Exported copies are separate files.

Size, field, retention and row ceilings live in [Limits](https://pr-767-stg.superartifacts.app/docs/reference/limits.md).

## Check it worked

A submitted answer appears on **Data**. The export includes the response. After erasure, reading it back no longer returns that record.

Next: [Collections, insights and dashboards](https://pr-767-stg.superartifacts.app/docs/workspace-data.md).