Privacy Policy

Last updated: May 7, 2026

Panorama Tribune is owned and operated by Digent LLC (and successors or assigns)("Digent," "Panorama Tribune," "we," "us," or "our"). We operate panoramatribune.com, related subdomains, feeds, APIs, and mobile apps (collectively, the "Service"). This policy describes what we collect, how we use it, how long we keep it, and the rights you have over your data. By using the Service you consent to the practices described here.

Age of Users — COPPA

The Service is for adults. You must be at least 18 years old (or the age of majority in your jurisdiction, if higher) to access or use it. It is not directed to, marketed to, or intended for use by children or anyone under 18, and we do not knowingly collect personal information from anyone under 18. We do not collect information from children under 13 within the meaning of the Children's Online Privacy Protection Act (15 U.S.C. §§ 6501–6506) or its implementing regulations. If you are a parent or guardian and you believe a minor has provided us information, contact our contact form with the words "child deletion request" in the subject line and we will delete the information we can identify within a reasonable time.

Information We Collect

  • Visitor ID: A randomly generated UUID stored in your browser's localStorage. Used to count daily unique browsers, page views, sponsor impressions, and article click-throughs without an account. Not linked to name, email, address, or any identifier you did not provide.
  • IP Address: Logged by our servers and CDN (Cloudflare) for rate limiting, abuse prevention, and security logging. Retained in rolling access logs for up to 30 days, then deleted. Not joined to Visitor IDs or advertiser reports.
  • Aggregate Usage Data: Event counts such as page views, edition preferences, article clicks, sponsor impressions, sponsor clicks, and referrer hostnames. We publish a daily aggregate of this data on the public, append-only, hash-chained traffic ledger. The ledger contains no personal information; it is aggregate counts tied only to a calendar date.
  • Subscriber Email (optional): Only if you subscribe to a digest. Stored with a verification token and an unsubscribe token. Removed on unsubscribe.
  • Sponsor Buyer Data: If you book a sponsorship, we collect the advertiser name, contact email, headline, destination URL, budget, and a payment reference issued by our payment processor. The advertiser name, headline, and destination URL are published on the Service while the sponsorship runs (this is the ad). The contact email and payment reference are not published. Retained for the duration of the business relationship and as required for accounting and tax law.

Information We Do Not Collect

We do not require account creation to read the Service. We do not collect precise geolocation, government identifiers, biometric identifiers, immigration status, employment history, credit history, browsing history outside the Service, or inferences used to build advertising profiles. We do not operate third-party advertising trackers and do not sell or share personal information for cross-context behavioral advertising. Payment card details are never transmitted to or stored by our servers — our payment processor handles them directly.

Sensitive Personal Information — Not Collected

We do not collect "sensitive personal information" as defined by the California Consumer Privacy Act (Cal. Civ. Code § 1798.140(ae)) or analogous state laws. Specifically, we do not collect government-issued identifiers, account access credentials, precise geolocation, racial or ethnic origin, religious or philosophical beliefs, union membership, the content of mail or email or text messages, genetic data, biometric identifiers processed for the purpose of uniquely identifying a consumer, personal information collected and analyzed concerning health, or personal information collected and analyzed concerning sex life or sexual orientation.

How We Use Information

  • To operate, maintain, secure, and improve the Service.
  • To rank and cluster headlines (Visitor ID + click events).
  • To produce aggregate advertiser reports (counts only; no raw visitor identifiers).
  • To compute the daily pay-per-view debit against sponsor budgets, using only the daily aggregate unique-visitor count from the public traffic ledger.
  • To send transactional email you requested (digest verification, unsubscribe, sponsor booking receipts, refund confirmations).
  • To prevent abuse, fraud, and security incidents.
  • To comply with law and respond to lawful requests.

Cookies and Local Storage

We do not use advertising cookies. We use browser localStorage to keep a Visitor ID and theme preference on your device. If you clear storage, a new Visitor ID is generated the next time you visit; there is no cross-device linking.

Advertiser Reporting

Sponsor reports show aggregate metrics only. Unique visitors are counted by browser ID rather than by IP address, so people sharing a VPN or network are not collapsed into one visitor. We never sell, rent, license, or disclose raw Visitor IDs, user-agent strings, IP addresses, or individual browsing records to sponsors or any other third party.

The Public Traffic Ledger Is Not Personal Data

The append-only, hash-chained traffic ledger published at /traffic/ledger contains daily aggregate counts (e.g., total unique browsers per day, total page views per day, total sponsor impressions per day) and the SHA-256 hash chain that links each day to the prior day. It does not contain Visitor IDs, IP addresses, user-agent strings, account identifiers, sponsor buyer email addresses, or any other information that could be used to identify a natural person. The ledger is intentionally public so that sponsors and other third parties can independently verify that the per-view debit applied to their order corresponds to a real, immutable, hash-chained aggregate count.

