This policy explains how Imazeo Blog handles information on this product journal. The site publishes articles and provides browser-based search. It does not offer reader accounts, comments, a newsletter, payments, or a public contact form. Product security for media APIs is covered on imazeo.com/security.
Effective 8 November 2026.
Reading and searching
Public articles, fonts, and images are served by our hosting provider. Submitting a search sends your query to this site in the request URL so our server can search published articles. Search queries may therefore appear in hosting request logs. Ordinary requests may include IP addresses, request paths, browser information, and timestamps needed to deliver and protect the site. Hosting-log retention depends on the hosting account and provider settings.
What this blog stores
Published articles, categories, tags, and information pages.
Images chosen as covers or social previews.
Administrator credentials and private drafts, which are not public.
Analytics
Public pages may load Google Tag Manager container GTM-NSF2K3LP for aggregated traffic measurement with Google Analytics. Admin, private previews, and draft pages are not tracked by that public tag. You can use browser privacy settings or content blockers to limit analytics requests. Blocking analytics does not prevent reading the site.
Administration and security
A private content-management area is used by the site’s administrator. It uses an essential session cookie for sign-in and security checks. Authentication attempts and administrative events are recorded for security. These controls do not create reader accounts or enable public tracking.
Links and information you share
Articles link to external documentation and Imazeo product pages. Following a link takes you to a service with its own privacy practices. Please do not send passwords, API keys, or other sensitive information through article links or email.
Questions and changes
For privacy questions or requests, use the contact page. If you email us, we receive your address and whatever you choose to send, and use that information to handle your enquiry. We will update this policy and its effective date when the blog’s data practices materially change.