Privacy & Cookies
This page explains what data HamHub Server processes, and which cookies are used for essential functionality.
Contact
Questions, concerns, or deletion requests: info@hamhub.nl
Cookies
HamHub Server uses essential cookies to keep administrators (and optionally beta testers) signed in. These cookies are required for authentication and security.
admin_token
Purpose: admin authentication for /admin pages and /api/admin/* endpoints.
Properties: HttpOnly, Secure, SameSite=Lax.
Retention: up to 7 days (or until logout).
beta_token (optional)
Purpose: beta tester authentication for gated beta downloads.
Properties: HttpOnly, Secure, SameSite=Lax.
Retention: up to 7 days (or until logout).
We do not use advertising cookies. If we add analytics in the future, we’ll only load it after consent.
What data we collect
Bug reports may include: summary/description, email (if provided), app version, build number, track, OS, architecture, runtime ID, locale, and optional uploads (screenshots/logs).
Feature requests may include: summary/description, email (if provided), and limited app context fields (depending on the form).
Admin/beta sign-in uses essential cookies to maintain your authenticated session.
Uploads (screenshots/logs)
When you attach screenshots or logs, HamHub Server may upload those files to its configured storage provider (e.g., Cloudinary) and store the resulting URLs in the database for triage and support.
Tip: Don’t include secrets (API keys, passwords, license keys) in logs/screenshots.
Retention & deletion
We keep submitted reports/applications as long as needed for support and product improvement. If you want your submissions removed, email info@hamhub.nl with the details (ideally include the report ID).