Privacy Policy

The privacy file sets proportional rules for what launch-time forms, member access, AI requests, analytics hooks, admin exports, and anti-abuse tooling may collect, why they may keep it, and when the notice must change.

Classification Privacy and data policy
Access Public record
Status Official public record under active editorial development

Open the privacy map Open the contact desk

Privacy File

FFTAC-PRV-01

Map Routes 5

Operating Sections 5

Quick Routes 5

Functional collection. Proportional retention. No decorative surveillance.

Privacy Policy

Who we are

Suggested text: Our website address is: http://anti-christ.org.

Comments

Suggested text: When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

Suggested text: If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

Suggested text: If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Suggested text: Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

Suggested text: If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where your data is sent

Suggested text: Visitor comments may be checked through an automated spam detection service.

Governance Map

The privacy map

Use this page to understand how signals signup, contact routing, program intake, protected access, AI inquiry, admin exports, analytics events, and security controls handle personal data before public scale arrives.

Collection

See what enters the system

Signals signup, contact routing, intake forms, protected access, and security logs all have different collection reasons.

Open data intake

Purpose

Read the operating purpose

The Foundation collects data for functional routing, protected access, and abuse prevention, not behavioral profiling.

Review operating purpose

Technical

Review cookies and technical storage

Functional cookies, server-side checks, and future third-party tooling all have to remain proportionate and visible.

Inspect technical storage

AI / Exports

Review AI, analytics, and admin exports

AI Engine requests, browser analytics hooks, and admin-only intake CSV exports now have explicit boundaries before external tooling is chosen.

Open AI and export boundaries

Retention

Understand retention and review

Stored data should match the seriousness of the relationship and should not outlive its operational purpose by inertia.

Open retention rules

Data Intake

What enters the system

The privacy file separates signups, routed forms, protected access, and abuse controls so readers can see exactly why information is being kept.

Signals

Briefing signup data stays narrow

Signals subscriptions may keep a name, email address, and reading interest so editorial follow-up can remain relevant without becoming audience profiling.

Intake

Program and contact forms collect operational context

Applications and routed messages may keep identity, role, route choice, and notes because editorial review needs enough information to answer proportionally.

Open program intake

Access

Protected participation needs account data

Member authentication only stores the profile information needed to maintain access, continuity, and accountable protected exchange.

Open the membership portal

Participant Mirror

Roster data stays secondary to WordPress identity

When Participants Database is active, member profiles and private intake may be mirrored into operational roster fields. WordPress users and Foundation private records remain the canonical audit trail.

Review member profile tools

AI Engine

AI requests may include prompts, local history, and key metadata

The signed-in AI Engine can send the current prompt and recent browser-local conversation context to the selected model provider. Personal keys are stored encrypted in user meta and are never displayed back after saving.

Open the AI Engine

Use And Storage

Why the Foundation keeps data at all

Collection is supposed to support routing, moderation, authentication, and abuse prevention rather than decorative engagement metrics or behavioral advertising.

Editorial Routing

Messages are kept so they can be answered or reviewed

The Foundation stores submissions to route corrections, media requests, recovery inquiries, and applications into the right working lane.

Open the contact desk

Protected Access

Authentication supports accountable protected exchange

Account data exists to maintain continuity and security in protected spaces, not to build a hidden surveillance profile of participation.

Review conduct boundaries

Anti-Abuse

Security logs defend the site against noise and flooding

Timestamps, rate-limit fingerprints, and operational logs may be retained when they are necessary to reduce spam, scraping abuse, or malicious automation.

Cookies And Technical Storage

How browser and server-side persistence should behave

Technical storage should stay functional, proportionate, and revisable before outside analytics, mailing tools, or consent systems appear.

Functional Cookies

Login and session continuity come first

WordPress may set the cookies needed for login state, session continuity, and basic interface preferences when protected access is in use.

Server Checks

Anti-automation controls do not need spectacle

Public forms rely on server-side timing, honeypot, and rate-limit checks so the site can remain usable without turning readers into adtech inventory.

Future Tooling

New third-party systems trigger notice revision

If analytics, consent tooling, or external mailing systems are added, this file should change before those systems go live.

Open review notices

Retention And Review

How stored data stays proportionate

Retention should match the seriousness of the relationship and should not continue merely because a system happened to store something once.

Retention

Keep data only as long as it remains operationally useful

Stored submissions and account records may remain available for continuity, security, and collaboration until those purposes genuinely end.

Minimization

Delete what no longer earns its place

The Foundation should remove personal data that no longer serves an editorial, security, or protected-participation purpose.

No Automatic Entitlement

Submission does not create membership or publication rights

Readers can contact the Foundation or apply to programs without assuming approval, continued access, or a permanent data relationship in return.

Use the contact desk

AI, Analytics, And Exports

How launch tooling stays bounded before external systems arrive

The theme now exposes AI request handling, privacy-aware analytics hooks, and admin-only intake exports without quietly turning those features into public surveillance or third-party handoff by default.

AI Requests

AI Engine prompts are operational inputs, not public records

Signed-in user prompts and recent local conversation context may be sent to the selected model provider when the engine is enabled. Responses are returned as bounded inquiry aids and should not be treated as revelation, advice, or permanent canon.

Open the AI Engine

Analytics Hooks

Theme analytics events are provider-neutral by default

The front end dispatches event names and limited context for navigation, search, downloads, forms, research filters, support clicks, and AI prompts. The theme does not install a third-party analytics provider by itself.

Review AI governance

Admin Exports

Private intake CSVs are admin-only operational handoffs

Signals, Contact Desk, Program Intake, and combined launch-intake exports exist for migration into future newsletter, support, CRM, or program tooling. They are not public downloads.

Open the contact desk