Privacy Policy
How Architecture Log handles your personal data.
Last updated: 20 June 2026
Who is responsible
Architecture Log is operated by Filip Jelev, based in Sofia, Bulgaria ("we", "I"). For any privacy question or request, contact architecturelog.com@gmail.com.
What we collect
We keep the data footprint small. We collect:
- When you sign in to comment (via Google or GitHub): your name, email address and profile picture, as provided by that service.
- Your comments and the times they were posted or edited.
- Basic technical data needed to run the site securely - a login/session cookie, and standard server logs (including IP address) kept briefly for security and abuse prevention.
- Analytics data (only if you accept cookies): anonymised usage statistics via Google Analytics - see Cookies & analytics below.
We do not use advertising or cross-site tracking cookies, and we do not sell your data.
Why we use it (legal basis)
- To let you sign in and publish comments - on the basis of your consent and our legitimate interest in running a discussion.
- To email you when someone replies to your comment - on the basis of your consent, which you can withdraw at any time (see below).
- To measure how the site is used (analytics) - only on the basis of your consent, given via the cookie banner.
- To keep the site secure and prevent abuse - our legitimate interest.
Sign-in providers & email
We use Google and GitHub only to authenticate you; we receive your basic profile from them but never your password. Reply-notification emails are sent via Google (Gmail). Their handling of your data is governed by their own policies.
Cookies & analytics
We use a minimal set of cookies, in two groups:
- Essential cookies - a sign-in/session cookie (only if you sign in to comment) and a small cookie that records your cookie choice. These are required for the site to work and are used without consent.
- Analytics cookies (optional) - with your consent we use Google Analytics to understand how the site is used (for example, which articles are read). Google sets its own cookies and processes anonymised usage data, including a truncated IP address, on our behalf; its use of data is governed by Google's own policies.
When you first visit, a banner asks you to Accept or Decline. Analytics and its cookies load only after you click Accept. If you Decline (or simply ignore the banner), Google Analytics is never loaded and no analytics cookies are set. You can change your mind at any time via Cookie settings in the footer, or by clearing cookies in your browser. We do not use advertising or cross-site tracking cookies.
Email notifications & unsubscribe
If someone replies to your comment we email you a notification. You can turn these on or off yourself at any time from your account page. Every notification email also includes a one-click unsubscribe link that stops all further emails - no sign-in required.
Managing & deleting your data
When you're signed in, your account page lets you manage email notifications, sign out, and permanently delete your account. Deleting your account immediately and irreversibly removes your profile and all of your comments, replies and likes, along with your saved sign-in tokens and cached avatar.
How long we keep it
Your account and comments are kept until you delete them (see above) or ask us to remove them. Server logs are kept only for a short period.
Your rights
Under the GDPR you can request access to, correction of, or deletion of your data, object to processing, and request a copy of it. You can delete your account and its data yourself from your account page; for anything else, email architecturelog.com@gmail.com. You may also complain to your local data-protection authority.
Children
The site is not directed at children under 16, and we do not knowingly collect their data.
Changes
We may update this policy; we'll revise the "last updated" date above when we do.