1. Who is responsible
FetchNode operates FetchNode. Privacy questions and data requests can be sent through the public support channel; request a private contact route and do not post personal data publicly.
2. Data we process
Account data includes your email address, authentication records, workspace membership and project configuration. Billing data includes Stripe customer, subscription and invoice identifiers; card details remain with Stripe.
A project manager can create an expiring shared evidence link after reviewing an aggregate snapshot. FetchNode stores that snapshot, the chosen period and inclusion options, its creator, expiry and revocation state, plus an anonymous view count and last-view time. The view counter does not store a recipient identity or IP address. A verified improvement snapshot contains one aggregate before/after result, exact windows and sample counts for the same hidden route. Website name and maintenance request volume are excluded unless the manager opts in; domains, routes, issue titles, stack traces, release names and identifiers, user data, conversion data, request data, SQL and private notes are not included.
When a workspace administrator connects Google Search Console, FetchNode stores the connected Google account email, encrypted OAuth credentials, accessible property URLs and imported finalized search-performance data. Imported data can include dates, search queries, landing pages, countries, devices, search types, clicks, impressions, click-through rates and average positions. FetchNode requests read-only Search Console access.
When a project manager explicitly requests AI SEO advice, FetchNode fetches a bounded extract of the selected public landing page and may fetch public competing pages from the same mapped Search Console property. It sends the extracted title, description, headings, link evidence and visible text together with the selected query, aggregate search statistics and aggregate landing-page outcomes to xAI. FetchNode removes URL query strings and does not include Google credentials, cookies, request headers, visitor identifiers or private monitoring payloads in this request.
Monitoring data depends on your configuration and can include exception details, application stack frames, internal user IDs, routes, response timing, releases, normalized database-query structure, browser pageviews, Web Vitals, sessions, background-job health and explicitly tracked product events. Generated defaults keep request bodies, headers, IP addresses, query strings, usernames, email addresses, SQL parameters and raw SQL text disabled.
3. Why we process it
We process account, project and billing data to provide the service and administer your subscription. We process operational records to secure the service, prevent abuse and diagnose failures. With your analytics consent, FetchNode records pageviews, an anonymous visitor and session identifier, internal account ID after sign-in, and explicitly tracked product events so we can understand product journeys. Declining analytics leaves this optional measurement off; operational error monitoring is handled separately. Google user data is used only to provide and secure the user-facing Search Console integration, including manager-requested page advice; it is not sold or used for advertising. AI advice is generated only after a project manager requests it and is presented as an inference with its evidence and limitations. Human access is limited to what is necessary for security, support requested by the user, legal compliance or other circumstances permitted by applicable policy. When you use FetchNode for your own visitors, you determine the lawful basis and consent requirements for the monitoring configuration you enable.
4. Service providers
FetchNode uses infrastructure, email-delivery and payment providers where needed to run the service. Stripe processes checkout and payment details under its own privacy terms. Google provides the optional OAuth identity and Search Console APIs; using that integration is also subject to Google’s applicable terms and privacy policy. xAI processes bounded page and aggregate performance evidence when a project manager requests Grok SEO advice. FetchNode asks the xAI Responses API not to store the conversational response state; xAI account-level audit retention or Zero Data Retention settings can still apply. Providers receive only the data needed for their function and are expected to protect it appropriately.
5. Retention and deletion
Raw monitoring history is retained according to the active plan. A shared evidence link stops working at its selected expiry or immediately after revocation; its bounded snapshot and counters remain available for an audit period and are deleted 180 days after expiry or revocation, or sooner when its project is deleted. Imported Search Console performance is retained for approximately 16 months. Generated SEO advice and its bounded evidence metadata remain with the project until that project is deleted; the full extracted page text is not retained in the project record. Disconnecting a Google account removes its credentials, properties and imported Search Console data, and FetchNode attempts to revoke the Google token. Account, subscription and security records can be retained longer where required to operate the service, resolve disputes or meet legal obligations. Confirmed project deletion permanently removes the project and its associated monitoring, shared evidence links, mapped search-performance data and generated advice, and invalidates its keys.
6. Your choices and rights
You can preview what a shared maintenance or improvement card contains, keep optional identity and volume fields off, select its expiry and revoke its bearer link. Improvement cards hide the compared route, environment and release identifier and expose only aggregate before/after values, sample counts and exact windows. Anyone who receives an active link can read the chosen snapshot, so share it only with the intended audience. You can also configure capture fields in the Django client, control browser consent, choose retention within plan limits, disconnect Google Search Console and delete a project from its settings. You can withdraw FetchNode’s access from your Google Account permissions. Depending on your location, you may request access, correction, deletion, restriction, portability or object to certain processing. Contact us from the account email so the request can be verified.
7. Changes
Material changes will be reflected by updating the effective date and, when appropriate, notifying account owners. This notice describes the application as shipped; deployment-specific operator details should be configured through the production environment.