Skip to content
BloGrove

Privacy Policy

Last updated

This policy explains what data BloGrove (“we”, “us”) collects when you visit, why, and the choices you have. We collect the minimum needed to run a blog — and most of it only after you say yes.

What we collect

Always (no cookies)

  • Aggregate page-view counts. Each article view is counted as an anonymous tally. No profiles, no cross-site tracking, no identifiers.

Only with your consent

  • Analytics (if enabled): Google Analytics 4, Plausible, or Umami may set cookies or process IPs to measure traffic. These load exclusively after you press “Accept” in the consent banner.
  • Advertising: Google AdSense and its partners may use cookies to serve and measure ads. On first visit we hold ad requests until you consent; if you decline, non-personalized placeholders or no ads are shown.

Only if you give it to us

  • Comments — if Giscus comments are active, they run on GitHub Discussions under GitHub’s privacy policy, using your own GitHub identity.

Cookies we set ourselves

One functional cookie, blogrove_session, exists only for the site administrator’s login session. Readers never receive it. Draft-preview links use expiring signed tokens instead of cookies.

Third parties

Depending on configuration, these processors may receive data strictly after consent: Google (AdSense, Analytics), your chosen analytics provider, GitHub (comments), and our hosting provider (serving pages, standard server logs). Cover images may be served via CDNs which see standard request metadata.

Your choices

  • Change or withdraw consent any time via the “Cookie settings” control in the footer.
  • Declining consent keeps the site fully readable.
  • Unsubscribe from emails with one click; ask for deletion of your email address by contacting us.

Contact

Questions about this policy? Reach us at [email protected] or through the contact page.