Scoby Analytics

Scoby Analytics is a privacy-focused analytics plugin for WordPress. It is designed to provide website operators with actionable usage statistics without using cookies, device fingerprinting, or cross-site identifiers.
The WordPress integration is a lightweight, client-side integration that prioritizes visitor privacy. Scoby’s goal is to enable analytics in a way that can typically be operated under legitimate interest (Art. 6(1)(f) GDPR) and without consent banners, provided it is used as intended and configured appropriately. Scoby does not provide legal advice; always assess your specific setup with your DPO/legal counsel. We’re happy to answer their questions at <a href="mailto:hello@scoby.io" rel="nofollow ugc">hello@scoby.io</a>
<h3>Privacy approach (GDPR / ePrivacy)</h3>
Scoby is designed around the following principles:
<ul>
<li>No cookies / no storage on the user device (relevant for ePrivacy / TDDDG)</li>
<li>No device fingerprinting</li>
<li>No user profiles or cross-site tracking</li>
<li>Anonymization before transmission and aggregated storage (no individual-level analytics)</li>
</ul>
This means Scoby is not trying to “optimize consent rates”. Instead, it aims to reduce or avoid regulated processing operations in the first place by keeping analytics non-identifying and aggregate.
<h3>What Scoby measures</h3>
Scoby provides aggregated statistics such as:
<ul>
<li>Page views and visits</li>
<li>Entry/exit pages and content performance</li>
<li>Engagement metrics (e.g., time-spent distributions/percentiles)</li>
<li>Conversion events (depending on your setup)</li>
<li>Referrers and traffic sources (without persistent identifiers)</li>
</ul>
<h3>What Scoby does not do</h3>
<ul>
<li>No cookies</li>
<li>No device fingerprinting</li>
<li>No cross-site tracking</li>
<li>No user/device profiles</li>
</ul>
<h3>Reporting & exports</h3>
<ul>
<li>WordPress dashboard reporting</li>
<li>Export to <code>.xlsx</code></li>
<li>Integrations with BI tools (e.g., Looker Studio, PowerBI, Tableau)</li>
</ul>
<h3>Third Party Services</h3>
Scoby Analytics uses Scoby-operated servers for analytics processing.
<h3>Service Used</h3>
Service: Scoby Analytics Servers 
Purpose: Capture, process, and store website usage statistics in an anonymized and aggregated form to provide analytics reporting.
<h3>Data Handling and Privacy</h3>
– Anonymization prior to transmission: Page views and associated metrics are anonymized before being transmitted to Scoby Analytics servers. 
– Aggregation: Stored data is aggregated and not intended to relate to identifiable individuals. 
– No personal identifiers: Scoby is designed to avoid collecting or storing identifiers such as cookies, fingerprinting signals, or IP addresses.
<h3>Transparency and further information</h3>
– Service information: https://www.scoby.io/ 
– Terms of Use: https://www.scoby.io/terms 
– Privacy Policy: https://www.scoby.io/privacy

Privacy-focused analytics for WordPress — designed to minimize data protection risk under EU GDPR and ePrivacy.

jinaldesai

FlareStats brings your CloudFlare web analytics data directly into the WordPress admin. No third-party tracking services, no cookies — just privacy-preserving analytics from Cloudflare.
<h4>Features</h4>
<ul>
<li>Dashboard Widget — A compact summary widget on the WordPress Dashboard.</li>
<li>Full Analytics Screen — Dedicated admin page with a 7-day daily chart, top 5 pages, and top 3 countries.</li>
<li>Last 7 Days — Data always covers the rolling last 7 days.</li>
<li>Cloudflare GraphQL API — Connects to the Cloudflare GraphQL Analytics API using your API Token.</li>
<li>Lightweight & Dependency-Free — No external JavaScript frameworks; charts are CSS-based.</li>
<li>Caching — API responses cached via WordPress transients to minimise API calls.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>A <a href="https://cloudflare.com" rel="nofollow ugc">Cloudflare</a> account with Web Analytics enabled for your site.</li>
<li>A Cloudflare API Token with Account Analytics: Read permission.</li>
<li>Your Cloudflare Account ID.</li>
<li>Your FlareStats Site Tag (optional but recommended for multi-site accounts).</li>
</ul>
<h4>Configuration</h4>
<ol>
<li>In your Cloudflare dashboard go to My Profile → API Tokens and create a token with Account Analytics: Read permission scoped to your account.</li>
<li>Note your Account ID (visible in the Cloudflare dashboard right-hand sidebar).</li>
<li>Go to Analytics & Logs → Web Analytics, select your site, and copy the Site Tag from the site settings (optional).</li>
<li>In WordPress go to FlareStats → Settings and enter your credentials.</li>
</ol>
<h4>Privacy / Tracking Disclosure</h4>
FlareStats displays analytics data inside WordPress by requesting reports from Cloudflare Web Analytics.
What this plugin sends to external services
<ul>
<li>This plugin sends authenticated requests from your WordPress site to the Cloudflare GraphQL API (<code>api.cloudflare.com</code>) using your configured API token, account ID, and site tag (if provided).</li>
<li>Request parameters include reporting date ranges and query fields needed to fetch analytics metrics.</li>
</ul>
What this plugin receives
<ul>
<li>Aggregated analytics data such as pageviews, visits, top pages, top countries, browser/device, and referrer/source metrics.</li>
<li>This plugin displays those metrics in the WordPress admin dashboard and analytics screens.</li>
</ul>
What this plugin stores in WordPress
<ul>
<li>Plugin settings in <code>wp_options</code> (for example API token, account ID, site tag, cache duration).</li>
<li>Cached analytics responses in WordPress transients to reduce API calls.</li>
</ul>
Personal data handling
<ul>
<li>This plugin does not create its own visitor tracking cookies.</li>
<li>Visitor analytics collection is performed by Cloudflare Web Analytics on your site.</li>
<li>This plugin does not add separate per-visitor profile records in WordPress for analytics.</li>
</ul>
Data retention / access
<ul>
<li>Cached analytics data is temporary and expires according to the configured cache duration.</li>
<li>Plugin settings and analytics screens are only accessible to users with appropriate admin capabilities (for example <code>manage_options</code>).</li>
</ul>
Third-party policies
<ul>
<li>Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/</li>
<li>Cloudflare Terms: https://www.cloudflare.com/website-terms/</li>
</ul>
Site owners are responsible for ensuring their site’s public privacy policy accurately describes how Cloudflare Web Analytics is used.

FlareStats

Display CloudFlare Web Analytics data — pageviews, visitors, top pages and top countries — right in your WordPress admin.

Scoby Analytics vs FlareStats