Delete your data

Three ways to have data removed from CoreLayerEngine, depending on how much you want gone. All of them are self-service; none of them require you to email us first.

1. Disconnect a single channel

Sign in at app.corelayerengine.com.
Open Settings → Connected channels.
Choose Disconnect on the channel you want removed.

We revoke the grant at the platform itself — not just delete our copy of the token — for Facebook, Instagram, Threads, Google, YouTube, TikTok, X and LinkedIn. We then delete the stored tokens along with any comments and drafted replies fetched from that channel, and stop requesting anything further from it. Where a platform publishes no revoke endpoint, the console tells you so rather than implying we revoked something.

2. Remove the app inside Facebook, Instagram or Threads

If you remove CoreLayerEngine from your app settings on Facebook, Instagram or Threads, the platform sends us a deauthorization callback. We treat it exactly like a disconnect, automatically, and issue a confirmation code.

Meta's flow returns a status URL of the form https://app.corelayerengine.com/platform/data-deletion/status?code=<your code>, which you can open at any time to confirm the request was actioned.

The public data-deletion request endpoint registered with Meta is https://app.corelayerengine.com/platform/<platform>/data-deletion, and these instructions are also served directly by the product at app.corelayerengine.com/platform/data-deletion. Requests to that endpoint are signature-verified and fail closed: an unsigned or badly signed request deletes nothing.

3. Delete an entire workspace

Sign in and open Profile → Delete workspace.
Type the workspace name to confirm. Only the workspace owner can do this.

This erases every post, schedule, contact, asset, connection and account record for that workspace — in every region we can reach, not just the one that served your request, so a workspace that was migrated between regions leaves nothing behind.

What remains afterwards is a tombstone recording that a deletion happened: the workspace identifier, region, timestamp, reason and who requested it. It contains no name, no email address and no content. We keep it for 730 days as proof the erasure occurred, and so that if an old backup is ever restored we can immediately re-delete the same records.

If you are not a CoreLayerEngine customer

If a business uses CoreLayerEngine and holds your details — because you gave them your number, filled in one of their forms, or commented on one of their posts — that business controls your data, not us. Contact them and they can, from their console, look you up by email or phone, export everything they hold about you, erase it, or record that you have withdrawn consent so you drop out of their future messages.

If you cannot reach them, write to legal@ektasi.io with the business name and the email address or phone number concerned. We will pass the request to them and confirm to you that we have done so. We will not act on their data ourselves without their instruction, because we are their processor and not their controller.

How long deletion takes

Disconnecting a channel and deleting a workspace take effect immediately. Requests sent to us by email are actioned within 30 days.

One limit we would rather state than bury: erased data persists in encrypted backups until those rotate out on our schedule of 7 daily, 4 weekly and 12 monthly copies — up to about twelve months for the oldest monthly copy. Those backups are encrypted, are never restored into production as a matter of routine, and if one is ever restored we re-run the purge so that deleted records do not come back.