Skip to content
REDACTED FORGEAmerican history. Evidence attached.

Privacy

Keep the receipts.
Respect the visitor.

This page explains the basic information Redacted Forge may receive when people visit the site, use site features, or voluntarily submit material.

Citation guide

Information you choose to provide

If you submit a historical question, source lead, correction, message, or other material, we may receive the information included with that submission. Do not send passwords, financial credentials, or other sensitive information that is not needed for the request.

Basic website and security data

Hosting, security, and delivery providers may process ordinary technical information such as IP address, browser or device information, request time, requested pages, and security signals needed to operate and protect the site.

Analytics

Redacted Forge may use privacy-conscious analytics or platform reporting to understand traffic, performance, and how public content is discovered. Analytics should be used to improve the site and content—not to turn uncertain or unavailable data into invented facts.

Accounts and sign-in

If Investigator access is activated and you choose to sign in, an approved identity provider such as Google, Apple, or passwordless email may process the account information needed to authenticate you. Public Investigator authentication is separate from the private owner console and does not grant operator access. Signing in does not subscribe you to Redacted Dispatch. When public accounts are active, the account page also provides a control to delete the current authentication identity.

Referral and first-party attribution

When a link identifies the source, campaign, File, derivative, or language that brought you to Redacted Forge, the site may preserve a small first-party referral record so Redacted Forge can measure which distribution routes lead to useful return visits. This referral record is not used to import your social contacts or stitch your identity across unrelated platforms.

Cookies and local storage

Hosting, security, authentication, preferences, or embedded services may use cookies or similar browser storage when necessary for their function. The site should avoid unnecessary tracking where a simpler approach works.

Third-party services and links

Links, embeds, newsletters, video platforms, payment services, or other external services may have their own privacy practices. Their policies govern information handled on their services.

Retention and corrections

Information should be kept only as long as reasonably useful for the purpose it was provided, operational security, recordkeeping, or legal obligations. Editorial corrections and historical source records may be preserved when needed to maintain an accurate public record.

Policy updates

This policy may change as the site adds or removes services. Material changes should be reflected on this page rather than silently represented as old policy. Effective date: September 17, 2026.

Trust & MethodologyTermsCite & ReuseHome