What data can ApifyForge access?

ApifyForge can only access the data that the Apify API exposes for your account using your API token. This includes your actor list, run history and logs, dataset metadata, key-value store metadata, build information, and usage statistics. ApifyForge cannot access anything outside the Apify API scope. Here is a specific breakdown of what is and is not accessible. ApifyForge CAN access: the list of actors in your account with their settings and metadata, run history including status, duration, and resource consumption for each run, dataset metadata such as item counts and schema information, key-value store listings, build logs and version history, and your account usage statistics and credit consumption. ApifyForge CANNOT access: your actor source code or repository contents, environment variables and secrets stored in your actor configuration, the actual content of your dataset items (we read metadata only, not your scraped data), proxy passwords or proxy configuration details, billing information or payment methods, or any data from other Apify users' accounts. This distinction matters for security. Your source code, environment variables, and scraped data never leave Apify's servers. ApifyForge computes analytics — revenue trends, success rates, quality scores, fleet health metrics — from the metadata available through the API. These computed analytics are cached temporarily in our database to keep the dashboard responsive, but the raw data is not stored permanently. Cache is refreshed at regular intervals and automatically cleared when you disconnect your account. The Apify API token you provide determines the exact permission scope. Standard tokens provide read and write access to your account resources. If Apify introduces more granular token scopes in the future, you could further restrict what ApifyForge can do. For now, we recommend using a dedicated token as described in the related question about how to connect your Apify account. For information about how your token is stored and protected, see the question about API token storage.