Privacy Policy

Operator and scope

The operator is CAUSIFOLD (causifold.com). Readers do not need an account to view public articles. Blogger authorization is provided by a CAUSIFOLD publisher, never by ordinary site visitors.

Information accessed

If you email us, we receive your email address and the information you provide. The Blogger integration accesses the authorized blog’s post titles, bodies, live/draft/scheduled statuses, labels, post IDs and URLs through https://www.googleapis.com/auth/blogger. It does not request access to Gmail or Google Drive.

Purpose

We respond to inquiries, avoid duplicate Blogger editions, prepare approved private drafts and publish editorially approved articles. We do not sell Google user data or use Blogger API data for advertising.

Website referral measurement

When a request for a web page contains valid UTM campaign fields, a custom Cloudflare Analytics Engine event records the requested path, article language, campaign source, medium, name and content tags, and referring hostname. That event does not add visitors’ names, email addresses, IP addresses or Google account identifiers. Cloudflare may separately process connection information to deliver and secure the website.

Storage and safeguards

OAuth credentials are configured as restricted GitHub Actions secrets. Execution logs and temporary reports may contain article content, hashes, Blogger post IDs and public URLs; actual GitHub Actions retention settings govern their retention. We do not intentionally log OAuth tokens in the publication receipts.

Live posts remain public on Blogger until an authorized editor changes or removes them. The application queries the authorized blog when running rather than storing its entire post inventory in an independent permanent database.

Service providers

Cloudflare delivers the website and processes tagged referral events; Google operates OAuth and Blogger; GitHub Actions runs the publishing workflow. Linked services including Substack and research publishers follow their own privacy practices.

Rights and contact

The account owner can revoke app access through their Google account. To inquire about personal information you supplied, correction or deletion, contact causifold@gmail.com. Applicable legal rights are unaffected.

Optional reader feedback and corrections

Only when enabled, pressing Send privately submits the article, language, answer and optional comment, or error type, excerpt, details and source URL, to improve articles and review corrections. Do not include personal, email or sensitive information. Other readers cannot see submissions. We create no reader accounts or cross-article tracking IDs and store no IP address or full user agent in this database.

Responses and comments are retained for 90 days; error reports for 180 days, then removed in one bounded daily task. UTC date boundaries and maintenance delays can delay deletion; the operator monitors this. Daily article/language/choice aggregates without personal identifiers may be kept longer. Cloudflare D1 stores submissions. Editors review them in the D1 console after signing in to their Cloudflare account; no public administration interface is provided. Turnstile validates submissions. Cloudflare may process connection information including IP addresses for delivery and security. Security scripts load after interaction; viewing alone makes no feedback API call.

For access, correction, deletion or support: causifold@gmail.com. Without accounts or persistent reader identifiers, we may be unable to locate a record. Provide only the minimum relevant submission text, article and time needed to identify it.

Updates

We will update this policy and its effective date if the described practices change.