Plan availability | All plan types (with varying limitations) |
Permissions |
|
Platforms | Web/Browser, Mac app, Windows app |
Airtable provides multiple ways for customers to fulfill GDPR data deletion (erasure) requests. Depending on your plan type and administrative controls, you can delete or remove personal data within your Airtable base(s) using the Enterprise API, Copy/Delete base method, or by disabling snapshots and clearing revision history.
Our overall recommendation to meet GDPR Data deletion requirements through the Airtable platform is to use the Enterprise API feature. It allows for automating workflows and significantly reduces manual deletion work. However, we understand that not all customers are on an Enterprise plan, and therefore, Airtable has laid out other options as described in Option 2 (Business or Enterprise customers) and Option 3 (Any plan type) to meet GDPR Data Deletion requirements.
Option 1: Using the Enterprise API
Enterprise admins can use the Enterprise API to automate deletion workflows, including removing records, comments, views, and user associations across bases.
Considerations:
When data is deleted through the API, it is deleted and immediately removed from the base UI.
Deleted data is no longer visible or accessible in Airtable, including through undo/redo, trash, base snapshots, and real-time payloads.
Requirements to use the Enterprise API:
Only available to Enterprise scale customers.
Requires admin/developer access and valid API credentials.
Setup steps:
Access the Enterprise API via your admin panel or developer credentials.
Identify and target the records, comments, or objects containing personal data.
Execute the API delete call.
Confirm deletion in your system logs or via a follow-up API read.
Option 2: Disable snapshots and clear revision history
Business or Enterprise admins and workspace owners can minimize exposure of personal data by clearing base revision histories and having Airtable disable the snapshots feature.
Considerations:
Clearing a base’s revision history is irreversible; once the history is cleared, it cannot be recovered.
Snapshots created before disabling remain until their retention period expires.
Disabling snapshots and deleting those snapshots can only be performed by request when relating to GDPR.
Setup steps:
Discuss the potential downstream impacts with your IT team.
Contact your Airtable account executive or Airtable Support to request that the snapshots feature be disabled across your organization’s Airtable instance.
Disabling the snapshots feature will not delete any previous snapshots, so our internal team will need to run a report to identify and delete all previous base snapshots.
You will need to clear revision histories on a base-by-base case. Consult the information in this article to perform these actions.
Option 3: Copy and delete base technique
For non-automated deletion, workspace owners or creators can remove data by copying a base without records or history, and then delete the original base that contains personal data.
Considerations:
The copied base includes your structure but doesn’t carry over history, comments, or integrations.
After copying, reconnect any automations, integrations, and API connections to keep your workflows running smoothly.
Setup steps:
Open the base containing personal data.
Duplicate the base without including records, comments, or revision history.
Verify that the duplicated base retains your desired structure (tables, fields, automations).
Delete the original base containing personal data.