1. What this notice covers
BoostYard LLC owns and operates Blogged. This notice covers cookies, browser storage, pixels, scripts, and similar technologies on Blogged's marketing website, documentation, and account experience. It also explains how Blogged's optional consent controls work on customer-published blogs. A customer's own privacy and cookie notice governs the trackers and custom code that customer chooses.
2. Blogged website and account technologies
| Technology | Purpose | Duration or control |
|---|---|---|
| Firebase Authentication browser storage | Keep users signed in, refresh authentication, and protect account access | Persists according to authentication state and is cleared when the user signs out or clears site data |
| Interface and tenant preferences | Remember local product choices, active workspace context, and interface state | Varies by preference; clear it through browser site-data controls |
| Google Analytics 4 | Measure page views, acquisition, navigation, button and form interactions, scroll depth, web performance, signups, logins, and verified subscription outcomes | Off until you select Allow analytics. Google analytics cookies and Blogged's shared choice are limited to 180 days |
| Microsoft Clarity | Understand page rendering and aggregated interactions such as clicks, scrolls, navigation, and session behavior so Blogged can improve usability | Off until you select Allow analytics. Blogged remembers that choice for 180 days across its marketing, documentation, and account subdomains |
| Security and rate-limit records | Protect public endpoints and accounts from abuse | Usually server-side rather than a browser cookie; retained only as needed for security and operational purposes |
Blogged loads fonts from Google Fonts and may serve public media from an external content-delivery host. Those providers receive ordinary request data such as IP address, user agent, requested URL, and timestamp. The Google Analytics tag uses measurement ID G-457QMK65WY only after analytics consent.
3. Google Analytics 4 and Microsoft Clarity
Google Analytics 4 measures page views across blogged.dev, app.blogged.dev, and docs.blogged.dev. On the marketing and account surfaces it also measures button, navigation, outbound-link, download, form, signup, login, checkout, verified subscription, scroll-depth, and Web Vitals events. Blogged sends a surface and low-cardinality route group for reporting, retains public campaign parameters on marketing pages, and removes application query values and dynamic identifiers from URLs before measurement. It does not send form values, passwords, email addresses, entered websites, workspace identifiers, customer content, or raw dashboard button labels.
Clarity may set first-party cookies such as _clck and _clsk and Microsoft-domain cookies used for operational analytics and browser recognition. It can collect rendered page and interaction data, but form input text is masked by Clarity. Blogged sets a surface label so marketing, documentation, and account activity can be separated in analysis.
Blogged does not request either analytics tag until you select Allow analytics. If you allow it, Blogged grants analytics storage while keeping Google and Microsoft advertising storage denied; Google ad-user-data consent, ad personalization, Google signals, and ad-personalization signals also remain disabled. Blogged remembers the combined choice for 180 days across blogged.dev, app.blogged.dev, and docs.blogged.dev. You can withdraw your choice by deleting Blogged, Google Analytics, and Clarity cookies through your browser or contact Blogged with a privacy request.
4. Customer-published blogs
A Blogged customer may configure Google Analytics 4, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, TikTok Pixel, or custom code on its blog. Blogged does not add those tools to a customer blog unless an owner or admin configures them. The customer is responsible for its notices, lawful basis, consent configuration, and vendor accounts.
| Customer-blog state | What happens |
|---|---|
| No configured tags or custom code | Blogged does not inject third-party tracking tags. First-party service and aggregated product analytics may still operate as described by the customer's notice |
| Tags configured, banner off | Configured tags can load when the page loads, subject to Do Not Track and Global Privacy Control unless the customer has deliberately overridden that default |
| Banner on, no choice yet | GA4 loads with Consent Mode v2 storage denied; Meta initializes with consent revoked; GTM, LinkedIn, TikTok, and custom code are withheld until acceptance |
| Reader accepts | Consent is granted to configured providers and deferred tags or custom code load |
| Reader declines | Consent remains denied and deferred tags or custom code do not load |
5. Customer-blog consent storage
The optional customer-blog banner stores the reader's choice in local storage under blogged:cookie-consent:v1. The choice expires after 180 days, after which the banner asks again. Local storage is specific to the browser and site. Private browsing, clearing site data, or using another device may cause the banner to return.
When a browser sends Do Not Track or Global Privacy Control, customer-configured tags are disabled by default and the Blogged banner is not shown because it has nothing to request. A customer can deliberately override the tag gate in settings, but remains responsible for doing so lawfully and disclosing that choice.
6. Your choices
- Use the accept or decline controls when a customer blog displays the Blogged cookie banner.
- Enable Global Privacy Control or supported browser tracking protection.
- Block or delete cookies and local storage in browser settings. Authentication and saved preferences may stop working until restored.
- Use vendor-specific controls for Google, Meta, Microsoft, LinkedIn, TikTok, or customer-added custom tools.
- Contact hi@blogged.dev for a request about Blogged's own surfaces, or contact the customer for a request about its published blog.
7. Changes to this notice
Blogged will update this notice when its storage, analytics, or customer-blog consent behavior materially changes. The effective date at the top identifies the current version.
Questions about this policy?
Include the relevant workspace, customer blog, public URL, or account email so the request can be routed without collecting unnecessary information.
Email hi@blogged.devRelated policies