The Apologetics Network
Support

This document is published in English, and the English text governs.

The Apologetics Network — Privacy Policy

Status: Publication draft for the public educational tier. Review by a licensed attorney familiar with US state privacy law, the GDPR, and Alabama nonprofit law has been deferred by the operator and has not taken place. This policy is not legal advice, and nothing in it is a claim of compliance.

Effective date: 15 November 2026 Website: https://theapologeticsnetwork.org Controller: The Apologetics Network, Inc.

1. Who We Are and Who Controls Your Information

The Apologetics Network is a religious educational website operated by The Apologetics Network, Inc., a nonprofit corporation incorporated in the State of Alabama on 15 November 2026, file number 001-286-700. Its registered agent is Renardo D Paggett and its registered office is 99 Lincolnshire Lane, Phenix City, Alabama 36870.

For the purposes of applicable data protection law, the controller of the personal information described in this policy is The Apologetics Network, Inc.

The corporation has not received recognition of exemption from federal income tax under section 501(c)(3), and this policy makes no claim of tax-exempt or charitable status. Donor information is not collected because donations are not accepted.

Privacy contact: info@theapologeticsnetwork.org Postal address: The Apologetics Network, Inc., 99 Lincolnshire Lane, Phenix City, Alabama 36870, United States

The operator is not established in the European Union or the United Kingdom, and no EU or UK representative has been appointed. Where the law requires a representative, one will be appointed and their details published here.

2. What This Policy Covers

This policy explains what information the site collects, why, how long it is kept, who it is shared with, and what choices you have. It covers people who browse without an account and people who register for one.

The site has two tiers. Public educational pages are readable without an account. Anyone may register for a free account, and members sign in with a one-time code emailed to them by the site. Community, prayer and live-session features are currently unavailable to everyone, and the sections that describe them apply when those features are enabled.

3. Children and Age

The site is intended for people aged 16 and older. When you register, you confirm that you meet the minimum age by accepting the Terms, and the site records that acceptance. The site does not ask for your date of birth and does not verify age.

Public educational content is readable without an account and is not age-gated. The site is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe someone under 16 has provided personal information, contact us and we will investigate and delete it where required.

4. Information Collected From Visitors Without an Account

If you read public educational content without registering, we do not ask for your name, email address, or any other identifying detail.

The server and hosting provider record technical data for every request, which is ordinary for any website. That data may include your IP address, browser and device information, the pages you request, the time of the request, and error records. It is used to deliver the site, keep it secure, and fix faults. Request logs include the address of each page requested, so for a search they include the words searched.

We do not use advertising or analytics tracking, and we do not build profiles of visitors.

Visitor count. The site keeps a simple count of visits by signed-in members. Visitors without an account are not counted, and nothing is stored about them for this purpose. For a signed-in member, a daily one-way code derived from the account is stored for two days so that each member is counted once a day, after which only the running total remains and the code is deleted. A separate indicator shows how many signed-in members are on the site at that moment and keeps nothing once they leave. Neither is used to build a profile, and neither is shared.

5. Information Collected From Registered Users

The following applies to registered members, including members first invited by the operator.

  • Account and sign-in information. Sign-in uses an email address and a one-time code that the site emails to you. The site does not store passwords. For sign-in the site stores your email address in an account record, with the time you first confirmed it and the time you last signed in; a one-way hash of each sign-in code, which works once and expires after 10 minutes; and a one-way hash of each session token, with its creation, last-use and expiry times. Used or expired code records and ended session records are not currently deleted automatically, but they cannot be used again. To limit abuse, the site also keeps short-lived counters keyed to a hash of the address or of your IP address. A one-way cryptographic hash of the email address is used to link your activity and research data to your account.
  • Invitation records. If the operator invites you, your email address is added to the Cloudflare Access allow list, and the site keeps an invitation record containing your email address, a fingerprint of who issued the invitation, its status and the date.
  • Membership details: the username you choose; an optional display name, short biography and areas of study, which are private by default; your visibility, recommendation and Newest Members settings; the version and time of each agreement and acknowledgment you accept; a last-active time; and a record of account events such as registration, suspension and permission changes. Your username appears publicly only if you opt in to the Newest Members welcome section. Your email address is not stored in these membership records.
  • Saved activity: bookmarks, saved research, notes, study progress, and lesson or presentation material.
  • Research history: the site does not store your searches or AI questions on its servers. Your browser keeps a short list of recently visited pages and, if you start one, a research session. A synced copy is stored only if you turn account sync on. Request logs, described in section 4, contain page addresses including search words, and are kept for 7 days.
  • Community content: discussion posts, study-room messages, and live session participation data.
  • Prayer submissions, where that feature is offered, which may reveal religious belief. See section 6.
  • Contact and support messages you send us.
  • AI feature inputs: the question you ask and the material sent with it.

