A useful conversation starts with trust.
What this site stores
When you comment, we store your display name, comment text, submission time, moderation status, and a keyed hash of your IP address to limit spam and duplicate reports. You can use a pseudonym. Approved display names and comments are public; IP hashes are not. Please do not post passwords, contact details or other private information.
Public reading does not require an account or tracking cookie. Administrator sign-in uses a secure session cookie lasting up to eight hours. This version has no advertising or third-party analytics. Hosting infrastructure may maintain access logs, including IP addresses, for operations and security. External source links lead to sites with their own privacy policies.
Site traffic measurement
We run our own cookie-free traffic counters to improve SI Atlas. These store hourly page-view totals, approved campaign tags and broad source names, plus estimated daily visitor counts. They do not store full referring URLs, search phrases, raw IP addresses or browser headers. Daily counting keys are created from the IP address and browser header using a daily keyed hash. They are removed from the active database after 48 hours and omitted from new daily backups; aggregate reports are retained for 180 days. These estimates can merge people sharing a network or count someone again when their network or browser changes.
Requests sending Do Not Track (DNT: 1) or Global Privacy Control (Sec-GPC: 1), known bots and administrative pages are excluded from visit counting. Operational error and response-time totals contain no visitor identifiers. Infrastructure access logs are separate and may contain IP addresses and URLs. There are no advertising or third-party analytics scripts.
Comment rules
- Discuss the event and support factual claims with sources.
- Disagree with ideas without harassment, threats, impersonation or hate.
- No spam, deceptive promotions or repeated submissions.
- All comments are reviewed. Moderators may decline publication or hide comments that break these rules. The report button sends a comment back to moderation.
Corrections and removal requests
Submit a comment on the relevant event with “Correction” or “Removal request” at the beginning. Include enough detail to identify the issue or your earlier comment. Requests remain in the private moderation queue unless they are suitable for public discussion. The editorial desk can hide approved comments and edit event records.