Integrations

Connect the systems where user data lives. Forget API offers multiple integration types so you can route deletion Requests across your stack.

What is an Integration?

An Integration is a destination that Forget API can send deletion Requests to, so your users’ data can be removed from that system. Each Integration is made up of three parts:

1. Workspace assignment: Every Integration belongs to exactly one workspace. This is how Forget API knows which Integrations to target when a Request is submitted to that workspace. Workspaces let organizations group Integrations to match business needs.
2. Account (authentication): Each Integration uses an Account to authenticate (API key, OAuth, or database credentials). Accounts can be created during Integration setup, and later edited or switched from the Settings/Accounts page. A single Account can be reused across multiple Integrations of the same Integration type.
3. Additional configuration: Many Integrations require extra settings so Forget API can process deletions correctly (for example, identifier type, project IDs, dataset/table names). Configuration needs are Integration-specific.

Request processing types

Integrations support two deletion processing modes:

• Synchronous: The provider processes the deletion immediately and returns a final result right away.
• Asynchronous: The provider accepts the deletion and completes it later. Forget API tracks progress and surfaces status updates until completion.

Forget API handles both modes and normalizes status across Integrations.

Integration categories

Brief overviews are below; see subpages for details and setup steps.

• Cloud Tools: Third-party SaaS where customer data may live (e.g., analytics, marketing, product tooling) and which support deletion APIs. Forget API maintains these Integrations so you can reliably propagate deletions.
• Webhooks: A flexible way to process deletions for internal systems or third-party tools not yet natively supported. Use webhooks to trigger custom logic on your side.
• Databases & Warehouses: First-class support for Snowflake, BigQuery, Postgres, and more to manage customer data according to your business logic (e.g., soft delete, masking, scheduled jobs).
• Productivity: Workflow-oriented Integrations that don’t necessarily delete data directly but help coordinate internal processes. For example, the Linear Integration creates an issue for a designated team to kick off manual steps required to remove data from non-exposed systems.