Privacy Policy

# Privacy Policy

## SEM — Server Event Manager

Barry Good Games | barrygoodgames.com

---

### Summary

SEM does not transmit, share, or sell any data, and never communicates with

Barry Good Games, Tebex, or any third party. Everything — including the small

local file it uses to remember your event schedule across restarts — stays

entirely on your own FiveM server.

---

### 1. No External Communication

SEM makes **zero outbound network requests**. There is no telemetry,

analytics, license-check phone-home, or update-checker. The resource runs

fully offline aside from the FiveM server it's installed on.

### 2. Local-Only Event Persistence — No Database

To save you from re-entering your schedule after every restart, SEM saves

your **event list** (name, description, category, location, schedule, repeat

settings, max players) to a single local file, `sem_events.json`, inside this

resource's own folder.

- This file never leaves your server and is never sent anywhere.

- It contains only the event details you entered yourself — no player data.

- SEM still uses **no SQL database** — no setup, no migrations, no external

  service of any kind.

- Delete `sem_events.json` at any time to wipe all saved events and start

  fresh.

Player sign-up rosters are handled separately and are **never** written to

this file or any other — see below.

### 3. Player Sign-Up Rosters

If a server enables the player sign-up feature for an event with a coordinate

location, SEM records each signed-up player's FiveM **license identifier** in

memory, purely to:

- Track who has signed up and enforce the event's Max Players cap

- Let a player cancel their own sign-up

This identifier:

- Is never sent off the server

- Is never written to disk — `sem_events.json` (Section 2) never includes rosters

- Is never shown to other players (only an attendee *count* is shared)

- Is cleared automatically when the event ends, is edited, or the server restarts

### 4. Server Console Logging

Optional debug logging (`Config.Debug`) prints event activity to the server

console for the server owner's own troubleshooting. This stays in the local

console/log files and is never transmitted anywhere.

### 5. Server Owner Responsibility

Because all data stays on your server, **you** (the server owner) are the

operator of any data SEM handles. SEM does not impose any data-handling

obligations on you beyond what your own server already has — it simply adds

nothing new to transmit, store externally, or report.

### 6. Changes to This Policy

If a future version of SEM changes how data is handled, this document will be

updated and included with that release.

### 7. Contact

Questions about this policy: open a support ticket via your Tebex purchase

receipt, or contact Barry Good Games via barrygoodgames.com.

---

*This document describes SEM's actual behavior as shipped. It is provided for

convenience and does not constitute legal advice.*