EDITION · Sat, 01 Aug 2026 · 13:26 UTC
Source-verified ledger · editorial corrections desk open
LEGAL

Privacy policy — what the desk collects and how it is used

Lvlup collects only what is needed to operate the newsroom: editorial correspondence, anonymous reading signals and the standard telemetry that keeps the site usable. We do not sell reader data and we do not share it with third-party brokers.

What the desk collects

The desk operates four inboxes (corrections, tips, partnerships, customer-care) and a reader-supported companion app. The desk collects what is needed to handle each request — a reply handle and the message content. No third-party broker forwards are used.

The site uses standard telemetry (page views, scroll-depth, broken-link alerts) to keep coverage usable. No personally identifying telemetry is sold or shared. The companion app's analytics are described in the companion app's separate policy.

What the desk does not collect

Lvlup does not collect biometric data, payment data or wagering activity. Where readers reach a publisher-controlled path, that data is processed by the publisher under the publisher's policy, not Lvlup's. The desk frames publisher paths editorially only.

READER RIGHTS

Three rights a reader always has

  • Request export of any message threads you started.
  • Request deletion of any newsletter or alert subscription.
  • Request a correction of any item the desk carries about you.

Send to the corrections desk; 14h turnaround.

RETENTION

How long the desk holds data

01

Correspondence

Inbox content kept for 24 months; the desk publishes an anonymised correction log indefinitely.

02

Reading telemetry

Anonymised, IP-truncated; 13 months rolling retention; no third-party sale.

03

App subscriptions

Bound to the companion app's policy; the app does not share subscriber data with the editorial desk.

PRIVACY · CONTINUED

How the desk enforces the four data categories

The desk's privacy standard is built on four data categories. Below is the working method for each.

Category one — correspondence

Correspondence is data the desk collects via the four inboxes. Inbox content lives on the desk's editorial mail host; the mail host retains the data for 24 months before any anonymisation.

Category two — telemetry

Telemetry is anonymised at point of collection. The desk does not store personally identifying telemetry; the desk's reading telemetry is page views, scroll depth and broken-link alerts.

Category three — app subscription

App subscription is data the companion app handles. The companion app's analytics are described in the companion app's separate policy; the desk does not share subscriber data with advertisers.

Category four — public archive

Public archive is data the desk publishes on the editorial archive. The desk retains the published corrections log indefinitely; the desk does not redact corrections log entries.

FAQ

Privacy FAQ

Does Lvlup sell reader data?
No.
Does Lvlup use third-party cookies?
Only what is required to operate the site. No advertising cookies; no remarketing pixels.
Where do I send a data-access request?
Via the corrections desk. 14h average turnaround.
Is the publisher's policy also my contract with Lvlup?
No. Publisher paths are framed editorially only; once a reader proceeds, the publisher's own privacy and terms apply.
PRIVACY · METHOD

How the desk enforces the four data categories

Below is the desk's working method for enforcing the four data categories.

Category one — correspondence

The desk's editorial mail host enforces a 24-month retention window on inbox content. After the window, content is anonymised; the anonymisation is documented on the corrections log.

Category two — telemetry

The desk's reading telemetry is anonymised at point of collection. IP addresses are truncated; user agents are stripped of identifying tokens; the desk's analytics provider is a Tier-A privacy provider.

Category three — app subscription

The companion app's analytics are described in the companion app's separate policy. The desk does not share subscriber data with advertisers.

Category four — public archive

The corrections log is public. The desk retains public archive entries indefinitely; the desk does not redact corrections log entries.

How a data subject request is processed

A data subject request is processed by the desk's privacy handler. The handler reviews the request, processes the export or deletion, and replies within 14 hours.

PRIVACY · FAQ

Reader questions on privacy and data

Below is the desk's working method for the most common reader questions on privacy and data.

How do I request my data export?

A data export request is sent to the corrections inbox with the prefix "DATA EXPORT:" in the subject. The desk's privacy handler replies within 14 hours.

How do I request data deletion?

A data deletion request is sent to the corrections inbox with the prefix "DATA DELETE:" in the subject. The desk's privacy handler replies within 14 hours.

How long does the desk retain inbox content?

The desk retains inbox content for 24 months. After the window, content is anonymised.

How long does the desk retain reading telemetry?

The desk retains reading telemetry for 13 months on a rolling basis. Anonymisation is at point of collection.

How do I unsubscribe from alert pushes?

An alert push is unsubscribed via the companion app's settings page. The companion app deletes the alert subscription on confirmation.

How do I report a privacy concern?

A privacy concern is sent to the corrections inbox with the prefix "PRIVACY:" in the subject. The desk's privacy handler replies within 14 hours.

How do I check who has access to my data?

The desk's access log is published on request. The desk replies via email within 14 hours.