NARENDAR MADHAVAN

Data classification

RAN1 Live is a fully public, static site. Everything that ships in the build is world-readable, so data is split into three tiers and only tier 1 is ever built.

Tier 1 — Public (safe to build and publish)

Generated by the ingestion pipelines into public/data/:

• meeting registry (meetings.json) from the 3GPP portal
• per-meeting meeting.json, schedule.json, rooms.json, agenda.json, sources.json, changes.json
• draft/FL index (drafts.json) — public 3GPP FTP file listings only

All of it is already public on 3gpp.org. No person-level information is added.

Tier 2 — Device-only (never built, never uploaded)

Stored exclusively in the browser’s localStorage on the delegate’s own device:

• bookmarks and followed agenda items
• draft read/unread state and notification preferences
• selected meeting
• display name, company group code, and room presence / check-ins (ran1live.company.*)

Rules:

• src/services/presenceService.ts is the only module that reads or writes presence. Components go through it, never through storage directly.
• If a shared presence backend is added later, it must be fetched at runtime behind the PresenceStore interface and access-controlled server-side. It must never be pre-rendered, snapshotted, or committed into public/.

Tier 3 — Secret (never in the repository)

API keys, service-role keys, private keys, venue credentials. These belong in GitHub Actions secrets or a server runtime environment, never in the repo or the client bundle.

Enforcement

scripts/check-public-data.mjs runs before every build (prebuild) and again in CI before the GitHub Pages upload. It fails the build when:

• a file under public/ is named like private data (*.private.*, *.secret.*, .env*, presence*.json, attendees*.json, …)
• any JSON under public/ contains a sensitive key (presence, checkins, attendees, email, userId, groupId, …)
• built output contains secret material (service_role, private key headers, live API key prefixes, …)

To publish genuinely public data that happens to use one of those key names, rename the field rather than weakening the guard.