01
Scope and principle
This notice applies to the public website at soga.blog. Soga does not create member accounts, advertising profiles, or cross-site identifiers, and declining analytics does not restrict access to content.
02
Before consent
Soga stores no analytics events before consent. The hosting and security infrastructure may process technical logs needed to deliver and protect the site, but Soga's content analytics database does not store IP addresses, user agents, referrers, or raw query strings.
03
What is recorded after consent
Even after consent, D1 stores only the four event types below with the page path and event time. Names, email addresses, IP addresses, cookie IDs, advertising IDs, and browser fingerprints are not attached.
- Page view
- Reached 75% of a page
- Selected a labelled CTA
- Return visit from the same device
04
Choices stored on your device
The consent-policy version, allow/decline value, decision time, and last-visit time stay in browser localStorage. A new policy version asks for a new choice. You can decline at any time through Analytics settings; declining also removes the last-visit value.
05
Retention and deletion
Raw analytics events have a 90-day retention standard. Every normally accepted event automatically deletes rows older than 90 days, and data may be deleted earlier when it is no longer needed. Analytics data is not used for ad targeting or sent to external LLMs.
06
Infrastructure and external links
The public site and database run on Cloudflare-based Sites/D1 infrastructure, where processing locations can vary for delivery and security. If you follow a community or social link, that service's privacy policy applies.
07
Changing your choice and contact
Use Analytics settings at the bottom of the screen to withdraw consent or choose again. Because this site does not collect a personal identifier, it does not build a facility for locating and linking a particular visitor's analytics rows.
08
Privacy and analytics contact:
the public contact method on the Community page