Skip to content
lineup›
HeatmapNewsletterNews
  1. Home
  2. Security disclosure policy
Legal

Security disclosure policy

Found a security problem? Thank you. Please tell us privately so we can fix it before anyone is harmed.

Last updated 14 November 2026

How do I report a security vulnerability in LineUp?

Email hello@lineup.celira.space with the subject line "Security", describe the issue and how to reproduce it, and we will acknowledge your report within 3 working days. Please report privately and give us reasonable time to fix the problem before you disclose it. Our contact details are also published in security.txt.

What to include

  • a short description of the issue and the type of vulnerability;
  • the affected URL, endpoint or component;
  • step-by-step instructions to reproduce it, with any proof-of-concept code or requests;
  • the potential impact: what an attacker could do, and to whom;
  • how you would like to be credited, if at all.

A clear, minimal reproduction helps us fix things faster than a long scanner report.

Our commitments

What we doWhen
Acknowledge your reportWithin 3 working days
Give you an initial assessmentWithin 10 working days
Keep you updated until the issue is fixedAt least every 2 weeks
Credit you publicly, if you would likeAfter the fix is released

In scope

  • https://lineup.celira.space and its pages, including the heatmap, story pages, the newsletter archive, and the newsletter sign-up and unsubscribe flows;
  • our application programming endpoints under /api/;
  • the RSS feed and the emails we send.

Issues we especially want to hear about

  • anything that exposes subscribers' email addresses or subscription records;
  • ways to subscribe or unsubscribe someone else without their action, or to abuse the unsubscribe code;
  • injection of any kind (including into our database queries or email headers), cross-site scripting, or server-side request forgery;
  • ways to alter published stories, editions or trend data;
  • authentication or authorisation flaws in any administrative function.

Out of scope

  • Denial-of-service attacks, load testing, and anything that degrades the service for others;
  • social engineering, phishing, or physical attacks against our staff, offices or providers;
  • third-party websites and services, including X and the publishers we link to;
  • reports from automated scanners without a demonstrated, exploitable impact;
  • missing best-practice headers or settings that do not lead to a vulnerability, and clickjacking on pages with no sensitive actions;
  • rate-limit or spam issues that require large numbers of requests;
  • the contents of the lineup:subscribed item in your own browser's local storage, which holds no personal data (see our cookie policy).

Rules for testing

  • Only test against accounts and data you own. Do not access, modify or delete other people's data; if you encounter it, stop and tell us.
  • Do not subscribe email addresses you do not control.
  • Use the minimum testing needed to demonstrate the issue, and do not keep or share any data you obtain.
  • Give us reasonable time to fix the issue before disclosing it publicly; we will agree a disclosure date with you.

How LineUp is built to limit risk

LineUp is designed to hold as little as possible: the main personal data we store is subscribers' email addresses with their subscription records, kept in a managed cloud database, alongside short-lived server logs. The site sets no cookies, loads no third-party scripts and has no user accounts or passwords for readers. We use encryption in transit (HTTPS), security headers, restricted administrative access protected by secret credentials, and short retention periods, as described in our privacy policy.

What happens after you report

We reproduce the issue, assess its severity and impact, and fix it. If personal data may have been exposed, we follow the breach notification duties described in our privacy policy. When the fix is released we tell you, agree a disclosure date with you, and credit you if you would like.

Public disclosure and credit

We believe in coordinated disclosure. Once a fix is released, we agree a disclosure date with you and, if you wish, credit you by name or handle. Please do not publish details, proof-of-concept code or data before that date. If we cannot fix an issue within a reasonable period, we will explain why and agree next steps with you.

Emails or sites pretending to be LineUp

LineUp has no reader accounts, never asks for a password, payment details or personal documents, and only ever sends the welcome email and the daily newsletter to subscribers. If you receive a message claiming to be from LineUp that asks for any of these, or find a website imitating ours, please forward the details to hello@lineup.celira.space.

Safe harbour

If you act in good faith and follow this policy, we will consider your research authorised, we will not pursue or support legal action against you, and we will work with you to understand and resolve the issue quickly. This does not authorise testing of third parties' systems. We do not currently offer monetary rewards.

Frequently asked questions

Where do I report a security issue in LineUp?

Email hello@lineup.celira.space with the subject line Security. Details are also in our security.txt file.

How quickly will you respond?

We acknowledge reports within 3 working days and give an initial assessment within 10 working days.

Do you pay bug bounties?

Not currently. We are happy to credit you publicly once the fix is released, if you would like.

Will you take legal action against me?

No, if you act in good faith and follow this policy. We consider such research authorised.

Is denial-of-service testing allowed?

No. Denial-of-service and load testing are out of scope.