Wipe Analytics

What Wipe Analytics is

Wipe Analytics is a web analytics product that measures how visitors use a website, with a focus on busy sites and dynamic content. It is delivered as a script that loads from the provider and appears in third party tracker databases, which indicates it behaves like a typical analytics tracker. Detailed public documentation on its data handling is limited, so several important facts are not independently confirmed. Where the record is unclear, this profile applies the cautious assumptions a privacy officer would use.

What data and cookies it collects

As a behavioral web analytics tool, Wipe Analytics is expected to collect page views, navigation, referrers, timing and technical metadata such as device, browser and a truncated or full IP address. Unless the vendor clearly documents a cookieless design, you should assume it may set at least one analytics cookie or use a similar persistent identifier to recognise visits. That identifier, combined with IP and behavioral data, can constitute personal data. Confirm the exact cookies and fields with the provider before relying on a lighter assessment.

GDPR and ePrivacy implications

If Wipe Analytics stores or reads any identifier on the device that is not strictly necessary, Art. 5(3) of the ePrivacy Directive requires prior consent. The behavioral data it collects is processed under the GDPR, so you need a lawful basis, transparency under Art. 13 and a processor agreement. A genuinely cookieless and European hosted configuration could potentially rely on legitimate interest, but you must verify that this is actually the case. Absent that confirmation, treat the deployment as consent based.

Consent requirements

Because the cookie behavior is not publicly confirmed, the safe position is to obtain prior consent before Wipe Analytics loads, and to block the script until the user agrees. If you later obtain documented evidence that the tool is strictly cookieless, anonymises data and is hosted in the European Economic Area, you can reassess whether consent is required. Until then, treat consent as necessary and make declining as easy as accepting. Keep records of the consent you collect.

International data transfers

The hosting location of Wipe Analytics is not publicly confirmed, so you cannot assume the data stays in the European Economic Area. A cautious approach treats the processing as a potential transfer to a third country, including possibly the United States, which would require Standard Contractual Clauses or another valid mechanism plus a transfer impact assessment. Ask the vendor where data is stored and which subprocessors are involved. Document the answer and apply safeguards until the location is confirmed as European.

Practical compliance steps

Start by asking the vendor to confirm in writing whether the tool sets cookies, where data is hosted and whether data leaves the European Economic Area. Until you have that, load Wipe Analytics only after consent through your consent management platform and describe it in your cookie policy and privacy notice. Sign a data processing agreement and document your transfer mechanism. Record a short assessment that states the conservative assumptions you applied and revisit it once the vendor facts are confirmed.