Right To Be Forgotten (RTBF)
Implement GDPR-compliant data deletion for your typeforms
The Right to Be Forgotten (RTBF), also known as the Right to Erasure, is a key component of GDPR and other privacy regulations. It gives individuals the right to request deletion of their personal data. The Typeform Responses API provides endpoints to help you comply with these requirements.
What is the Right to Be Forgotten?
Under GDPR (General Data Protection Regulation) and similar privacy laws, individuals have the right to:
- Request deletion of their personal data
- Have their data removed from systems without undue delay
- Be informed when their data has been deleted
As a data controller using Typeform, you’re responsible for honoring these requests for responses collected through your forms.
When to delete responses
You should delete responses when:
- A respondent explicitly requests deletion of their data
- The data is no longer necessary for the purpose it was collected
- The respondent withdraws consent for data processing
- The data was unlawfully processed
- Required by law or regulation
Before deleting data, ensure you understand your legal obligations. In some cases, you may be required to retain data for legal, accounting, or regulatory purposes even when a deletion request is made.
Deleting responses via API
Delete specific responses
To delete one or more responses, send a DELETE request with the response tokens:
Example:
This permanently removes the specified responses from Typeform’s systems.
This action is irreversible. Once deleted, responses cannot be recovered. Always verify response tokens before deletion.
Response deletion confirmation
Successful deletion returns a 204 No Content status code:
If any tokens are invalid or don’t exist, you’ll receive an error:
Implementing an RTBF workflow
Step 1: Identify the response to delete
First, locate the response(s) associated with the deletion request. You’ll typically need to:
- Match the user’s email or identifier to form responses
- Retrieve the response token(s) for that user
Then filter responses in your application to find matching email addresses or identifiers.
Step 2: Verify the request
Before deletion:
- Authenticate the requester (confirm they own the data)
- Check if you have legal grounds to retain the data
- Document the request for compliance purposes
Step 3: Delete the response
Step 4: Delete from your systems
Remember: Typeform only stores response data on its platform. If you’ve exported or synced responses to your own databases, you must also delete them from:
- Your database
- Analytics platforms
- CRM systems
- Email marketing tools
- Any other integrated systems
Step 5: Confirm deletion
Notify the requester that their data has been deleted, including:
- What data was deleted
- From which systems
- Date of deletion
- Retention of any data (with justification)
Automation example
Best practices
Verification
- Authenticate requests: Verify the requester’s identity before deletion
- Confirm email ownership: Send confirmation emails to verify the request
- Document everything: Keep logs of all deletion requests and actions
Process
- Respond promptly: GDPR requires response within 30 days
- Search comprehensively: Check all forms and systems for the user’s data
- Delete completely: Remove data from all systems, not just Typeform
- Verify deletion: Confirm data is removed from all locations
Communication
- Acknowledge requests: Respond immediately upon receiving a request
- Set expectations: Explain the timeline and process
- Confirm completion: Notify the requester when deletion is complete
- Document exceptions: If data must be retained, explain why
Handling file uploads
If responses include file uploads, those files should also be deleted:
- Download and store file metadata before deletion (if needed for compliance logs)
- Delete the response (files are automatically deleted with the response)
- Remove any copies you’ve stored elsewhere
Data retention policies
Implement clear data retention policies:
Audit trail
Maintain an audit trail of all deletions for compliance:
Legal considerations
This guide provides technical implementation guidance only. Always consult with legal counsel to ensure your RTBF processes comply with applicable laws and regulations in your jurisdiction.
Key legal points:
- 30-day response time: GDPR requires response within one month
- Exceptions exist: Some data may need to be retained for legal reasons
- Proof required: You may need to demonstrate data deletion
- Scope matters: Deletion must be comprehensive across all systems
- Communication required: You must inform the requester of the outcome
Testing your RTBF process
Custom RTBF script
For more complex scenarios, see the RTBF custom script guide for advanced implementation patterns.
Next steps
- See the RTBF custom script for advanced automation
- Learn about response webhooks for real-time processing
- Review the API Reference for complete endpoint documentation
- Implement data retention policies for automated cleanup