Privacy Policy

Version 2026-07-16 · Last updated: 16 July 2026

This policy explains what personal information Lineup collects, why, and your choices. For any question or request, contact [email protected].

Who we are

Lineup is an independent surf-competition companion and a private family live-video service. It is operated as a personal project; the operating entity and contact address are published at [email protected]. Lineup is not affiliated with LiveHeats or any event organiser.

What we collect

  • Account details: your username, an optional email address (used for sign-in recovery and verification), and a password stored only as a salted hash (argon2) — never in plain text.
  • Social sign-in: if you use Google or Meta, we store a stable provider account identifier to recognise you. We do not receive or store your social password. The Meta email is discarded.
  • Channel configuration: for broadcasters, your own Cloudflare account identifiers and API token — the token is encrypted at rest (AES-256-GCM) and never returned to any browser.
  • Invite and guest-link records: to control who may view a private channel.
  • Technical data: IP address and basic request logs, used to rate-limit and protect the service.

Video.Family video is ingested and delivered through each family's own Cloudflare Stream account (bring-your-own). Lineup does not store your video; it only mints short-lived, signed playback URLs so your invited circle can watch while the channel is live.

LiveHeats scores.The public scores and draws pages read LiveHeats' publicly available competition data live, only on request — we fetch just the specific data needed to render the page you open. We do not crawl, copy, store, or compile a copy of that data, and we display factual results only.

Why we use it (and our legal basis)

  • To provide the service you asked for — creating your account, running your channel, and showing scores (performance of a contract).
  • To keep the service secure and prevent abuse (our legitimate interests / legal obligations).
  • To send you account emails such as invites, verification, and password resets (contract; the optional email is provided by you).

Under the EU/UK GDPR the bases above are Art 6(1)(b), (f) and (c) as applicable. In Australia, a small-business operator may fall within the Privacy Act small-business exemption; we still aim to handle your information consistently with the Australian Privacy Principles.

Who we share it with

We do not sell your personal information. We use these processors to run the service:

  • Cloudflare — live-video ingest and delivery (each family uses its own Cloudflare account).
  • Resend — transactional email (invite / verification / password-reset links only; never passwords).
  • Google and Meta — only if you choose social sign-in.
  • Our hosting/database provider — to run the application.

Some of these providers operate overseas, so your information may be processed outside your country.

How long we keep it

We keep account data while your account exists and for a reasonable period afterward to meet legal and security needs. Invite and guest links expire automatically. Ask us to delete your data at any time (see your rights below).

Your rights

You can ask to access, correct, delete, or export your information, or object to certain uses. Email [email protected] and we will respond within the timeframe required by applicable law.

Children

Lineup lets families stream footage of their own children to an invite-only circle. The family that runs a channel is responsible for the consent of everyone filmed, including minors. Accounts are intended for adults; a child should appear only within a parent- or guardian-run channel. See the Acceptable Use Policy.

Security

Passwords are hashed with argon2; per-family Cloudflare tokens are encrypted with AES-256-GCM; invite, reset, and verification tokens are stored hashed. No system is perfectly secure, but we take reasonable steps to protect your information and will notify you and any regulator as required if a notifiable breach occurs.

Cookies

We use essential cookies only (for sign-in and viewing). See the Cookie Notice.

Changes

We may update this policy; material changes will be reflected in the “last updated” date above.