Data Deletion Instructions

Disconnect a Connected Provider

A tenant administrator can disconnect a connected provider from the relevant Kitenga setup area, such as Marketing Social direct providers, Marketing Ads direct providers, or connected reporting sources.

Users can also revoke Kitenga's access directly in the third-party provider account, such as Meta Business integrations, Google account permissions, LinkedIn account permissions, or the relevant platform's business settings.

What Disconnection Does

Disconnection prevents Kitenga from making new API calls with that provider credential. Existing imported reporting rows, calendar items, draft references, audit logs, and historical metrics may remain until a deletion request is processed or the tenant retention policy removes them.

Where provider tokens are stored, Kitenga removes or disables the tenant-scoped credential state as part of the disconnection process.

Request Data Deletion

To request deletion of Kitenga-held tenant or connected-platform data, email support@kitenga.app with the tenant name, workspace domain, connected provider, channel or account name, and the data you want removed.

We may need to verify that the requester is authorised for the tenant or connected account before deleting data. We will confirm the scope of deletion, complete the request where technically and legally possible, and explain any records that must be retained for security, audit, billing, or legal reasons.

Meta, Facebook, and Instagram Data

For Meta Social connections, deletion requests can cover stored connection records, discovered Facebook Page and Instagram Business channel records, imported organic posts, imported insights, calendar items created from imported social posts, and social publication state created in Kitenga.

Revoking Kitenga in Meta will stop future access. If the tenant also wants previously imported data removed from Kitenga, they should submit a deletion request using the process above.

Response Time

Kitenga will acknowledge deletion requests as soon as practical and process verified requests according to applicable privacy law, contractual obligations, and platform requirements.