Privacy · 2026-08-18
We receive information you submit, such as newsletter addresses, licensing inquiries, developer profile details and editorial contributions. For authenticated developer access we receive a stable account identifier, email and display name from the sign-in provider. API requests produce security and usage records.
We use information to publish journalism, provide requested services, secure accounts, meter contracted access, deliver corrections, communicate about products, prevent abuse and meet legal obligations. We do not sell developer account information as a data product.
API key plaintext is shown once and is not stored. We retain a cryptographic key hash. During agreement acceptance, network address and user-agent values are transformed with a daily rotating one-way hash to support security review while reducing long-term identifiability.
Published journalism, disclosures, provenance, corrections, claims, entities and licensed channel artifacts may be distributed through public pages and contracted machine products. Personal information is included in editorial content only under our editorial standards and applicable law.
Infrastructure, authentication, communications, analytics and payment providers may process limited information for us. Licensed buyers receive journalism and its rights metadata—not developer profiles or subscriber lists. We disclose information when required by law or necessary to protect rights and safety.
Retention depends on the purpose, security needs, contracts and law. You may request access, correction or deletion of account information, unsubscribe from email, or close an evaluation project. Some audit, transaction and editorial records must be retained for integrity or legal reasons.
Questions and privacy requests may be sent to privacy@nationaltribune.com. Material changes will receive a new policy version and effective date; prior commercial obligations remain governed by their signed agreement.
