Deleting a Mass Creative project, removing a hosted tool, disconnecting credentials, revoking third-party permissions, and deleting uploaded files are separate actions. Use the steps below for the level of removal you want.
01 Remove the saved connection
Sign in to the hosted Meta Ad Loader with the same site-managed account identity used to make the connection, then choose Disconnect Meta. This removes the encrypted Meta credential used by that KITWRKS account and stops future Meta API calls through the connection. It does not delete your ad account, campaigns, ads, batch records, or creative files already transferred to Meta.
02 Revoke access at Meta
In Facebook, open Settings & privacy → Settings → Business Integrations. Under Active integrations, select the KITWRKS integration and choose Remove. This prevents future access through the integration. Meta's current instructions are in its Business Integrations help article.
03 Delete uploaded creative files
Creative files uploaded to the hosted Meta Ad Loader are kept in private Cloudflare R2 storage with a default 30-day retention window. After expiry the app stops using them and removes them during storage cleanup. To remove a file sooner, open the Creatives step and choose the × control beside that upload. If a batch is actively using the creative, finish the current row or build a replacement plan first. If you cannot use the self-service control, email hello@kitwrks.com from the address associated with your KITWRKS account and identify the batch or upload.
Removing a hosted creative does not delete an ad or media object already created in Meta. Manage those separately in Meta Ads Manager. A Meta deauthorization or data-deletion callback also does not remove objects that Meta holds independently.
04 Delete a Mass Creative project
Email hello@kitwrks.com from the address associated with your KITWRKS account and include the project name or batch ID. After verifying the request, we will remove eligible Mass Creative project records, briefs, research records, uploaded assets, generated media, and quality-review records from our active systems. Files or ZIP exports you already downloaded are outside KITWRKS control and are not removed by this process.
Billing, transaction, security, fraud-prevention, and support records may be retained when reasonably needed to meet legal obligations, prevent abuse, resolve a dispute, or document a credit or purchase. Deleting a project does not automatically cancel or refund a Stripe purchase.
05 Remove a generated lead magnet
Email hello@kitwrks.com from the owner address used to publish the tool and include its public URL. After verifying the request, we will remove the hosted configuration, encrypted connection details, and associated aggregate events. Disconnect or rotate the credential in Google, GoHighLevel, or your automation provider as well. Removing the KITWRKS tool does not delete contacts already delivered to your connected destination.
06 Delete other KITWRKS records
Email hello@kitwrks.com from the address you used with KITWRKS and ask for a data deletion. We will acknowledge the request and, after verifying it, remove the email and subscriber information we hold within 30 days of receipt. If applicable law allows or requires more time, we will explain the reason and the expected timing.
A verified request can cover the encrypted Meta credential and connection metadata in private D1 storage, hosted destination and batch records, and eligible account records. Some security, transaction, subscription, or accounting records may be retained when reasonably needed to prevent abuse, resolve disputes, or meet legal obligations. Canceling a paid subscription is a separate action: use the Stripe billing portal when available or ask us to cancel future renewals. Deletion does not retroactively refund subscription fees.
The Meta connection relay normally has no lasting customer record to delete: its one-time token ticket is removed when redeemed, becomes unusable after five minutes, and is cleared from temporary memory during relay cleanup if it expires. When KITWRKS receives a valid Meta deauthorization or data-deletion callback, it clears any associated ticket still in flight and processes deletion of the corresponding hosted Meta connection. Use step 03 or include the relevant uploads in your request if you also want hosted creative files removed early.
What revocation does not remove
Ads and other objects already created in your Meta account remain under your control until you change or delete them in Meta. Meta may also retain information under its own terms and privacy policy. KITWRKS cannot delete records held independently by Meta or another service.
Need help?
If you cannot access the KITWRKS account that was connected, email hello@kitwrks.com from the associated address. We will verify the request and help complete the appropriate removal steps. See the privacy policy for more detail about what KITWRKS handles.