Privacy Policy
How visitora.eu processes data, for visitors of customer websites and for account holders.
1. What visitora.eu is
visitora.eu is a hosted website analytics service, operated by Gerald Neher on servers in the European Union. The Free plan provides aggregate traffic statistics. The optional Pro plan can also identify the company behind a visit from a corporate network's public IP registration data. visitora.eu does not use analytics cookies, browser fingerprinting or cross-site tracking, and it never stores raw IP addresses.
2. Data visitora.eu collects about website visitors
- Aggregate counters (visits per hour, day, page, source, country and device) used in the Free plan and throughout the service. These reports contain no named individual profiles.
- Event and goal names chosen by the website owner or discovered automatically from page URLs, form descriptors, button labels and link destinations, such as signup_start or signup_complete, with total triggers, daily-deduplicated session counts and aggregate funnel progress. Input values are never read, and event collection does not accept form values or free-form event metadata. Automatic discovery can be disabled per website in Settings.
- A salted hash of the IP address (first 32 hex characters of SHA-256 with a per-site secret salt) used to recognise repeat visits and link actions within one day. The IP cannot be reconstructed from the hash. Temporary session links are removed after the day ends; only aggregate counts remain.
- On Pro, company information derived from the visitor's IP address: organisation name, industry network (AS), country and city. The raw IP itself is discarded immediately after lookup.
- On Pro, page trails, dwell time, screen size, browser language and referrer/UTM attribution attached to the company record, never to a named person.
Visitors from consumer, mobile, VPN/proxy and datacenter networks are not added to Pro company records; their visits are counted only in the aggregate totals.
3. IP lookup providers (sub-processors)
For optional Pro company identification, the service queries third-party directory services over HTTPS: ipwho.is and ip-api.com (both EU-based) and optionally ipinfo.io (US-based; used only for the lookup, disclosed here). No visitor data beyond the IP address is transmitted, and the IP is not retained by the directory beyond the lookup.
3a. Google integrations (Search Console and Google Analytics import)
Account holders can optionally connect a Google Search Console property and a Google Analytics 4 property for each registered website, to import the aggregate reports Google provides (Search Console: queries, pages, clicks, impressions, positions; Google Analytics 4: sessions, users, pageviews, engagement, channel groups, countries, devices, pages). Authorization uses Google OAuth 2.0 with a read-only scope: the provider never sees the Google password and stores only the OAuth refresh token required for the API calls. The connection can be revoked at any time in the dashboard (Settings) or in the Google account; revoking deletes the stored token. The imported data is aggregate data as reported by Google (daily aggregates, retained for 400 days for Google Analytics 4 and 92 days for Search Console), stored per website like other analytics data and used solely to display the Search and Analytics tabs of the customer's dashboard. No raw, visitor-level Google data is imported. For the imported data the customer remains the controller and the provider processes it on the customer's behalf under Art. 28 GDPR (see the Data Processing Agreement); the provider is itself controller only for the stored OAuth token as part of the account data (section 5). The Google APIs used for the import are operated by Google LLC (United States); the requests are sent over TLS and the transfer is protected by the EU–US Data Privacy Framework and/or EU standard contractual clauses (Art. 44 et seq. GDPR). The agreement between the customer and Google, including the Google API Services User Data Policy, applies to the Google-side processing.
Cookies and similar technologies
visitora.eu sets no cookies and uses no local storage or fingerprinting for the
analytics measurement itself, so no cookie-consent banner is required for the analytics. The
dashboard and account area use one strictly necessary session cookie (PHPSESSID)
provided by PHP for authentication and security (provider: the hosting operator, EU-based).
It is not used for tracking or marketing, contains no personal data beyond the session id, and
expires at the end of the browser session (session cookie). No other cookies or similar storage
are set.
Storage limitation: analytics data is retained for the configured period (default 365 days) and then automatically pruned; account/billing data is retained as required by Austrian tax law (7 years) and deleted afterwards. Backups are retained for a maximum of 30 days.
Automated decision-making: visitora.eu does not perform automated decision-making or profiling within the meaning of Art. 22 DSGVO. Company records are informational only and are not used to take decisions with legal or similarly significant effects.
4. Roles and legal basis
For visitor data, the customer website owner is the controller and Gerald Neher acts as processor under Art. 28 GDPR (see the Data Processing Agreement). Because visitora.eu sets no cookies, creates no fingerprints and stores no personal identifiers beyond the salted IP hash, most customer websites do not require a cookie-consent banner for the analytics itself. The customer remains responsible for their own compliance assessment (legitimate interest balancing under Art. 6(1)(f) GDPR is commonly used). Consult your data protection officer for your specific setup.
5. Account and billing data (controller: the provider)
To operate customer accounts, the provider processes contact details (name, email), the list of registered websites and billing data: company name, billing address, country, VAT number and/or organisation registration number. When a Google integration is connected, the provider additionally stores the OAuth refresh token authorising read-only API access (section 3a); it is deleted when the connection is removed. Payment and invoicing partner Mollie receives the billing identity, invoice line items, payment references and reusable customer/mandate identifiers needed to collect payments, issue invoices and deliver invoice emails. Legal bases are contract performance (Art. 6(1)(b)) and legal obligations, in particular Austrian tax law (Art. 6(1)(c)). Billing data is retained as required by Austrian law and deleted afterwards.
6. Retention
Company records are kept for a configurable retention period (default 365 days) and pruned automatically. Aggregate counters are retained for the same period; imported Google reports for 400 days (Google Analytics 4) or 92 days (Search Console). OAuth refresh tokens are deleted when the Google connection is disconnected. Analytics data of a customer is deleted within 30 days after termination of the contract.
7. Your rights
Website visitors can request information about stored data relating to their network and its deletion (Art. 15 and 17 GDPR) from the operator of the website they visited; the provider supports the customer in answering such requests, including one-click exclusion of a network (effecting an Art. 17 erasure/opt-out). Account holders can request access, rectification, erasure, portability and object to processing by contacting legal@visitora.eu. You also have the right to lodge a complaint with the Austrian Data Protection Authority (dsb.gv.at).
8. Data residency and transfers
All analytics data is stored on servers operated by the provider in the European Union (Austria), separated per customer website; analytics data is not transferred to third countries for storage. The optional Google integrations retrieve reports from Google APIs operated by Google LLC (United States) over TLS, with the safeguards described in section 3a (EU–US Data Privacy Framework and/or EU standard contractual clauses, Art. 44 et seq. GDPR); the optional IP directory lookup (section 3) transmits only the visitor's IP in real time and stores nothing.
9. Operator contact
Gerald Neher, Rosengasse 40, 2230 Gaenserndorf, Austria · legal@visitora.eu