Data Processing Agreement (Art. 28 GDPR)
Data processing terms between the website owner (controller) and Gerald Neher (processor) for the visitora.eu hosted analytics service.
1. Parties and scope
This agreement supplements the Terms & Conditions. The controller is the customer operating one or more websites registered with the service. The processor is Gerald Neher, who operates the hosted visitora.eu installation (tracking endpoints, data store and dashboard) on servers in the European Union for the controller. This agreement is concluded in the written form required by Art. 28(9) GDPR and § 11 of the Austrian Data Protection Act (DSG) and constitutes the controller's documented instructions under Art. 28(3) GDPR.
2. Subject matter, duration, nature and purpose
- Subject matter: provision of aggregate website analytics and, on the optional Pro plan, company-level identification for the controller's websites; and, at the controller's option, import of aggregate reports from Google Search Console and Google Analytics 4 properties connected by the controller.
- Duration: for the term of the service contract, ending with deletion under section 7.
- Nature and purpose: aggregation of page measurements and website-owner-defined or automatically discovered event names into traffic, goal and funnel reports; on Pro, identification of visiting companies from public IP directory data and aggregation of page trails, dwell time and attribution into company records; presentation in a protected dashboard; on the controller's instructions (connecting a property), retrieval via Google APIs of the aggregate reports Google provides for that property (Search Console: queries, pages, clicks, impressions, positions; Google Analytics 4: sessions, users, pageviews, engagement, channel groups, countries, devices, pages, as daily aggregates) and their storage and presentation next to the other reports. No raw, visitor-level records are imported from Google.
- Categories of data: company identifiers (organisation, AS/network, country, city); salted IP hash (non-reversible); page trails, dwell times, screen size, language, referrer/UTM data; event and goal names without form values or free-form metadata; imported aggregate Google reports as listed above; the OAuth refresh token authorising read-only access to the connected Google property. No names, email addresses, cookie IDs, device fingerprints or raw IP addresses.
- Categories of data subjects: visitors of the controller's websites (employees of visiting organisations and other visitors, whose visits are discarded unless they originate from a corporate network); for the imported Google reports, the same visitors in aggregated form only, as reflected in the reports provided by Google.
3. Obligations of the processor
Technical and organisational measures (TOMs): transport encryption (TLS) end to end; salted SHA-256 hashing of IP addresses; token-protected access with MFA; separate data stores per customer website; server-side bot and non-corporate filtering; daily encrypted backups retained for 30 days; access limited to authorised personnel; admin action logging; OAuth refresh tokens for connected Google integrations stored only in the account database, usable solely for the agreed read-only scopes (webmasters.readonly, analytics.readonly) and deleted when the connection is removed.
Breach notification: the processor notifies the controller without undue delay and in any event within 72 hours of becoming aware of a personal data breach (Art. 33/34 GDPR), and supports the controller in meeting its own notification obligations.
The processor processes personal data only on documented instructions of the controller; ensures confidentiality of persons authorised to process; implements appropriate technical and organisational measures (Art. 32 GDPR): salted hashing of IP addresses, token protected access, no-cookie operation, separate data stores per customer website, server-side bot and non-corporate filtering, EU hosting; engages sub-processors only under section 4; and assists the controller with data-subject requests, breach notification and data-protection impact assessments through the service's exclusion, export and ROPA features.
4. Sub-processors
The controller authorises engagement of the following IP-to-company directory services, invoked over HTTPS and receiving only the visitor's IP address: ipwho.is (EU), ip-api.com (EU) and optionally ipinfo.io (US; can be disabled on request).
When, and only as long as, the controller connects a Google integration, the following provider is engaged for the import API calls, invoked over HTTPS and receiving only the OAuth access token and the requested report parameters: Google LLC (United States; Google Search Console API, Google Analytics Data API, Google Analytics Admin API). Google may process these requests in the United States; the transfer is safeguarded under Art. 44 et seq. GDPR by Google's participation in the EU–US Data Privacy Framework and/or by EU standard contractual clauses. The controller can end this processing at any time by disconnecting the Google integration in the dashboard, which deletes the stored refresh token.
The processor informs the controller of any intended change of sub-processors and the controller has a right to object.
5. Data subject requests
The processor promptly forwards requests from data subjects to the controller and supports their fulfilment: network-level exclusion (Art. 17 erasure/opt-out), export of stored records, and Art. 30 Records of Processing Activities directly from the dashboard.
6. Audits
The controller may audit compliance with this agreement with reasonable notice; the processor provides the information needed, including this documentation and a human-readable export of the controller's data. The underlying data format is open (plain JSON) and fully inspectable by the controller at export.
7. End of provision; deletion and return
At the end of the service contract, the processor returns (export) and then deletes all personal data within 30 days, except where Union or Member State law requires storage (e.g. invoicing data). Data retention during the contract is configurable (default 365 days); automatic pruning enforces it. Imported Google reports are kept for 400 days (Google Analytics 4) or 92 days (Search Console) and then pruned; OAuth refresh tokens are deleted when the controller disconnects a Google integration.
8. Governing law
Austrian law; place of jurisdiction Gaenserndorf, Austria.