Globalogs standards
Privacy Policy
This Privacy Policy explains what data Globalogs collects, why we collect it, how long we keep it, and how readers can contact us about access, correction, or deletion requests.
Last updated: 2026-07-19
Information we collect
We collect the name, email address, and message that a reader voluntarily submits through the contact form. We may also collect operational data such as server logs, IP-related security signals, browser details, and request metadata to help keep the site secure and available.
The current application does not include a third-party analytics provider or public reader accounts. If analytics or account features are enabled later, this policy and any required consent controls will be updated to identify the data and provider.
Why we use data
We use personal data to enforce security controls, investigate abuse, operate the publishing platform, respond to reader messages, improve performance, and understand how the site is being used.
Operational logs and essential controls help maintain uptime and prevent abuse. Where required, we will seek consent before enabling non-essential analytics or advertising technologies.
Cookies, analytics, and consent
The private CMS uses an essential signed session cookie for administrator authentication. Public theme preference is stored in the reader's browser rather than a cookie. If analytics or advertising technologies are configured later, they may use cookies or similar identifiers as described here and in the Cookie Policy.
Where applicable, we will present consent choices for non-essential cookies. More detail is provided in our Cookie Policy.
Third parties and infrastructure providers
The application uses MongoDB for content and contact records and a VPS filesystem served by Nginx for uploaded publishing media. The operator's database, server, network, and backup providers may process technical information needed to provide those services.
Google AdSense code loads only when publisher and placement IDs are configured. No third-party analytics provider is configured in the current application. Each enabled provider may process technical data under its own terms and privacy policy.
Retention and user rights
Contact submissions receive an automatic expiry date. The default retention period is 180 days and can be configured between 30 and 730 days for operational or legal needs. Other operational records may follow different necessary periods.
Subject to applicable law, you may request access to your personal data, ask us to correct inaccurate information, request deletion, object to certain processing, or ask for a portable copy of data you provided. We review requests in good faith and respond according to the law that applies to the request.
Privacy requests and updates
Privacy-related questions or requests can be sent through our Contact page. We may ask you to verify your identity before we act on a request.
We may update this Privacy Policy as the product, legal requirements, or advertising stack changes. Material updates will be reflected on this page with a new last-updated date.