Landsidu management policy (quality; information security; privacy; continuity)

LS-POL-001 · version 1.0 · Approved · next review 2027-11-07

1. Purpose

This is Landsidu's top-level policy. It sets out what Landsidu commits to in four areas: the quality of what it runs, the security of its accounts and systems, the privacy of the people who use it, and keeping its services running or getting them back quickly. Every other Landsidu document follows from it.

It tells members, players and their families what they can expect, and gives staff a fixed point to check their work against. Landsidu is built to the structure and intent of the standards in its standards register (LS-REG-008), and audits itself against them every November. It does not hold, and does not claim, any certification.

2. Scope

This policy applies to everything Landsidu runs or uses:

• the Landsidu Discord;
• every game server Landsidu hosts: "Landsidu - The After" (DayZ, Nasdara) and, when they open, "Landsidu - The Long Winter" (DayZ, Chernarus) and "Landsidu - Grundwela" (Minecraft);
• the rented server computer in Sydney that runs them, and everything on it;
• the landsidu.com domain;
• the accounts used to run them: the hosting, Discord, Steam, domain registrar and email accounts;
• Landsidu's documents, records and files;
• everyone who holds a staff role, and every member and player while they use a Landsidu service.

3. Terms

4. Responsibilities

• The Owner owns and approves this policy, and answers for Landsidu keeping to it.
• Admins and Moderators carry it out in their own work. What each role may do is set out in the access register (LS-REG-003) and the service documents; who holds each role is recorded only there.

This sets the roles and responsibilities asked for by STD-001 clause 5.3 and STD-002 clause 5.3.

5. Commitments

5.1 Quality: run things well and keep improving

• Run every service the way its documents say, and write down how each one is set up, so it can be run or rebuilt from the documents alone.
• Tell players what each server offers and keep to it. Announce changes before they happen where possible.
• Check every change to a live service before it runs, with a way to undo it.
• Use the newest supported version of every standard, tool, game and mod, test each update before it goes live, and record anything whose newest version cannot be confirmed.
• Listen to members and players: bug reports, suggestions and complaints are recorded and answered (LS-PRO-007).
• Learn from every incident and record what changed as a result.

5.2 Information security: protect accounts, systems and secrets

• Give each person only the access their role needs, and remove it when the role ends (LS-REG-003).
• Use two-factor sign-in on the accounts that run Landsidu.
• Keep passwords, keys, webhook addresses and other secrets out of every document, post and message.
• Use Discord's own tools and Landsidu's own webhooks; no third-party bots.
• Keep the server computer's software up to date in planned update windows, and harden it to a recognised benchmark.
• Report and fix security weaknesses privately; never post an exploit in a public channel (LS-PRO-009).

5.3 Privacy: collect little, keep it briefly, protect it

• Collect only what is needed to run the community and keep it safe.
• Keep each kind of record only as long as the records retention schedule says (LS-REG-007).
• Public ban and hostile lists show only active listings, by in-game name and reason. Account IDs are kept only where LS-POL-003 says; real names are not kept.
• Staff are named only in the access register (LS-REG-003). Nowhere else names a person; public documents and posts name the role.
• Follow the Australian Privacy Principles as a guide. The detail is in LS-POL-003.

5.4 Safety of children and young people

• Landsidu is for people aged 13 and over, in line with platform rules and the law.
• Design for safety first: the children's area is given by the Owner only, content filters are on for everyone, only the Owner creates invites, and newcomers wait in one room until a moderator lets them in, following the Safety by Design principles (REF-009).
• The conduct rules are LS-POL-002; reports, complaints, sanctions and appeals follow LS-PRO-007.

5.5 Continuity: keep services running and recover quickly

• For each game server, aim to restore service within 2 hours of an outage, and to lose no more than 6 hours of world progress.
• Keep backups off the server computer, and test a restore every month.
• Keep a continuity plan and rehearse it (LS-PLN-001).

5.6 Accessibility and plain language

• Write in plain Australian English, following the Australian Government Style Manual and the Macquarie Dictionary.
• Make every page and document meet WCAG 2.2 level AA (STD-013).

6. How the policy is carried out

Objectives that put this policy into measurable terms are set and checked at each quarterly management review (LS-PLN-002), and held in LS-PLN-003 Objectives (planned).

7. How it is shared

• Approved versions of the public documents are published for everyone, and the Discord links to them.
• Staff read it when they take on a role, and again after each change.

8. Review

The Owner reviews this policy every 12 months, at the management review nearest the due date, and sooner after any incident or change that affects it.

Basis: decisions D01, D02, D06 to D08, D10, D14, D16 to D18, D21 to D23, D28, D31, D36, D39 and D57 to D59 in the Landsidu decisions record. Written to the policy requirements of STD-001 clause 5.2, STD-002 clause 5.2 and Annex A 5.1, and STD-003 clause 5.2, with the continuity intent drawn from STD-004.