What we collect.

The short version

• Execution depends on the product path. Local CLI fetches run from your machine. Hosted API fetches are processed by Everfetch infrastructure so we can return the requested metadata or workflow result.
• We do not train models on customer inputs or outputs. Your request data is used to provide, secure, debug, and bill the service, not to train Everfetch or third-party models.
• You retain ownership. We do not claim ownership of your inputs, outputs, prompts, URLs, or customer content.
• We don't sell personal data. We do not sell your personal data or your individual request data.

What we collect

Account data. When you create an account, we store the basic profile details returned by your chosen sign in method, such as your name, email, user ID, and provider username. If you answer the optional signup question about where you first heard about Everfetch, we also store that fixed category with the account creation event. We do not collect free text in that field. We don't request repository access or OAuth scopes beyond the profile details needed for authentication.

API key usage. Each API call is logged with operational metadata such as key ID, timestamp, endpoint, status code, latency, and IP address for rate limiting, abuse prevention, billing, and debugging. For hosted fetch, request parameters and upstream responses are processed to provide the service. We do not use customer payloads for model training or sell them as personal data.

Hosted fetch content. Hosted API requests are executed from Everfetch-managed infrastructure and selected service providers. We process submitted URLs, parameters, headers, and upstream responses only as needed to fulfill the request, operate the service, investigate abuse, or support a customer-approved debugging workflow.

Telemetry (opt-in only). If you opt in via everfetch telemetry enable, your CLI batches these fields per fetch: schema ID and version hash, success / failure flag, latency in milliseconds, coarse geo (country-level), and intent category (from the schema). Disable at any time with everfetch telemetry disable.

Website visitor identification. On our marketing website (everfetch.tech) we use a third party business visitor identification service. Through a pixel on the site, this provider and its partners may set cookies, collect device and browsing information, and match it against third party data sources to identify business visitors by name, business email, phone number, and LinkedIn profile, even if you do not submit a form. We use this only for business to business sales and marketing outreach. This applies to the marketing website only, not to the Everfetch CLI or hosted API. To opt out or request deletion, email hello@everfetch.tech.

What we don't collect

• Credentials or session cookies for any site unless you explicitly provide them for a workflow
• Cross session or cross device tracking identifiers through the Everfetch CLI or hosted API (our marketing website uses visitor identification cookies, described above)

Infrastructure and subprocessors

Our primary hosted API and fetch infrastructure currently runs in the United States. We use subprocessors for hosting, edge security, payments, authentication, email, analytics, and route-specific hosted execution. Subprocessors operate under their own security and privacy commitments or data-processing terms; enterprise customers can request the current subprocessor list during review.

Public website and API traffic is served over HTTPS/TLS. Data stored in our primary Google Cloud data stores is protected by Google Cloud's default encryption at rest. Everfetch API keys are generated with cryptographic randomness, validated by hash, and can be revoked.

Your rights

You can delete your account at any time, which removes your profile, API keys, and all associated usage logs. Aggregated telemetry (which contains no identifier) is retained. Email hello@everfetch.tech for access or deletion requests.

Changes to this policy

We may update this policy from time to time. Material changes will be posted here and noted on the changelog.