6. Religious Belief and Sensitive Information

Prayer submissions, discussion posts, and some profile details can reveal religious belief, which is treated as sensitive personal information under the GDPR and under some US state laws.

Before prayer submission is offered again, the site will ask for explicit consent to process that information for that feature, record the consent, and provide a way to withdraw it. Withdrawal stops future processing based on consent and does not affect processing already carried out. You can withdraw by deleting the submission where the feature allows, or by contacting us.

Prayer submissions are currently unavailable and no consent step exists yet. Prayer requests submitted before the feature was closed are retained. While the Prayer Wall is off, they are visible only to the operator, on an administration page, and to no other member. They are kept until the author asks for deletion or the operator deletes them. Anyone who submitted a request before the feature closed can ask for it to be deleted at any time by emailing the address in section 1, and it will be deleted without needing a reason.

8. Public and Private Content

Content in public features is visible to other users. Prayer submissions will be either visible to other users or visible only to the operator, and the submission form will state which before you submit. Choose the route that matches what you are willing to share, and do not submit another person’s information or anything you would not want disclosed.

9. Cookies and Similar Technologies

The site sets its own sign-in session cookie (__Host-tan_session; it cannot be read by page scripts and is sent only over HTTPS to this site), which lasts until you sign out, after 14 days without use, or after 30 days at most. Cloudflare sets security cookies, and Cloudflare Access sets an authentication session cookie for the operator's administration area. These are required for sign-in and for protection against abuse, and they do not require consent where the law provides an exemption for strictly necessary cookies.

The site also sets an ah-lang cookie that remembers the language you selected, kept for one year, and uses browser storage on your device, both localStorage and sessionStorage, for your first-visit acknowledgment, your research, highlights, notebook, lessons, sync status and display preferences. That storage stays on your device unless you turn on account sync. You can clear it in your browser settings.

We do not use advertising or analytics cookies.

Embedded video. Some pages embed YouTube videos through the privacy-enhanced youtube-nocookie domain. Even in that configuration the player is a Google service that receives your IP address and the page it was loaded from, and it may set its own cookies once playback begins. Its own privacy notice applies to that processing. Loading is triggered when the page renders; where a page loads the player only on click, the data is not sent until you press play. The video library page is not part of the public educational tier and is available only to signed-in members.

You can block or delete cookies in your browser settings. Blocking the necessary ones will prevent sign-in from working.

10. Service Providers and Sharing

  • Cloudflare provides hosting and content delivery, security, authentication through Cloudflare Access, email delivery of sign-in codes through Cloudflare Email Sending, the Cloudflare Turnstile check on the sign-in and registration forms (Cloudflare evaluates signals from your browser, and the site receives only a pass or fail result), the D1 database, real-time features, AI inference through Workers AI, and request logs. Cloudflare processes information to provide those services under its own terms and privacy documentation.
  • AI inference. AI features run on Cloudflare Workers AI using the models llama-3.1-8b-instruct-fp8-fast and m2m100-1.2b. There is no AI gateway, no vector store, and no separate direct integration with another model provider. Cloudflare runs these models on its own network and through sub-processors it lists publicly; for Workers AI those currently include CoreWeave, Inc. in the United States and Nebius BV in England. AI features are available to signed-in members only and form no part of the public educational tier. Cloudflare’s documentation for Workers AI states that standard inference requests are not retained after the response is delivered and are not used to train models. Quranic Arabic text is not sent to the model. English translations may be sent as context.
  • Email delivery. The site sends its one-time sign-in codes through Cloudflare Email Sending, from no-reply@notify.theapologeticsnetwork.org; Cloudflare receives your email address and the message in order to deliver it. Cloudflare Access delivers its own one-time code only for the operator's administration area. No separate email provider is used.
  • Embedded video. YouTube, through the youtube-nocookie domain, as described in section 9.

