Airtable

Airtable says users own the content they upload.

Airtable frames many privacy rights around access, correction, and deletion of service data.

Base and workspace permissions still limit who can reach data before optional features are enabled.

The policy provides contact paths for permanent deletion support rather than leaving all intervention opaque.

The reviewed source does not provide a strong product-specific no-AI-training commitment.

Integrations and product-improvement processing still mean uploaded content is not isolated to one narrow use case.

Airtable discloses third-party integrations and service-provider data flows.

Shared bases and connected tools can expose records beyond the person who entered them.

Users can access, correct, amend, or delete content within the services.

Workspace and base permissions let teams constrain who sees records internally.

Uploaded-content ownership creates a better baseline than a pure platform-owned-content model.

Users can request permanent deletion support for certain data-handling issues.

Airtable collects automatically collected information and may use marketing or advertising technologies.

Integrations and website analytics widen the tracking surface beyond just base editing activity.

Privacy rights are documented for EEA, UK, Swiss, and U.S. state residents.

Airtable is not built as a public social or ad-targeting feed.

Workspace permissions and account governance slightly narrow the practical exposure of tracked activity.

Deleted content may remain in archived or backup copies for revision history and base snapshots.

Shared workspaces and integrations can keep copies of data beyond one user's direct deletion action.

Users can delete Airtable data and request permanent deletion support.

Workspace and base governance can help teams actively manage what data remains available over time.

The rights framework gives users a formal basis to challenge or remove retained data.

Uploaded-content ownership makes retention questions more reviewable than in opaque platform-owned models.

Users can manage content within the service and contact privacy@airtable.com for permanent deletion.

Access, correction, amendment, and deletion rights are documented.

Base and workspace permissions let teams control who can view or edit shared data.

Users can choose how and whether to connect third-party tools.

Some deletion outcomes still require support and shared workspace or base coordination.

In collaborative bases, one person cannot always unilaterally control every copy or permission state.