Security at PanelWatcher

Pterodactyl API credentials are stored encrypted and decrypted only for server-side synchronization. Stored credentials are bound to their organization and connection. Dashboard responses do not include the stored API key.

The integration uses read-only requests and validates outbound destinations. Use a read-only Application API key scoped to the information PanelWatcher needs. You can replace the key or disconnect the integration without granting server-control access.

Customer access is scoped to the authenticated organization and verified membership. Infrastructure, capacity, notifications, support and billing records are checked against that scope on the server. Plan access checks also restrict resource details before they are sent to the customer interface.

Authorized platform administration and support have separate access controls for operating the service.

• Owner: manages the organization and its billing.
• Admin: manages configuration and team members, without billing or ownership authority.
• Member: uses and monitors the workspace within their permissions.

Team invitations and role changes are checked server-side. Hiding a control in the interface is not the billing or workspace authorization boundary.

Stripe and PayPal handle payment approval through their services. PanelWatcher verifies incoming billing webhooks and reconciles provider subscription state with the organization’s billing records.

Browser redirects alone do not grant paid access. Plan mappings and billing mutations are validated server-side, and duplicate-subscription protections prevent an active customer from starting a second subscription through another provider.

Infrastructure snapshots and history support dashboards, capacity views and alerts. Synchronization status and data freshness matter: an unavailable panel or delayed notification can affect what you see.

PanelWatcher does not require SSH, Wings command access or game-server console control. It is not a server-management agent and does not replace your operational monitoring or incident-response procedures.

Application backup tooling covers the database, support attachments and deployment configuration. Backup sets are validated, and backup health is visible to platform administrators. Recovery uses a documented restore procedure.

These are application backups, not backups of your game servers. They do not constitute a guarantee against data loss or a guaranteed recovery time.

Stored Discord webhook URLs and generic webhook destinations and signing secrets are encrypted. Settings expose safe configuration status rather than returning stored secrets. Email delivery credentials remain server-side.

Outbound destinations are validated, and generic webhook destinations require public HTTPS. Notification payloads go to the recipients or services you configure, so treat those destinations as part of your workspace’s access boundary.

Use [email protected] to report a suspected vulnerability or security concern. Describe the affected area, observed behavior and safe reproduction steps. Avoid sending credentials, customer data or exploit payloads in an initial report.

Do not access other customers’ data or disrupt the service while investigating. No security measure guarantees complete protection; reports help us investigate specific issues.