Where self-hosted server data is stored
Messages, files, emojis and settings stay on your own machine. Only accounts, sign-in, banners and access rules live in the GameVox cloud.
Your community's content is stored on your own machine. The GameVox cloud stores only user accounts and sign-in, server banner images and the rules for who can join.
Stored on your server
| Data | Where |
|---|---|
| Channels, categories, groups, roles and permissions | community.db |
| Server settings, member list, ban list, emoji details | community.db |
| Announcements, events and badges | community.db |
| Chat messages, reactions, pins and read state | content.db |
| Polls | content.db |
| Uploaded files and attachments | data/files/ |
| Custom emojis | data/emojis/ |
| Soundboard clips | data/soundboard/ |
| Activity log | audit.db (not in backups; deleting it only clears the log) |
| Backups | data/backups/ |
Encrypted on disk
community.db, content.db and audit.db are SQLite files encrypted with SQLCipher, and so are the database snapshots in data/backups/. The key comes from your server's identity, so another server's binary cannot open them. Databases from older, unencrypted versions are converted the first time a newer version starts.
These are not encrypted, so protect them with file permissions or disk encryption:
- Uploaded files, custom emojis, stickers and soundboard clips (
data/files/,data/emojis/,data/stickers/,data/soundboard/) - The file zips inside backups (
files_backup_*.zipanddata/backups/large_files/) - Logs in
data/logs/andGENERATED-README.txt
Stored in the GameVox cloud
- User accounts and sign-in (login, registration, sessions)
- Server banner images
- Access rules (who can join the server)
Voice, video, chat and files go directly between members and your server. The cloud handles sign-in and coordination.
The status heartbeat
Every 30 seconds your server sends a small status report to the GameVox cloud. It runs the owner dashboard, times updates and helps find problems.
| Data | Why |
|---|---|
| Server version and database schema version | Updates and migrations |
| Number of connected users and video or screen shares | Owner dashboard and update timing |
| Uptime, memory use and goroutine count | Health monitoring |
| Database sizes, storage size, message and file counts | Storage monitoring (counts only) |
| Backup status and time | Alerts if backups stop |
| Control channel reconnect count | Connection stability |
| Recent error types and context | Finding problems; truncated, with no user data |
If you set PUBLIC_IP, or the server finds a public IPv6 address, the heartbeat also carries that address and the TCP port, so the cloud can tell members where to connect.
The heartbeat never includes message text, voice audio, file contents, usernames, channel names or members' IP addresses.
Other things the server sends
- A setup summary when it connects: the same text as
GENERATED-README.txt(paths, ports, addresses, build and disk use), so support can help without asking you for it. - Website Widget data, only if you turn the widget on: its settings and the data it shows.
- Mobile push notifications: the channel name and which members to notify, for example "New message in #general". No message text, sender name or topic title.
- Logs, only when you ask: Send Logs to GameVox in Server Settings > Server uploads your log files.
Export your data
You can export any table from your local databases with the server's export flags. See Self-hosted server command-line options.