Administrator access. The operator can see, on an administration page, each account’s display name, a short fingerprint, how many items, notes and lessons that account has synced, and when it was last active. For members who have registered, the operator can also see the username, membership status, role, feature restrictions, agreement records and last-active time, and can suspend an account or restrict a feature; these actions are logged. The operator cannot see the content of notes, highlights or lessons there. The operator can read prayer requests and discussion messages on that page in order to moderate them. Because the data is held in the site’s Cloudflare database, the operator can technically reach its content for maintenance, security, backups or to answer a request from you. Administrators appointed by the operator, currently no more than three, can delete prayer requests.

Other users may see what you choose to share in public features. We do not share information with advertisers or data brokers. We may disclose information where the law requires it, or where reasonably necessary to protect the site, our users, or another person.

11. How Long Information Is Kept

InformationRetention
Request logsCloudflare Workers Logs, captured at full sampling and retained for 7 days
Account, display name, saved activityUntil you delete it or request account deletion
Community posts and messagesDeleted automatically after 30 days
Inactive study roomsDeleted after 30 days without activity
Live session dataDeleted 10 minutes after the session ends
Prayer submissionsUntil you, the operator, or an appointed administrator deletes them
AI inputs and outputsNot retained by the provider after the response. The site does not store your questions or the answers, with two exceptions: an AI research translation of a hadith narration is kept in a shared cache, holding only the narration reference, the translated text, the model name and the date, with no user identifier, so the same narration is not translated twice; and daily AI usage counters, keyed by a one-way code for the account and for the network, are kept for 3 days to enforce usage limits
Contact and support messagesKept for as long as needed to answer them and for our records, then deleted
Database backupsExports are made manually by the operator, not on a schedule, and are kept in one folder. Each time the backup script runs it keeps the 12 newest exports in that folder, including any made separately for maintenance, and deletes older ones; until it next runs, more than 12 can be held. Cloudflare D1 point-in-time recovery (Time Travel) keeps up to 30 days of history: 30 days on Cloudflare's Workers Paid plan, 7 days on its free plan

We keep information longer where we must to meet a legal obligation, resolve a dispute, or address a security issue.

12. Your Rights and Choices

Where the law gives you these rights, you may ask to access your information, correct it, delete it, restrict or object to its processing, receive a portable copy of information you provided, and withdraw consent where consent is the basis.

To exercise a right, email us at the address in section 1. We may ask for information needed to verify your identity, and where the GDPR applies we respond within the period the law requires, generally one month, subject to lawful extension.

If you are in the EEA you may complain to the supervisory authority where you live, work, or believe a breach occurred; a list is published by the European Data Protection Board. If you are in the UK you may complain to the Information Commissioner’s Office. You may also contact the privacy regulator where you live.

13. Account Deletion

The self-service control, Remove synced copy, removes synced items: saved research, notes, bookmarks, and progress. It does not remove everything, and an account is not fully deleted by the control alone. Invitations, shared note links, and prayer submissions are removed when you email us and ask. A shared note link can also be revoked by you, which erases the stored copy at once.

To close an account and have the remaining associated information removed, email us from the address associated with the account. We confirm the request against that address before acting, because acting on an unverified request would let a third party delete someone else’s account.

Some information persists after deletion. Deleted records can remain in database exports made before the deletion until those exports are deleted (exports are made manually, and the backup script keeps the 12 newest each time it runs), and in Cloudflare’s point-in-time recovery history for up to 30 days. Content other users have copied, and pages a third party has indexed, are outside our control. Records we must keep by law, or need to establish, exercise, or defend a legal claim, are retained.

14. Security

Access to account features is controlled by the site's own sign-in session, which the application checks on each request rather than trusting a client-side flag; the administration area is also controlled by Cloudflare Access, whose authentication token the application verifies on each request. Sign-in is by email one-time code. The site is served over HTTPS.

No system is completely secure. We do not claim that the site is certified, audited, or isolated, and we do not describe any control in stronger terms than the implementation supports.

If a personal data breach occurs we will assess and respond as the law requires, including notifying a supervisory authority within the period the GDPR sets where it applies and the breach meets the notification threshold, and notifying affected people where the law requires it.

15. Changes and Contact

We may update this policy when our practices change. The updated version is posted with a new effective date, and where a change is material we provide additional notice or obtain consent where the law requires it.

Questions, requests, or complaints: info@theapologeticsnetwork.org, or by post to The Apologetics Network, Inc., 99 Lincolnshire Lane, Phenix City, Alabama 36870, United States. The controller is The Apologetics Network, Inc., an Alabama nonprofit corporation.