Third-Party Services

  • Fly.io — Hosting. Subject to Fly.io's Privacy Policy.
  • Cloudflare — DNS, CDN, and DDoS protection. Subject to Cloudflare's Privacy Policy.
  • Resend — Transactional email delivery. Subject to Resend's Privacy Policy.
  • Payment processor — Processes sponsor payments directly; we do not receive or store card details. The active processor is named on the sponsor checkout page at the time of booking (currently Lemon Squeezy as Merchant of Record, with Stripe configured as a documented backup).

Data Retention

  • Visitor ID events: retained up to 400 days for trend reporting, then aggregated and the raw events deleted.
  • Story click-throughs: used only for the 24-hour MOST READ NEWS ranking; older clicks are aged out of the ranking query.
  • Access logs (IPs): up to 30 days rolling.
  • Subscriber records: kept while subscribed; deleted on unsubscribe (except a hashed suppression record to honor opt-out).
  • Sponsor booking records: retained for the business relationship plus the period required by tax, accounting, and legal recordkeeping laws (typically 7 years in the United States).
  • Per-view debit records: retained for at least 3 years for revenue verification and dispute resolution; the corresponding traffic-ledger entries are retained indefinitely as part of the public hash chain.

Security

We use industry-standard controls: TLS for all public traffic, least-privilege access to production, secrets stored in the host's secret manager (not in source code), encryption of backups, signed webhook handling for payment events, and routine dependency updates. No system is perfectly secure.

Breach Notification

If we become aware of a data incident that materially affects personal information of users or subscribers, we will notify affected users by email (for subscribers) and by a prominent notice on the Service, and will notify regulators where required by law, within the timeframes required by applicable law.

Your Rights (All Users)

You may clear localStorage to reset your Visitor ID. You may unsubscribe from any digest at any time using the unsubscribe link in every email. You may submit a privacy request by sending it through our contact form. We will respond within the timeframes required by applicable law.

How to Submit a Privacy Request — Verification and Authorized Agents

To process a request to access, correct, delete, restrict processing of, port, or opt out, we will need enough information to verify the request comes from you (or your authorized agent). For most requests, the email address you used when interacting with the Service plus details only the requester would know is sufficient. We will not discriminate against you for exercising a privacy right.

An authorized agent may submit a request on your behalf with written authorization signed by you. We may contact you to verify the authorization before responding.

EU/UK Residents (GDPR, UK GDPR)

If you are located in the European Economic Area, the United Kingdom, or Switzerland, you have the right to access, correct, delete, restrict processing of, port, and object to our processing of your personal data, and the right not to be subject to a decision based solely on automated processing that produces a legal or similarly significant effect. Our legal bases for processing are (a) legitimate interests in operating, securing, and reporting on an information service; (b) your consent for optional features like the email digest; (c) performance of a contract with a sponsor buyer; and (d) compliance with law. We do not transfer personal data outside the United States in a form that requires standard contractual clauses, beyond hosting providers' own cross-border processing as governed by their privacy policies. You may lodge a complaint with your local supervisory authority. Requests: contact form.

California Residents (CCPA / CPRA)

If you are a California resident, you have the right to know what personal information we collect and how we use it, to delete it, to correct it, to limit the use of any sensitive personal information (we do not collect sensitive personal information; see above), and to opt out of any "sale" or "sharing" (we do not sell or share personal information as those terms are defined under California law). We do not engage in profiling that produces legal or similarly significant effects about you. To exercise any right, contact our contact form. We will not discriminate against you for exercising your rights.

Other U.S. State Privacy Laws

We extend a substantively similar set of access, correction, deletion, portability, and opt-out rights to residents of states with comprehensive consumer privacy laws, including (without limitation) Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Utah (UCPA), Texas (TDPSA), Oregon (OCPA), Montana (MCDPA), Iowa (ICDPA), Tennessee (TIPA), Indiana (ICDPA), Delaware (DPDPA), New Hampshire (NHPA), New Jersey (NJDPA), Maryland (MODPA), Minnesota (MCDPA), Rhode Island, Kentucky, and any successor or analogous statute. We do not sell personal data and we do not process personal data for targeted advertising or for profiling in furtherance of decisions that produce legal or similarly significant effects. Submit any request via our contact form.

International Transfers

The Service is operated from the United States. If you use it from outside the United States, your information will be transferred to and processed in the United States.

Do Not Track and Global Privacy Control

Because we do not run cross-site advertising trackers, we do not respond differently to Do Not Track browser signals. Our baseline is already "no tracking." We honor the Global Privacy Control (GPC) opt-out signal where the law requires us to: because we do not sell or share personal information, the practical effect is the same as our default behavior.

Changes to This Policy

We may update this policy. The "Last updated" date at the top reflects the latest revision. Material changes will be announced by a notice on the Service.

Contact

Privacy requests, questions, or complaints: Digent LLC (and successors or assigns), c/o our contact form.

Home · About · Privacy · Terms · DMCA

© 2026 Digent LLC (and successors or assigns). Contact.

Also from Digent: Chatterbox.