Data practice
Visitors can read Satmar.org without creating a profile, submitting a personal history, or accepting targeted advertising.
A YouTube player loads only after a visitor chooses to watch. Until that click, the page shows a thumbnail and Satmar.org’s own context without loading the embedded player. After the click, YouTube applies its separate privacy practices.
External links
Links to source repositories, archives, institutions, and media platforms lead to services that govern their own data practices.
Anonymous audience measurement
Satmar.org uses a third-party analytics provider to understand which pages and topics are useful, how visitors arrive, how far articles are read, which internal links and cited sources are opened, and how much of an embedded film is watched. The provider receives a random browser identifier together with technical details such as browser and device type, referring page, page path, and approximate location derived from network information.
The analytics service does not create person profiles for public visitors and is configured without automatic click capture. Session recording is disabled. Traffic from the editor’s office network is labeled as internal test traffic and may use one shared test profile so it can be excluded from reports. Satmar.org does not send names, email addresses, form messages, or text typed into fields to the analytics provider, and it does not use this information for targeted advertising.
Private reader conversations
When private conversations are available, the response form saves what you send, including your optional name and email address, on Satmar.org’s server as a private conversation with the editor. You receive an access code that opens only that conversation. Satmar.org keeps a one-way fingerprint of the code, not the code itself, so a lost code cannot be recovered; access expires after 90 days, and the editor can issue new access, revoke it, close the conversation, or block it.
Messages are plain text without attachments. Private conversation pages load no analytics, embedded media, or third-party resources, and they ask search engines not to index them.
Each message you send is stored with the technical details that browsers and networks normally provide with a request: your IP address; browser, device, and language information reported by your browser, including its user-agent; the referring page; and an approximate location and network provider that Satmar.org’s hosting provider derives from your IP address. Location is approximate and never precise GPS location, and browser details can be inaccurate and do not by themselves identify a person. These details help the editor investigate abuse and keep a reliable correspondence record. They are kept with the conversation for as long as it is kept, are visible only to the editor, and are never shown on your conversation page or included in email. Satmar.org does not record your cookies, passwords, or sign-in details with your messages, and records no connection details for the editor’s replies. Your network address is also used in short-lived, one-way form to limit abuse.
If you include an email address, a third-party email-delivery provider sends you a private link to the conversation once. Later email alerts, which you can turn on or off, contain no message text and no link to your conversation. The editor receives a similar notice that a new message is waiting, without its contents. Conversations are kept as needed to respond and to maintain an editorial or corrections record; to ask for deletion, say so in the conversation.
Reader responses
When private conversations are unavailable, the form sends the information you provide to the editor through a third-party email-delivery provider. Your name and email address are optional. The email also includes the submission time, IP address, browser name, and user-agent information, and, when your browser provides them, its preferred language, platform, mobile-device hint, and the referring page, to help investigate abuse and delivery problems. Messages may be retained in the editor’s mailbox as needed to respond and to maintain an editorial or corrections record. Earlier messages received this way may also be copied, with the details their email included, into the editor’s private conversation inbox; this does not give the sender access to a conversation or send them any notice.
A third-party bot-protection provider checks response submissions for automated abuse and receives the technical and network information needed to perform that check. The verification token is validated on Satmar.org’s server and is not reused.
To ask about a submitted response or request its deletion, use the reader response form and select “General feedback.”
Financial contributions
If you choose to support Satmar.org, a third-party payment processor collects the name, email address, billing details, and payment information needed to complete the contribution. Satmar.org does not receive or store full card or bank-account numbers.
The processor returns transaction details such as the amount, frequency, payment status, contributor name and email address, and any optional dedication entered at checkout. These records are retained as needed for receipts, accounting, support, fraud prevention, and the administration of recurring contributions.
Changes to this policy
This page will be updated when the site’s data practices change. Last updated October 19, 2026.