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.
Monitoring data depends on your configuration and can include exception details, application stack frames, internal user IDs, routes, response timing, releases, browser pageviews, sessions and explicitly tracked product events. Generated defaults keep request bodies, headers, IP addresses, query strings, usernames, email addresses and 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. 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. 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. 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 data and invalidates its keys.
6. Your choices and rights
You can configure capture fields in the Django client, control browser consent, choose retention within plan limits and delete a project from its settings. 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.