Data processing terms
These terms form part of the Nodkeeper service agreement between Valvsolution and the customer identified by the account. They cover personal data we process on the customer’s instructions.
Version
Who decides how data is used?
You decide why your website uses cookies, which services to connect, and what to tell visitors. You are the controller for that processing. Valvsolution is your processor when we deliver your hosted consent configuration, record choices or inspect the public pages you authorise. If you manage a site on behalf of another controller, you must have authority to appoint us as a subprocessor and relay that controller’s instructions.
Valvsolution is a controller for its own customer accounts, security, billing and support administration. We use Resend to deliver account verification and recovery emails. The privacy notice describes that separate processing.
What you instruct us to process
Your instructions consist of this agreement, your published configurations, scan requests and subsequent documented instructions you send through support. They apply while we provide these services and until return or deletion is complete. We follow those instructions, including for international transfers, unless applicable EU or Member State law requires otherwise. We will tell you before acting on a legal requirement unless the law prohibits disclosure. We will tell you immediately if we consider an instruction unlawful under applicable data protection law.
- Visitors to your website. A hosted banner sends the site and policy revision, consent action, selected categories and a fresh random identifier for that action. We use a site-specific digest of the identifier to prevent a retry from counting twice and retain daily totals. We do not fingerprint visitors or create a persistent visitor identity. A self-hosted installation handles consent choices on the website and sends no choice events to the service.
- Optional page-view statistics. Where you enable Premium website statistics, visitors who accept analytics contribute aggregate counts in fixed route groups. The collector does not receive full page URLs, query strings or fragments. Fresh per-view duplicate-delivery keys are used for about 24 hours and removed in bounded cleanup; aggregate counts are retained for 90 days. It does not identify unique visitors or build browsing histories.
- People represented in scanned website information. At your request, the scanner visits public pages of your verified domain and records paths, cookie names and attributes, storage-key names, resource hosts and observed consent states. Paths or key names can contain personal data if your site puts it there. Reports omit cookie and storage values. Keep private areas and sensitive personal data outside the scope of a scan.
- Request metadata. The hosting and delivery providers receive network metadata, such as IP addresses, as requests reach their infrastructure. The consent reporting database keeps site-level counts and duplicate-delivery keys.
Access, security and incidents
We restrict access to people who need it to operate the service and are subject to confidentiality duties. We apply security measures appropriate to the risk, including HTTPS in production, account-scoped access to configuration and reports, restricted administrative access, and ownership checks before browser scans.
If we become aware of a personal data breach affecting data we process for you, we will notify your account contact without undue delay. We will share the nature and likely consequences, affected data and people where known, measures taken and a contact for follow-up. We will provide further information as it becomes available and assist you with the notifications you must make.
Providers and international transfers
You give us general written authorisation to use the providers listed here for processor services. OpenAI Sites hosts the application, using Cloudflare infrastructure for execution and database storage. Cloudflare also provides hosted banner delivery and browser scanning when those services are in use. Resend handles account email under our controller activities. We do not send website visitor consent events to Resend.
We will bind each subprocessor to written obligations that afford the protection required by these terms and remain responsible to you for its performance. Before adding or replacing a subprocessor, we will notify your account email and give you a reasonable opportunity to object on data protection grounds. We will discuss the objection before the change affects your data. If it cannot be resolved, you may end the affected service and request return or deletion.
Provider operations may involve countries outside the EEA. We will allow a transfer subject to GDPR Chapter V only where an applicable transfer mechanism is in place and any necessary supplementary safeguards have been addressed. You may request details of the applicable destination, mechanism and safeguards before enabling the affected hosted service.
Retention, return and deletion
A banner choice is remembered on the visitor’s device for up to 180 days. A hosted installation may queue an undelivered event on that device for up to seven days. Hosted decision reports cover 30 UTC calendar days. Server-side duplicate-delivery keys and daily totals are eligible for batched cleanup after that reporting window. Completed scan reports are available for 90 days. Expired rows are removed during service activity, so physical cleanup may occur later.
You may export your information or remove a website in the dashboard. At the end of our processor services, we will return or delete the personal data at your choice and delete remaining copies unless EU or Member State law requires retention. Export before deleting the account or ask us to arrange a return. A self-hosted banner and choices already stored in visitors’ browsers remain under the website operator’s control.
Rights requests and oversight
If a visitor contacts us about your processing, we will direct the request to you and help you respond, taking into account the nature of the processing. We will assist with security duties, impact assessments and regulator consultations, using the information available to us. You remain responsible for visitor notices, the lawful basis, the services loaded by your website, and the decisions you make about rights requests.
We will provide the information needed to assess our compliance with these processor obligations. We will allow and assist with audits and inspections by you or your authorised auditor. Coordinate scope and timing through support so that other customers’ confidentiality is protected. An urgent incident or regulatory requirement may warrant a shorter timetable.
Contact Nodkeeper support · Account and export
Legal references include the GDPR, especially Articles 28, 32–36 and Chapter V, and IMY’s guide to processor agreements.