> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/tutorials/removing-participant-data.md).

# Removing Participant Data

Remove participant data for privacy compliance or data cleanup

Whether you are removing test data, cleaning up your reporting, or responding to a customer's privacy request, Zigpoll makes it simple to clear history and metadata from an individual.

#### How to Remove Participant Data

1. **Log into** your Zigpoll dashboard.
2. Click **Participants** in the sidebar. Search for the person if you need to.
3. Select the participant you want to remove.
4. Click **More Actions**, then click **Delete** under **Delete Participant**.
5. Type **permanently delete** and confirm.

This removes the participant, all of their responses and answers, and any email addresses they submitted. Your dashboard totals update to match.

{% hint style="warning" %}
Deleting a participant is permanent and can't be undone. It also doesn't lower the number of responses counted toward your monthly plan limit.
{% endhint %}

{% hint style="info" %}
This feature is useful for complying with privacy regulations like GDPR, where customers may request deletion of their personal data.
{% endhint %}

{% hint style="info" %}
To remove only some of a participant's responses and keep the rest, use **Delete Responses** on the same card. See [Deleting Survey Responses](/tutorials/deleting-responses.md).
{% endhint %}

#### Removing many participants

Participants are deleted one at a time. There is no bulk delete. See [Deleting many participants at once](/tutorials/deleting-responses.md#deleting-many-participants-at-once) for your options.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/tutorials/removing-participant-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.