How do I disconnect my account?

To disconnect your Apify account from ApifyForge, go to the Settings page and click the Disconnect button. This immediately deletes your encrypted API token from our database and clears all cached analytics data associated with your account. The disconnection takes effect instantly — no waiting period, no data retention, no lingering access. Here is exactly what happens when you disconnect. Your encrypted API token is permanently deleted from our database. All cached analytics data — revenue figures, success rates, quality scores, fleet metrics — is purged. Your ApifyForge dashboard resets to its initial empty state. No API calls can be made to your Apify account from ApifyForge after this point. Your actors, runs, datasets, and everything on the Apify platform itself are completely unaffected — disconnecting from ApifyForge has zero impact on your Apify account. There is an alternative approach if you prefer. Instead of disconnecting through ApifyForge, you can revoke the API token directly from your Apify account at console.apify.com/account/integrations. Simply find the token you created for ApifyForge and delete it. This invalidates the token everywhere instantly, which means ApifyForge can no longer make API calls even though the encrypted (now-useless) token remains in our database until you formally disconnect. For complete cleanup, we recommend doing both: revoke the token on Apify's side first, then disconnect in ApifyForge Settings. Reconnecting later is straightforward. Go to Settings, enter a new API token, and click Save. Your dashboard will repopulate within a few minutes with fresh data from the Apify API. No previous cached data is restored — everything is pulled fresh. This means there is no penalty for disconnecting and reconnecting; you get a clean start every time. If you are disconnecting because of a security concern, revoke the token on Apify's side immediately at console.apify.com/account/integrations rather than relying solely on the ApifyForge disconnect button. For more on token security, see the related question about how your API token is stored.